EP v2 docs: reduce content-repo onboarding confusion#4282
Merged
Conversation
- Access/Local preview: make the /path/to/repo and <app-slug> placeholders explicit, add a filled-in example, and document the 'content path does not exist' error - Troubleshooting: add 'Updated main but customers still see old content' (nearest-lower-semver stray branch) and the preview path-placeholder error - Connect a Git Repo: add the actual git workflow for adopting template updates (no shared history -> upstream remote + checkout), clarify the banner is an informational feed and Mark reviewed only clears it - Manage Content Versions: add an opinionated default (main-only unless docs diverge; avoid stray version branches) Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
✅ Deploy Preview for replicated-docs-upgrade ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for replicated-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
github-actions
Bot
added
type::docs
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
…d-docs note - Access: break the preview command and example across lines with backslash continuation (matches the curl pattern in enterprise-portal-v2-vendor-api-automation) so the full command shows on narrow screens - Revert the added note on Manage Content Versions per review Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
NoaheCampbell
approved these changes
Jul 20, 2026
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
2 participants
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.
Preview links
What
Documentation improvements targeting recurring points of confusion for vendors setting up an Enterprise Portal v2 content repo.
/path/to/repoand<app-slug>placeholders, add a filled-in example, and document thecontent path does not existerror (vendors run the example command verbatim).git pull/mergedon't work — addupstreamremote,git checkout upstream/main -- <files>); clarify the banner is an informational feed and Mark reviewed only clears it.Why
Based on real onboarding friction: placeholder commands run literally,
mainsynced but a stray version branch still serving old content, and the template-update flow assuming knowledge of how to bring changes into a diverged repo.There are a few small UI improvements stories created as well, but this handles the docs side