Split dev-testing docs into own pages#28457
Open
ask-bonk[bot] wants to merge 1 commit intoproductionfrom
Open
Conversation
Co-authored-by: korinne <korinne@users.noreply.github.com>
Contributor
|
This PR requires additional review attention because it affects the following areas: PartialsThis PR updates partial files, which are pieces of content used across multiple files in our Render component.
|
Contributor
|
This pull request requires reviews from CODEOWNERS as it changes files that match the following patterns:
|
Contributor
|
CI run failed: build logs |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Here is a summary of all changes made:
Summary
Split the monolithic Development & Testing overview page into three dedicated pages, making it easier for coding agents and the Cloudflare MCP to fetch specific documentation sections.
New pages created
/workers/development-testing/local-development/- Covers starting a local dev server (Wrangler/Vite), defaults, and how bindings work during local development./workers/development-testing/remote-bindings/- Dedicated page for remote bindings with:remote: true<Details>tab showing all 12 binding types that support remote: AI, Browser Rendering, Images, KV, R2, D1, Queues, Vectorize, Service Bindings, mTLS, Email, and Dispatch Namespaceswrangler dev --remote/workers/development-testing/remote-development/- Legacywrangler dev --remotepage with a prominent caution callout recommending local development + remote bindings instead.Updated overview page
The overview (
/workers/development-testing/) now contains:CardGridwithLinkCardcomponents linking to the three new pagesInternal link updates
Updated 33 references across 25 files:
#remote-bindingsanchor links →/workers/development-testing/remote-bindings/#local-developmentanchor links →/workers/development-testing/local-development/#bindings-during-local-developmentanchor links →/workers/development-testing/local-development/#bindings-during-local-development#using-remote-resources-with-durable-objects-and-workflowsanchor links →/workers/development-testing/remote-bindings/#using-remote-resources-with-durable-objects-and-workflowspublic/__redirectsto point to new pagesValidation
All checks pass:
npm run check(0 errors)npm run lint(clean)npm run format:core:check(clean)bin/validate-redirects.ts(clean)#remote-bindingsor#local-developmentanchorsCloses #28456
github run