refactor: Rename "docs" directory to "website"

[Josmithr]

In preparation to add repo "wiki" documentation under a directory called "docs".

[github-actions]

Hi! Thank you for opening this PR. Want me to review it?

Based on the diff (134 lines, 207 files), I've queued these reviewers:

• Correctness — logic errors, race conditions, lifecycle issues
• Security — vulnerabilities, secret exposure, injection
• API Compatibility — breaking changes, release tags, type design
• Performance — algorithmic regressions, memory leaks
• Testing — coverage gaps, hollow tests

How this works

• Adjust the reviewer set by ticking/unticking boxes above. Reviewer toggles alone don't trigger anything.

• Tick Start review below to dispatch the review fleet.

• After review finishes, tick Start review again to request another run — it auto-resets after each dispatch.

• This comment updates as new commits land; your reviewer selections are preserved.

• Start review

[alexvy86]

Not necessarily for this PR but maybe this label should change too?

[Josmithr]

I was actually assuming this would expand to include things we put under the new docs directory. So this would be reviewers of any documentation content (versus the website one above). Or maybe we would want those to be distinct. But yeah, probably a conversation for the future.

[alexvy86]

Nit: would love to rename this file too but that's a bit more intricate; I think we'd have to create the new file as a copy, go to ADO and re-point the pipeline, then delete the old file. Not sure how it would impact branches other than main... we don't tend (should?) touch the docs(website) folder in other branches, right?

[Josmithr]

Yeah, fair point. I think I would prefer to do that as a separate PR, but probably worth doing.

Not sure how it would impact branches other than main... we don't tend (should?) touch the docs(website) folder in other branches, right?

We shouldn't be making website changes on other branches - those changes wouldn't go anywhere. But I don't know if we currently build on those branches or not. Would need to be verified.

[github-actions]

🔗 No broken links found! ✅

Your attention to detail is admirable.

linkcheck output

> fluid-framework-website@0.0.0 ci:check-links /home/runner/work/FluidFramework/FluidFramework/website
> 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-website@0.0.0 serve
> docusaurus serve --no-open

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

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

Crawling...

Stats:
  290871 links
    1933 destination URLs
    2183 URLs ignored
       0 warnings
       0 errors

[Copilot]

Copilot reviewed 10 out of 207 changed files in this pull request and generated no comments.

[github-actions]

🔗 No broken links found! ✅

Your attention to detail is admirable.

linkcheck output

> fluid-framework-website@0.0.0 ci:check-links /home/runner/work/FluidFramework/FluidFramework/website
> 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-website@0.0.0 serve
> docusaurus serve --no-open

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

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

Crawling...

Stats:
  290871 links
    1933 destination URLs
    2183 URLs ignored
       0 warnings
       0 errors