event
Event invitation
A page for a meetup, in black and white with the details large enough to read across a room. Adds a calendar file the visitor can download, and shows the organiser's recent notes.
Templates
Eleven starting points. Each is a working page with the editing controls already wired up, so you change the words and the colours rather than building from nothing.
# start from one
npx nsite-clay init mysite --template=blog --npub=npub1…
npx nsite-clay deploy mysite --sec=nsec1…
project
Project homepage
What the thing is, why you would want it, two commands to try it, and what it will not do. With a feed for the project's own writing.
personal
Personal homepage
Who you are and what you have been writing, with both your notes and your articles fetched from relays. The one to reach for if you want a single address that is yours.
gallery
Photo gallery
Photographs from an npub, in three layouts you can switch between: a canvas you drag across, a sparse one with room to breathe, and a dark map of thumbnails that reveal themselves.
brutal
Neo-brutalist
Thick borders, hard shadows, flat colour and type that shouts. Loud on purpose, and still passes contrast.
irc
Channel log
A page you keep adding lines to: notes, a journal, a changelog. Sign in and a composer appears at the bottom; what you type becomes part of the page. This one's transcript is the conversation that built it.
eco
Low weight
System fonts, few images, as little CSS and JavaScript as the job allows. It measures and prints its own transferred size.
They share one engine
Every template links the same /nsite-clay-base-afad1539.css and the same
/nsite-clay-6f396120.js from the site root, and none of them carries a copy. Styling
happens through CSS variables, so the toolbar, the dialogs and the feeds follow whatever
palette a template sets. Changing the engine means editing one file, not eleven.
The rules a template follows are in CONTRACT.md. If you are handing this to an agent, point it at llms-1298226c.txt instead and let it pick.