Repository navigation
Make the site documentation-first with one polished landing page - #72
Merged
Merged
Conversation
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.
The site now has one concise landing page leading into documentation. Docs use a shared site header and outer width, a secondary section bar, and a sidebar limited to the current section, with collapsible groups for larger areas.
Tighten the landing and getting-started copy, render inline code/emphasis/links in authored prose, move contribution guidance into docs, and point the documentation index at canonical docs URLs. Retired marketing pages become static forwarding pages with canonical links and a no-JavaScript fallback; they are excluded from the sitemap. These are HTTP 200 compatibility pages on GitHub Pages, not server-side 301/308 responses.
Includes the requested upgrade of all 17 Askr packages to published 0.5.0, compatible Monaco/OpenTelemetry peers, the lockfile, and regenerated API/CLI snapshots. A lightweight generated prop index keeps the full API snapshot out of the initial route bundle while making the page outline match visible props sections. Vite Plus's current formatter also normalizes existing whitespace in AUDIT_REPORT.md.
Validation:
npm ciand fullnpm run check: format, lint, typecheck, 42 unit tests, 22 Chromium tests, and the production build passed.