Repository navigation
fix(site): project homes go straight to their What-is pages - #447
Merged
Merged
Conversation
ykiko finds the synced project home pages (a hero and feature cards) not worth showing: /clice/, /catter/, /xclang/ and their zh twins now redirect to guide/what-is-<project>. The built page refreshes there before showing anything (GitHub Pages has no redirects) and names it as canonical; the theme redirects navigation within the site and the dev server's first load. The nav links to the What-is pages and stays lit anywhere in its project; the sitemap leaves the homes out. The strip of the homes' hero art goes: nothing of those pages shows any more.
16bit-ykiko
added a commit
that referenced
this pull request
Nov 15, 2026
Asked by ykiko: drop the Codex-drawn icons and use something else. clice's Command Line section (new in the 1.0 docs) had no icon at all, nor catter's Scripting or xclang's Build Systems and Reference. - `sidebar.ts`: every sidebar section gets an inline line icon on the 24 px grid, stroked in the theme's blue like the portal page's project icons — signpost (guide), toolbox (features), terminal (cli), page of code (scripting), plug (integrations), book (reference), drafting compass (design), wrench (dev). - `public/icons/` is deleted: the four chapter illustrations and the clice/catter feature icons, which only the project homes used (they redirect since #447). Checked: the 14 sections of clice, catter and xclang in light and dark; no built page names `/icons/`; `npm run build` passes. The mascot art (logo, footer, 404, empty search, portal figure) stays.
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.
Asked by ykiko: the project home pages (synced from each repo: a hero and feature cards) aren't worth showing; open each project on its "What is" page instead.
/clice/,/catter/,/xclang/and/zh/…redirect to<project>/guide/what-is-<project>. GitHub Pages has no server redirects, so the built page carries<meta http-equiv="refresh" content="0; url=…">and a canonical link to the target, and renders nothing of the home meanwhile (frontmatter replaced, search off). The theme redirects navigation within the site (router.onBeforeRouteChange) and the dev server's first load.activeMatch).Checked on the production build (
vitepress preview): direct visits to all five homes land on the What-is pages; clicking xclang in the nav and an in-site link to /catter/ too; the nav item stays lit.npm run buildpasses; the section-link check passes.