docs: rework canonical deployment setups as staged collaboration guide#1347
Merged
rubenfiszel merged 5 commits intomainfrom Apr 11, 2026
Merged
docs: rework canonical deployment setups as staged collaboration guide#1347rubenfiszel merged 5 commits intomainfrom
rubenfiszel merged 5 commits intomainfrom
Conversation
Restructure the canonical deployment setups page into a 4-stage progression (shared workspace → git sync → forks & merge UI → multi-workspace promotion), with each stage additive and a "move up when" section. Add stage pointers from git sync, workspace forks, local development, and the CLI workspaces docs so readers land on the guide from any entry point. Use the unified wmill.yaml `workspaces:` key in all examples. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Clarify the edition requirements for stage 2 of the staged collaboration guide and update the git sync page's pricing note to match. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Deploying windmilldocs with
|
| Latest commit: |
add3190
|
| Status: | ⚡️ Build in progress... |
Link the git sync page back to the local development guide and call out agentic coding tools (Claude Code, Cursor, MCP clients) alongside IDE and VS Code extension as valid local-dev environments. Same update on stage 2 of the collaboration guide. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Forks require no external infrastructure (pure UI workflow, as in the original Setup 1 framing), while git sync adds CI/CD, tokens, and wmill.yaml. Moving forks to stage 2 lets teams add isolation and a review gate without git, then layer git sync on top in stage 3 to gain audit trail, local development, and automatic fork branches. Stage 4 (multi-workspace promotion) still builds on git sync. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Add a callout at the top of stage 2 clarifying that git sync works on a plain shared workspace, so teams can skip forks and go straight to stage 3. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
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
1 participant
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.
Summary
docs/advanced/23_canonical_deployment_setups/index.mdxas a 4-stage progression: Shared workspace → + Git sync → + Forks & merge UI → + Multi-workspace promotion. Each stage is additive and ends with a "when to move up" section. Page retitled to Collaboration and deployment stages and relabeled insidebars.js.git_sync,workspace_forks,local_development,environment-specific-items, andworkspace-managementso readers land on the staged guide from any entry point. Update the collaboration overview page to DocCard into it.wmill.yamlexamples use the unifiedworkspaces:key introduced in windmill#8767 (single-workspace form in stage 2, multi-workspace form in stage 4).Test plan
npm run buildpasses — no new broken anchors, no new warnings (pre-existing broken anchors in/changelog/*and/platform/script-editor*are unrelated to this change)windmill-sync-examplerepo references (push-on-merge.yaml,push-on-merge-to-forks.yaml,open-pr-on-fork-commit.yaml,open-pr-on-promotion-commit.yaml) still match the workflow files in that repo🤖 Generated with Claude Code