feat(website): Add v1 marketing site and bilingual docs portal#283
Open
darion-yaphet wants to merge 40 commits intotw93:mainfrom
Open
feat(website): Add v1 marketing site and bilingual docs portal#283darion-yaphet wants to merge 40 commits intotw93:mainfrom
darion-yaphet wants to merge 40 commits intotw93:mainfrom
Conversation
Owner
|
@darion-yaphet Welcome to submit the code you think is good directly. |
darion-yaphet
changed the title
darion-yaphet
force-pushed
the
web-ui
branch
2 times, most recently
from
e6c4137 to
88fb01d
Compare
Brainstormed design for Kaku's official website: landing page + docs site built with Astro + Starlight, deployed to GitHub Pages. Terminal Hacker visual tone, zh-CN primary with EN toggle. Covers IA, 9-section homepage, docs structure, /roadmap, /changelog, and explicit out-of-scope items.
- Create SiteNav.astro with sticky nav, brand, lang switch (zh/en), and GitHub link - Harden all external links in SiteFooter.astro with target="_blank" rel="noopener noreferrer" (6 links: GitHub, Issues, Twitter, WezTerm, License, 作者) - Add <meta name="color-scheme" content="dark"> to LandingLayout.astro head
Create src/pages/index.astro composing Hero, TerminalDemo, FeatureGrid, AIShowcase, MigrateTabs, ScreenshotGallery, QuickStart, WhyKaku, and FAQ under LandingLayout. Astro page routing takes precedence over Starlight's content collection, so the landing lands at / with no route conflict; Starlight docs/index.mdx is untouched and remains for Task 4.1.
Replace placeholder index.mdx with a Starlight splash page using CardGrid + LinkCard components, offering six user-goal pathways.
Move src/content/docs/index.mdx to src/content/docs/docs/index.mdx so Starlight routes the docs landing to /docs/ instead of conflicting with /en/ due to the root locale + custom landing page at /. Update all LinkCard and hero action hrefs to include the /Kaku/ base path since Starlight does not auto-prepend the Astro base to user- supplied href attributes in MDX content.
… /docs/ Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
…gnore) Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Owner
|
@darion-yaphet thanks, I really want this! Could you start by adding real screenshots (feel free to check my Twitter @HiTw93 for inspiration on framing) and fleshing out the docs content? We'll tackle the rest together over the weekend. |
Author
I have recently checked and fixed the issue of comparing the Chinese and English versions, but I feel that the content is still not detailed enough. Can I directly post the screenshot in the comments section on GitHub? |
Author
|
The sample web page has been deployed at: https://darion-yaphet.github.io/Kaku/ You can preview it here @tw93 |
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
2 participants
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.
Here's the English translation:
What this PR does
Launches the official v1 website for Kaku Terminal — a Terminal Hacker–styled landing page plus a bilingual documentation site built on Starlight. Tech stack: Astro + Starlight, deployed to GitHub Pages.
What's included
Landing page (9 sections)
Secondary pages
/download— DMG / Homebrew / build-from-source installation methods/roadmap— three-phase roadmap (Now / Next / Later, data-driven)/changelog— static version historyDocumentation site
/docs/task-oriented entry point (5 LinkCards)Bilingual i18n
/en/Global a11y hardening
:focus-visiblekeyboard focus ring<nav>witharia-label="Primary"hreflang+aria-labelaria-hidden="true"target="_blank" rel="noopener noreferrer"aria-labelsummaryCI / Deployment
.github/workflows/deploy-website.yml— automatically builds and deploys to GitHub Pages on push tomainorweb-uiwhen changes touchwebsite/**Tests
Visual direction
Terminal Hacker dark theme:
#0a0a0ablack#00ff9fneon green#ffffffpure white~/kaku $ ...–style CLI promptNotable engineering decisions
@astrojs/sitemappinned to3.2.1(viapnpm.overrides) — versions 3.7+ invoke a hook that only exists in Astro 5, which crashes Astro 4 builds. This is documented in a comment at the top ofastro.config.mjs; remember to remove the override when upgrading to Astro 5.src/content/docs/docs/...(not Starlight's defaultsrc/content/docs/...) — becausesrc/pages/index.astrooccupies the/Kaku/root route as the landing page, and Starlight's default behavior would mount content at the root as well, causing a conflict. The subdirectory approach cleanly places docs at/Kaku/docs/./blogand/showcaseare not implemented./showcasemay be added in v2 (open community screenshot submissions).Validation status
✅ Passing:
pnpm build— 46 pages build cleanlypnpm test:smoke— Playwright 2/2 pass/Kaku/href links⏳ 4 items requiring manual confirmation before merge:
website/public/shots/are all copies ofassets/kaku.jpgDocumentation index
The full design spec and implementation plan are committed in this PR:
docs/superpowers/specs/2026-04-14-kaku-website-design.md— 12-section design document (IA / landing page 9 sections / docs area / color system / i18n / YAGNI cuts / risks, etc.)docs/superpowers/plans/2026-04-14-kaku-website.md— 23-task phased implementation planWould you like me to replace the PR body with this summary? I can run
gh pr edit web-ui --bodyto update it directly.