SubZeroDev.Platform.UI.LandingPage

A static landing-page toolkit for repositories that want a README-driven home page, a changelog route, optional full CSS control, and an auditable GitHub Pages deployment path.

Quick start

npm install --save-dev [email protected]
subzerodev-platform-ui-landing-page build

The default inputs are README.md, CHANGELOG.md, optional site/README.md, optional site/theme.css, and optional site/public/. The build writes site/dist/ with / and /changelog/.

Custom adapter

Existing frontend sites can export defineLandingPage(...) from site/landing.config.ts. Each route declares static metadata and exactly one of entry and body. In addition to the required title and description, route metadata can carry canonical, Open Graph, X/Twitter, icon, theme-colour and <noscript> values; the adapter emits only the optional fields declared by that route.

An entry route names a module, and its document is the toolkit shell — <div id="root"></div> plus a module script — with hydrate available for a server-rendered mount. A body route supplies the document body itself; that markup is emitted verbatim, no script is emitted, and the built page loads nothing. A body route may also declare a stylesheet, which is emitted as a <style> element in the head, since <style> is not valid in the body.

export default defineLandingPage({
  routes: [
    {
      path: "/",
      body: "<main><h1>Composed at build time</h1></main>",
      stylesheet: "main { font: 1rem/1.5 system-ui; }",
      metadata: { title: "Home", description: "A page that loads no script." },
    },
  ],
});

Development

npm install
npm run check

Compatibility

Generic-site DOM selectors and CSS custom properties beginning szd- are the public styling contract. During 0.x, consumers pin exact package versions and workflow SHAs. A later 1.0.0 will use semantic-versioning major releases for breaking CSS or DOM changes.