docs(docs): Add some "how-to" documentation for website development

[Josmithr]

Includes notes on:

• "Documents" vs "Pages"
• Modifying sidebars
• Docs versioning

AB#24262

[Josmithr]

For reviewers:

• I'm looking for feedback on what I have added so far. I've erred on the side of being somewhat minimal, and linking to Docusaurus's documentation, rather than re-stating what they have already documented. This also helps future-proof us somewhat as they update their own docs. That said, I'd still like for our own docs to be more useful than "go read Docusaurus's docs". It's a fine line to walk. Any feedback is appreciated s🙂
• I'm also looking for suggestions for other guides that would be helpful to add. We can always add more later as needed, but I'm also happy to add more now.

[Josmithr]

@zhenmichael I'd like to document the steps for setting up API model artifacts publishing for a new release branch, if possible. Hoping you can help me fill that in, assuming we have a process in place for that 🙂

[zhenmichael]

Looks good overall! The pubishing pipeline should automatically generate new artifacts in the blob storage the first time a new major version release version is run. As long as the config file is updated the download-apis step should have access the correct artifacts.

[WayneFerrao]

Reads well and I like the references to the Docusaurus docs!

[alexvy86]

Pretty clear IMO 👍

[Copilot]

Copilot reviewed 1 out of 2 changed files in this pull request and generated 1 suggestion.

Files not reviewed (1)

• .vscode/settings.json: Language not supported

Tip: Copilot only keeps its highest confidence comments to reduce noise and keep you focused. Learn more

[zhenmichael]

Looks good overall! The pubishing pipeline should automatically generate new artifacts in the blob storage the first time a new major version release version is run. As long as the config file is updated the download-apis step should have access the correct artifacts.

[github-actions]

🔗 No broken links found! ✅

Your attention to detail is admirable.

linkcheck output

> fluid-framework-docs-site@0.0.0 ci:check-links /home/runner/work/FluidFramework/FluidFramework/docs
> start-server-and-test "npm run serve -- --no-open" 3000 check-links

1: starting server using command "npm run serve -- --no-open"
and when url "[ 'http://127.0.0.1:3000' ]" is responding with HTTP status code 200
running tests using command "npm run check-links"


> fluid-framework-docs-site@0.0.0 serve
> docusaurus serve --no-open

[SUCCESS] Serving "build" directory at: http://localhost:3000/

> fluid-framework-docs-site@0.0.0 check-links
> linkcheck http://localhost:3000 --skip-file skipped-urls.txt

Crawling...

Stats:
  170006 links
    1595 destination URLs
    1825 URLs ignored
       0 warnings
       0 errors