Migrate the landing page to React (keep docs & blog on MkDocs)#3980
Draft
peterschmidt85 wants to merge 10 commits into
Draft
Migrate the landing page to React (keep docs & blog on MkDocs)#3980peterschmidt85 wants to merge 10 commits into
peterschmidt85 wants to merge 10 commits into
Conversation
…on MkDocs
Migrates the marketing landing from the MkDocs `home.html` template to the React app
from landing-v2, while docs and blog stay on MkDocs. Same single-origin URL structure:
`/` = React landing, `/docs` + `/blog` = MkDocs.
- website/: the Vite + React landing (copied from landing-v2), made integration-ready:
- vite assetsDir -> website-assets/ and public/ -> public/static/ so the build can be
overlaid onto the MkDocs site/ without colliding with MkDocs's /assets/ tree
- app owns only `/` (dropped the /old and /blog routes and the SPA 404.html copy)
- docs/blog/terms/privacy links are same-origin (configurable via VITE_DOCS_BASE)
- scripts/docs/build_site.sh: build landing + `mkdocs build` + overlay -> ./site
- .github/workflows/site.yaml: build + cross-repo Pages deploy (adapts docs.yaml;
inputs allow deploying to a staging Pages repo)
- just recipes: website-dev, website-build, site-build, site-serve
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
…e.yaml Fold the landing build + overlay into the reusable build-docs.yml (now builds the full site via scripts/docs/build_site.sh) instead of a separate parallel workflow: - build-docs.yml: add Node setup and run build_site.sh (landing + mkdocs + overlay). Consumed by both docs.yaml (deploy) and build.yml (PR build check), so the landing now also gets validated on PRs. - docs.yaml: unchanged behavior; renamed to "Build & Deploy Site" since it now ships the landing too. Still cross-repo deploys to dstackai.github.io. - Remove the standalone site.yaml that was only used to drive the peterschmidt85 staging experiment. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Restore src/pages/Old and its wiring (the /old route, the App layout context it uses, the top-nav drawer trigger, and the Cloudscape placeholder images). It stays reachable in dev (`npm run dev` at /old) as a starting point for product pages; in production this app owns only `/`, so MkDocs serves everything else. Same-origin docs/blog link changes are preserved. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
The landing ("/") is now the React app in website/. When the docs are served on their own
(`mkdocs serve`), index.md now redirects to /docs/ via a small redirect.html template, and
the 52KB home.html landing template is removed. In the combined build the React index.html
overlays this, so the redirect never ships to production. index.md keeps a title/description
so the social plugin still generates the home card the landing reuses as its OG image.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
The landing is now a separate React app, so it needs its own analytics and share metadata that the MkDocs theme used to provide. Add the GA4 tag (same property as the docs/blog, G-JX21114P7B; skipped on localhost so dev doesn't pollute the property), a proper title and description, canonical/favicon, and Open Graph + Twitter tags. The OG image reuses the card the MkDocs social plugin generates for the home page (assets/images/social/index.png). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Keep DOCS.md focused on the docs, but note the site now has three parts (landing/docs/blog), how to preview the landing (just website-dev) and build everything (just site-build), and that `mkdocs serve` alone redirects / to /docs. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Restructure the footer into a brand block (logo + GitHub/Discord/X/LinkedIn icons) and content-width link columns (Documentation, Examples, Community, Company), mirroring dstack.ai. Columns sit flush to the right edge on desktop, stack below the brand under 1100px, and drop to a clean 2-up grid on phones. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
mkdocs/overrides/assets/images/quotes/ was used only by the old landing template (overrides/home.html), which was dropped during the React landing migration. Nothing references these images anymore; the React landing keeps its own copies under website/public/static/quotes/. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Theme Cloudscape through its official applyTheme token API (cloudscape-theme.ts): square corners, text-color hairline borders, dark filled primary buttons, transparent outlined normal buttons, Geist fonts, and faint theme-aware hovers. The few details Cloudscape doesn't expose as tokens (0.5px border widths, text-color tab dividers/underline, the flat 300px Get-started popup, FAQ hover) are isolated in cloudscape-overrides.css with a maintenance header. - Nav: restructure the Get-started dropdown (Products/Login groups, descriptions, right-aligned external icons, segment divider); slightly larger menu buttons. - Home: new hero copy; AI-native cards become clickable link-cards with an arrow; add section CTAs (Backends, Kubernetes/SSH Fleets, Sign up); trim the GPU list; dotted testimonial borders; CEO @ Graphsignal. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
- Top nav: replace the standalone Blog link with a hover-opening "Resources" dropdown (Case studies / Benchmarks / Blog); mirror it as an expandable section in the mobile SideNavigation. - Dropdown popups: larger, consistent group-header/item label sizing, label/description spacing, and top/bottom breathing room that a first/last item's hover fill covers (fixes the dark-mode border being painted over). - Unify the hover tint across normal buttons, cards, and dropdown items via a single --cs-hover variable. - Footer column links now match the column heading size. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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
1 participant
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.
What
Replaces the MkDocs
home.htmllanding with the React app fromlanding-v2(now inwebsite/), while docs and blog stay on MkDocs. Same single-origin URL structure:/→ React landing (new)/docs,/blog→ MkDocs (unchanged)How it fits together
website/— the Vite + React landing. ViteassetsDiriswebsite-assets/and public files live underpublic/static/, so the build overlays onto the MkDocssite/without colliding with MkDocs's/assets/. The app owns only/;/oldis kept as a template for future product pages (dev-reachable, not in the production deploy).scripts/docs/build_site.sh— builds the landing +mkdocs build, then overlayswebsite/distontosite/.build-docs.ymlnow builds the combined site (so the landing is also validated on PRs);docs.yaml("Build & Deploy Site") deploys it via the unchanged cross-repo push. No separate/parallel workflow.index.mdredirects to/docs/for localmkdocs serve(the Reactindex.htmloverlays it in the real build, so the redirect never ships).G-JX21114P7B, skipped on localhost) and OG/Twitter metadata, reusing the MkDocs-generated home social card.Local dev
just website-dev(http://127.0.0.1:5173)just mkdocs-serve(http://127.0.0.1:8000, unchanged)just site-build && just site-serve(http://127.0.0.1:8001)Tested
Built and deployed end-to-end to a staging Pages site that mirrors
dstackai.github.io → dstack.ai: https://peterschmidt85.github.io/. Verified/,/docs,/blog, a blog post, cross-links, GA, and OG. Both a static deploy and the adapted workflow running in real GitHub runners produced identical output.Notes / follow-ups
website/src/styles.css(e.g..site-menu-button); left as-is to keep this diff focused.dstackai/dstack's deploy at this workflow; the docs/blog content andCNAMEare unchanged.🤖 Generated with Claude Code