Publish docs Markdown source files#930
Merged
Merged
Conversation
LLM and agent consumers get cleaner, lower-noise input from source Markdown than from rendered HTML, but the docs deployment only published the rendered Zensical pages. Mirroring the kata docs pattern makes each public docs page available from the same deployment as its HTML route and keeps validation in the docs check path so stale or missing source files are caught before deployment. Generated with Codex Co-authored-by: Codex <codex@openai.com>
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.
LLM and agent consumers get cleaner input from the source Markdown than from rendered HTML, but roborev.io only published the rendered Zensical routes. This mirrors the kata docs deployment pattern so public docs pages can be fetched from stable
.mdURLs, such as/changelog.mdnext to/changelog/and/index.mdnext to the landing page.The landing page now tells programmatic readers to prefer those source-form URLs, and the docs build/check path verifies that generated deployments include matching Markdown files and do not redirect
.mdroutes away from static source content.