Skip to content

Add the Hypercmd landing page and Markdown docs - #2

Merged
andreespirela merged 1 commit into
mainfrom
codex/landing-and-docs
Oct 4, 2026
Merged

andreespirela merged 1 commit into
mainfrom
codex/landing-and-docs

Conversation

@andreespirela

Copy link
Copy Markdown
Contributor

Hypercmd needs a landing page and browsable documentation while keeping the terminal crates independent of the browser apps. This adds a separate Cargo workspace under apps/, with the landing page at / and shared docs-base documentation at /docs/.

  • Render five interactive examples from the same HTML shown in the editor, using Hypercmd's actual layout and event handlers. Include installation, quick start, Docs, GitHub and X links, immediate transitions and reduced-motion support.
  • Serve the Markdown guides and their original source, with CLI and HTML/CSS references, consistent typography, search, theme switching and responsive navigation. Pin docs-base through Git.
  • Add just site / just preview and a manual Vercel deployment workflow for production or preview. Ignore generated output and local deployment credentials, and remove the tracked IDE metadata.
  • Use a browser-compatible clock when mounting Hypercmd examples in Wasm; native builds keep std::time::Instant.

Based on current main after #1. Its editor implementation is not repeated in this diff, and the rewritten controls guide retains its completion APIs.

Validation:

  • just check passed: formatting, workspace and consumer tests, Clippy, rustdoc, generated CLI app, offline package consumption and Rust 1.85, including both web apps.
  • just browser passed: shared component behavior, all five interactive examples, all nine guides, Markdown downloads, responsive layouts and combined-site navigation/deep links.
  • just landing-browser passed after adding the GitHub destination assertion.
  • just site passed with production output for both apps.
  • Actionlint passed for the check and deployment workflows; git diff --check passed, and no ignored artifacts are tracked.

The docs Clippy failure was reproduced before changing its template inclusion. Both web apps use Hypercmd's documented, narrowly scoped generated-template expectation for Fusor #17; the upstream issue remains open. No lint thresholds or CI gates were weakened.

The deployment workflow has not been run from this branch. VERCEL_TOKEN is configured in the vercel environment; merging does not deploy automatically.

@andreespirela
andreespirela merged commit 0b60751 into main Oct 4, 2026
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant