The website of flashtrace - a landing page plus
documentation rendered from the tool repository's docs/, served by GitHub Pages at
flashtrace.github.io.
Built in the flashtrace spirit: plain static HTML/CSS/JS, no runtime framework, and a single build-time dependency (marked).
build.mjsreads the tool repository'sdocs/(nav order derived fromdocs/index.md), renders every page throughmarked, rewrites inter-doc links to clean URLs and emits a fully static site intodist/.- The landing page (
src/landing.mjs) is hand-written HTML: a CSS-only IDE mock in the hero, feature grid, curated interactive examples (src/examples.mjs, captured from realflashtraceruns) and the install snippets. .github/workflows/deploy.ymlbuilds and deploys on every push tomain, on manualworkflow_dispatch, and on arepository_dispatchof typeflashtrace-releasethat the tool repository fires after each release. Docs are always checked out at the release tag (from the dispatch payload, or the latest release otherwise) - the site documents released behavior, notmain.
git clone https://github.com/flashtrace/flashtrace ../flashtrace # docs source, once
pnpm install
pnpm build # emits dist/
pnpm dev # build + watch + serve on http://localhost:8788The docs directory is resolved in this order: $FLASHTRACE_DOCS → ./flashtrace/docs
(the CI checkout location) → ../flashtrace/docs (local sibling checkout). Set
FLASHTRACE_REF to override the version label rendered in the header and footer.
dist/ is never committed; CI builds it fresh on every deploy.
Apache 2.0, like flashtrace itself.