Fix docs home header/nav/footer to match rebuilt site pattern#258
Merged
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.
Motivation
public/docs.htmluse the same header, Docs dropdown, and grouped footer pattern as the rebuilt canonical pages so the Docs Home visually matches other site pages.Description
public/docs.htmlto load/css/site.cssand adjusted the inline header/nav CSS to match the canonical pattern used bypublic/docs/wrap-your-agent.htmlandpublic/verify.html..brand span{display:none}style so only the logo image is visible in the header.Docs ▾active label linking to/docs.html, dropdown menu behavior, and addedaria-haspopup="true").public/docs.htmlwith the canonical 3-column grouped footer (.footer-grid) and spacing to restore grouped columns (Product / Developers / Proof).Testing
npm installin the repo which completed successfully.npm testand all unit tests passed (26 passed, 0 failed).npm run buildbut the repo has nobuildscript (script missing error).examples/webhook-auto-verifywithnpm installandnpm run check, which completed successfully.Codex Task