[Durable Objects] restructure docs around Diátaxis framework#28345
[Durable Objects] restructure docs around Diátaxis framework#28345elithrar wants to merge 7 commits intoproductionfrom
Conversation
|
This PR requires additional review attention because it affects the following areas: RedirectsThis PR changes current filenames or deletes current files. Make sure you have redirects set up to cover the following paths:
PartialsThis PR updates partial files, which are pieces of content used across multiple files in our Render component.
|
|
This pull request requires reviews from CODEOWNERS as it changes files that match the following patterns:
|
…orrect sidebar order
…em, split merged steps
61c33db to
3dd50ef
Compare
|
CI run failed: build logs |
|
/bonk fix it |
Co-authored-by: elithrar <elithrar@users.noreply.github.com>
|
Fixed. The link in |
|
/bonk update the PR description with the latest changes to this structure. Highlight any drift in your comment. |
|
Updated PR #28345 description with the audited structure. Here is the drift I found between the original description and the actual files on the branch:
The new PR description includes the full tree with sidebar orders, a redirect table, and all drift items highlighted in their own section. |
Closes #28344
Structure (Diátaxis framework)
Content movements
best-practices/*dissolved — 4 how-to pages moved tohow-to/, rules page moved toconcepts/(content refreshed with updated examples)reference/*dissolved — 3 how-to pages moved tohow-to/, 3 reference pages moved toplatform/, 1 explanation page (in-memory-state) merged intoconcepts/how-durable-objects-workexamples/testing-with-durable-objects→how-to/test-durable-objects(it is a how-to, not an example)examples/alarms-apicontent merged into newhow-to/use-alarmsconcepts/what-are-durable-objects+concepts/durable-object-lifecycle+reference/in-memory-statemerged into newconcepts/how-durable-objects-workdurable-objects-rest-api.mdxmoved intoapi/rest-api.mdx(now an external_link redirect to the API docs)pcx_content_typechanged fromconcepttoreferenceTypeScriptExample, with typedDurableObject<Env>, RPC methods, andthis.ctx.storage<Steps>build error inobservability/metrics-and-analyticsRedirects
All old paths have 301 redirects in
public/__redirects:/durable-objects/best-practices//durable-objects/how-to//durable-objects/best-practices/access-durable-objects-storage//durable-objects/how-to/access-storage//durable-objects/best-practices/create-durable-object-stubs-and-send-requests//durable-objects/how-to/invoke-methods//durable-objects/best-practices/websockets//durable-objects/how-to/use-websockets//durable-objects/best-practices/error-handling//durable-objects/how-to/handle-errors//durable-objects/best-practices/rules-of-durable-objects//durable-objects/concepts/rules-of-durable-objects//durable-objects/reference//durable-objects/concepts//durable-objects/reference/durable-objects-migrations//durable-objects/how-to/configure-migrations//durable-objects/reference/data-location//durable-objects/how-to/configure-data-location//durable-objects/reference/environments//durable-objects/how-to/use-environments//durable-objects/reference/in-memory-state//durable-objects/concepts/how-durable-objects-work//durable-objects/reference/data-security//durable-objects/platform/data-security//durable-objects/reference/faq//durable-objects/platform/faq//durable-objects/reference/glossary//durable-objects/platform/glossary//durable-objects/reference/durable-object-gradual-deployments//durable-objects/how-to/gradual-deployments//durable-objects/concepts/what-are-durable-objects//durable-objects/concepts/how-durable-objects-work//durable-objects/concepts/durable-object-lifecycle//durable-objects/concepts/how-durable-objects-work//durable-objects/examples/testing-with-durable-objects//durable-objects/how-to/test-durable-objects//durable-objects/examples/alarms-api//durable-objects/how-to/use-alarms//durable-objects/durable-objects-rest-api//durable-objects/api/rest-api/Drift from original PR description
The following items differ from the original PR description tree:
rules-of-durable-objects.mdxcontent was refreshed, not "unchanged" as originally stated — the diff shows 343 additions / 326 deletionsapi/rest-api.mdxis an external_link stub, not a moved content page — it redirects to/api/resources/durable_objects/how-to/gradual-deployments.mdxis an external_link stub, not a moved content page — it redirects to the Workers gradual deployments pageapi/webgpu.mdxretainspcx_content_type: configuration, not changed toreferencelike the other 9 API pagestutorials/sidebar order is 9 (not mentioned in original) — same asplatform/(order 9), which means they rely on alphabetical tiebreakingapi/base.mdxandapi/container.mdxboth havesidebar.order: 1— potential ordering collisionexamples/has 9 files (7 examples + 1 index + 1 external_link), not just the "unchanged minus alarms-api, testing" described — the original description omitted listingreference-do-name-using-init.mdx,readable-stream.mdx,agents.mdxobservability/sidebar order is 8 — the original description said "was 7" but the actual previous order was also 7, making the change 7→8 (confirmed correct)/durable-objects/what-are-durable-objects/still points to/durable-objects/concepts/what-are-durable-objects/(line 585) which itself redirects to/durable-objects/concepts/how-durable-objects-work/— this is a redirect chain, not a direct redirectNotes
tutorials/(order 9) andplatform/(order 9) share the same sidebar order — platform sorts after tutorials alphabeticallyapi/base.mdxandapi/container.mdxboth havesidebar.order: 1— container may need its own ordergradual-deployments.mdxandrest-api.mdxare external_link stubs, not standalone content pageswebgpu.mdxretainspcx_content_type: configuration(not changed toreferencelike the other API pages)Stats
durable-objects/tree