docs(architecture): document the two-repo content pipeline#203
Merged
Conversation
Add docs/architecture/two-repo-content-pipeline.md with system diagram, content-flow sequence, asset-flow sequence, and ER-ish content-type relationships. Covers repo boundaries and env var reference. Update README.md (pointer in Documentation section) and docs/architecture/overview.md (intro link). Closes #200.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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/architecture/two-repo-content-pipeline.md— canonical architecture note explaining theposts/websitesplit, with four Mermaid diagrams (system, content-flow sequence, asset-flow sequence, content-type ER)README.md— pointer in the Documentation sectiondocs/architecture/overview.md— intro link to the new pageAcceptance checklist
two-repo-content-pipeline.mdalone can answer: where does content live, where do assets live + how do they reach the website, build-time vs. runtime responsibilities, which repo to PR againstdocs/architecture/*.mdorposts/CONTEXT.mdOut of scope
overview.md/patterns.md/source-tree.mdend-to-endCloses #200.