feat: add on-site documentation and fix navigation#1
Conversation
Move all documentation on-site instead of linking back to GitHub. Update nav, hero, and footer links to point to local doc pages. Add docs landing page and 10 synced documentation articles.
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 052d0fe863
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
|
|
||
| ## Full Documentation | ||
|
|
||
| For complete documentation including theme customization, template overrides, and advanced features, see [docs/blog/README.md](README.md). |
There was a problem hiding this comment.
The Full Documentation link targets README.md, but there is no content/docs-blog/README.md (or corresponding routed page), so users on /docs/blog/ will hit a 404 when they click it. Since this section is presented as the next step for advanced usage, it should link to a valid on-site URL (or a concrete GitHub URL) instead of a missing relative file.
Useful? React with 👍 / 👎.
|
|
||
| ### AI Assistants | ||
|
|
||
| For detailed skill documentation, see [`.agent/skills/hype/`](.agent/skills/hype/). |
There was a problem hiding this comment.
.agent docs link from quick reference
This link points to .agent/skills/hype/, but that path is not present in this repository and will not exist in the generated site, so it resolves to a dead link for readers of /docs/quick-reference/. Replacing it with a real public docs location avoids sending users to an unreachable internal path.
Useful? React with 👍 / 👎.
1 participant
Summary
/docs/with links to all documentation sections/getting-started/instead of GitHubNav structure
Test plan
/docs/renders the docs landing pagehype blog buildsucceeds with no warnings