Repository navigation
feat(docs): add complete Radi reference and automatic Pages deployment - #62
Merged
Merged
Conversation
Marcisbee
marked this pull request as ready for review
October 22, 2026 15:41
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.
Build the Radi documentation site with Radi static generation, complete API references, system dark mode, mobile navigation, and generated Markdown and llms.txt for agent readers. The design is approved.
Build the documentation with deno task docs:build on pull requests and pushes to master. Successful master builds publish dist/docs through GitHub Pages. Pull requests cannot deploy. Manual runs from master are supported. GitHub Pages is configured for Actions and retains radi.js.org.
Deployment does not install Playwright or run browser tests. The existing docs interaction test remains available locally.
Validation: docs build and actionlint pass. Current master is incorporated. The first production deployment runs after merge; failed builds leave the previous site live.