Add a GitHub Pages splash for augment-it
A small Astro site at splash/ that ships to GitHub Pages on push to main, renders the repo's changelog/ and context-v/ alongside curated copy about the six module-federated microfrontends.
Why Care?
augment-it now has a public face. Before this, the only artifact a visitor
could land on was the repo README, which describes the tech stack but not
the shape of the workshop. The splash exists so a stranger can land at
lossless-group.github.io/augment-it/ and understand — within fifteen
seconds — what the six microfrontends are, what they do together, and
where the project actually lives.
It's also where the repo's changelog/ and context-v/ get rendered.
Versioned context becomes legible to someone who doesn't have the repo
checked out.
What's New?
splash/— an Astro Knots site, single-project variant. base/augment-it/, vibrant default mode, magenta-violet brand spine lifted from the wordmark gradient.The hero is a module-federation manifest: a 2×3 grid of the six microfrontends as primary content. No traditional centered headline + diagram pair. A pipeline rail below names the flow order (record → prompt → request → response → highlight → insight).
Pagefind wired by default — header search popover with
/keyboard shortcut, full/searchpage, token-driven UI overrides that pivot through vibrant/dark/light modes.Sort controls on
/changelog/and/context-v/with per-pagelocalStoragepersistence, server-pre-sorted to match the UI default.Lenient content schemas + defensive
toDate(unknown)helper — schemas never throw, render code never crashes on legacy entries..github/workflows/pages.ymldeploys on push tomainusingactions/deploy-pages@v4andactions/configure-pages@v5withenablement: trueso Pages bootstraps itself on first run.changelog/andcontext-v/scaffolded at the repo root per the universal-directory convention.
