Full-bleed hero
The first screen acts like a poster, not a dashboard.
What this example shows
One strong visual idea, then clear structure.
This sample is intentionally simple: one HTML file, no build step, responsive layout, and enough motion to prove the page is alive without turning it into a toy.
Reusable static output
It is already deployable through GitHub Pages with your existing script.
Team-friendly structure
Anyone with repo access can publish a new folder under the shared Pages site.
Selected flow
Publish rhythm for small frontends.
Keep the source page simple, publish to one slug, then let the repo landing page become the directory for everything you ship.
- Prepare static files Make sure the folder contains an `index.html` and any CSS, JS, or assets it needs.
- Run the publish script Copy the files into the shared repo under one predictable slug.
- Push to main The GitHub Actions workflow deploys only `public/`, so the repo stays clean.
Harbor Notes
A soft editorial product page built from a single static entry point.
Cinder Studio
A campaign microsite with strong typography and minimal chrome.
North Archive
A directory page showing how multiple deployments can live under one domain.
Ready to reuse
Use this page as the first published example.
Duplicate the source folder, change the copy and accent system, then publish to a new slug with the same repo flow.
Open the template flow