Open
Conversation
|
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
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.
This pull request refactors the documentation structure to clearly separate framework development docs (for contributors) from user docs (for end users). All contributor-facing technical documentation has been moved from the
dev-docs/directory to a newframework-docs/directory, with all references and cross-links updated accordingly. User guides remain indev-docs/. This improves clarity, onboarding, and maintenance for both contributors and users.Documentation structure refactor:
dev-docs/toframework-docs/, with all references, checklists, and cross-links updated throughoutAGENTS.md,DOCUMENTATION.md, and related files. [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] [12]Content pipeline update:
Quick links and onboarding improvements:
framework-docs/) and user docs (dev-docs/). [1] [2] [3] [4]Naming conventions and organization:
Progress log and architecture decision references:
framework-docs/paths and templates. [1] [2] [3] [4]