feat(docs): publish raw markdown route companions#870
Merged
Conversation
Expose authored docs markdown alongside the rendered documentation so users and agents can fetch the same deployed content without scraping HTML. The files are copied from the public docs build input after Zensical renders, which keeps internal maintainer docs out of the published site and keeps markdown tied to the deployed commit.
roborev: Combined Review (
|
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.
Expose raw authored markdown alongside the rendered docs so users and agents can fetch deployed documentation without scraping HTML or depending on GitHub raw URLs. The markdown files are copied from the same public docs input used for the rendered site, which keeps internal maintainer docs excluded and keeps
.mdresponses tied to the deployed commit.The built-site validation now treats markdown companions as part of the public docs contract, so future docs route changes cannot silently omit the agent-friendly form.