Showcase
Different websites. The same small Nift boundary.
These are real projects built while developing the v4 website—not hypothetical framework diagrams. The point is less that they share a visual style and more that wildly different results can share a remarkably small amount of Nift-specific machinery.
NIFT
Keep your HTML.
Keep your tools.
Stop repeating yourself.
01 · This website
Nift v4 website
A full documentation/product site with theme switching, syntax highlighting, downloadable projects, responsive navigation, examples, install guidance and an extensive documentation tree.
Architecture
Nift
├─ 28 tracked pages
├─ reusable root/docs templates
├─ shared header/footer/docs navigation
├─ vanilla CSS
├─ vanilla JavaScript
├─ Highlight.js from CDN
├─ downloadable template ZIPs
└─ ordinary generated HTML
Nift owns composition, tracked paths and builds. The theme switcher, tabs and navigation behaviour stay ordinary browser JavaScript; syntax highlighting stays an external specialist library.
✦ AURORA
Turn scattered signals
into clear direction.
02 · AI / SaaS
Aurora
A polished dark product landing page with atmospheric gradients, interface mock-ups, product metrics and feature storytelling.
Architecture
Nift
├─ content/index.html
├─ templates/template.html
├─ head/header/footer partials
└─ public/
├─ CSS
└─ JavaScript
No npm install
No frontend framework
No external image dependency
The design looks like a modern SaaS product site, but the underlying project is essentially one tracked page plus reusable structure and ordinary frontend assets.
■ FORGE
Ship the system.
Skip the platform tax.
$ forge deploy✓ build completed✓ deployment ready
03 · Developer tooling
Forge
A developer-infrastructure landing page with terminal output, platform metrics, technical feature cards and a code-first visual language.
Architecture
Nift
├─ tracked HTML content
├─ shared document template
├─ reusable header/footer
└─ public/assets/
└─ CSS
Browser result:
plain HTML + CSS
There is no special “developer-tool theme engine” here. The complexity lives in the design, not in Nift's project model.
MERIDIAN°
We make digital
work worth feeling.
MONUMENT
04 · Studio / Portfolio
Meridian
A dark creative-studio project using oversized editorial typography, art-directed panels and CSS-generated visual work.
Architecture
Nift
├─ page-specific HTML content
├─ reusable studio shell
├─ header/footer partials
└─ public/assets/
└─ CSS-generated visuals
No component runtime
No image library
No build dependency tree
This starter is a useful example of Nift getting out of the way: almost everything interesting about it is just HTML and CSS.
What the showcase is demonstrating
The architecture does not have to grow with the visual ambition.
Nift can stay a small templating/build boundary whether the result is documentation, a SaaS landing page, a developer product or a high-end portfolio. And when a project genuinely needs TypeScript, React, Vue, Svelte, Go, Node, Python, Supabase or something else, those tools can join the repository without becoming Nift features.
