docs(#1279): add install mode decision point before commands#1592
Open
fullsend-ai-coder[bot] wants to merge 1 commit into
Open
docs(#1279): add install mode decision point before commands#1592fullsend-ai-coder[bot] wants to merge 1 commit into
fullsend-ai-coder[bot] wants to merge 1 commit into
Conversation
The install guide previously presented org-wide installation as step 1, with per-repo installation buried as a subsection after all 6 org-wide steps. Users in shared-org scenarios would follow the guide top-to-bottom, run the org-level command, and create an unwanted .fullsend config repo before discovering the per-repo option. Add a "Choose your installation mode" section after Prerequisites that presents a comparison table (per-repo vs per-org), guidance on when to use each mode, and links to the relevant section. This gives users the decision point they need before running any install commands. Also restructure the document hierarchy: org-wide steps now live under a "Per-org installation" heading, parallel to the existing "Per-repo installation" section, making both modes first-class paths. Closes #1279
Site previewPreview: https://3e9bcdff-site.fullsend-ai.workers.dev Commit: |
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.
The install guide previously presented org-wide installation as step 1, with per-repo installation buried as a subsection after all 6 org-wide steps. Users in shared-org scenarios would follow the guide top-to-bottom, run the org-level command, and create an unwanted .fullsend config repo before discovering the per-repo option.
Add a "Choose your installation mode" section after Prerequisites that presents a comparison table (per-repo vs per-org), guidance on when to use each mode, and links to the relevant section. This gives users the decision point they need before running any install commands.
Also restructure the document hierarchy: org-wide steps now live under a "Per-org installation" heading, parallel to the existing "Per-repo installation" section, making both modes first-class paths.
Closes #1279
Post-script verification
agent/1279-install-docs-decision-point)e2721e94741317e30ffd4514724e1a7f01b11e4e..HEAD)