The CRT look is in place: one stylesheet, scanlines, a blinking cursor and a slowly turning sigil. A theme is only half a website, though. This transmission is a scratchpad of where the look could go next, and, more importantly, what a site dressed like an old bulletin board is actually good for.
Ideas for the theme itself
Ground rule first: the site is fast because it's plain HTML and CSS. Anything below that needs JavaScript should be an extra layer, so the page still works, and still looks right, with scripts turned off.
Phosphor switcher
Real terminals came in green, amber and white phosphor. Because every color is a CSS variable, a [GREEN] [AMBER] [WHITE] toggle in the footer is a few lines: swap a class on <html> and remember the choice in localStorage.
html.amber {
--fg: #ffb000;
--fg-dim: #805800;
--fg-bright: #ffe0a0;
}A real command line
The prompts are decoration today. A small script could make one of them live: type ls to list posts, cat sniffnet to open one, help for commands. The normal nav links stay as the dependable route, and the prompt is the fun one.
Boot sequence
A one-time startup screen on the first visit, with a memory check, a modem handshake and CONNECT 2400, before the page draws in. It needs a skip key and must respect prefers-reduced-motion, and after the first visit it shouldn't play again.
Keyboard navigation
Number keys for menu items, j/k to move through the post list, q to go back. It suits the aesthetic and makes the site genuinely quicker to use for people who live in a terminal.
Smaller touches
- A faint screen flicker or phosphor glow, offered as an option rather than forced on everyone.
- Self-hosting the IBM Plex Mono font, so the site makes no third-party requests at all.
- ANSI-colored art for post headers, rendered with spans rather than images.
- A printable stylesheet that turns any post into a clean, plain printout.
What to use the site for
The look sets expectations: technical, personal, a little nostalgic, built by hand. Content that fits that tends to feel at home here.
A homelab and project log
Write-ups of builds, server setups and things that broke, posted as dated transmissions. The ls -lt post list already reads like a changelog, which is exactly what a project log is.
Tool spotlights
Short posts like the Sniffnet one: what a tool does, why it's worth trying, and a link in the downloads directory. Over time that adds up to a curated software shelf.
A microblog
Not everything deserves a full post. A /notes feed of one-to-three-line dated entries ("rebuilt the NAS, 40 minutes, no data lost") would keep the site alive between longer pieces. Add an RSS feed alongside it so people can follow without checking in.
Guides and tutorials
The theme tutorial showed the format works: step-by-step, copyable code, nothing hidden. Networking, Linux, self-hosting and security basics all read naturally in monospace.
A link directory and webring
The resource index could grow into a hand-picked directory of the small web: personal sites, useful tools, good reading. Joining or starting a webring of similar retro and personal sites fits the BBS spirit of linking to your neighbors.
A status board
The System Status section on the home page could report real things: uptime of self-hosted services, the latest post date, the last deploy. A static site can still show it if a small scheduled job rewrites the numbers.
Community
The info@ mailbox is open now. A guestbook page, or later a forum, would close the loop and turn a site you read into a place you visit.
What to keep
Whatever gets built, a few things stay non-negotiable: pages load instantly, everything works without JavaScript, text stays readable (contrast before atmosphere), and the effects never get in the way of the words.
Got an idea or a request? Send it to info@spiralnet.io.
End of transmission.