← bioHACK.NET

Site notes / design guide

Colophon

How this little corner of the web looks, reads, and works.

A personal laboratory for compilers, game engineering, systems work, and language learning. Here is the visual language that connects it all, and how it changes to suit the work.

01 / Design guide

Across the site

The shared thread is readable type, visible structure, and a few purposeful accents. Each part of the site adapts that vocabulary to its subject: a playable experiment, a lesson, a field notebook, or a working tool.

The original inspiration

Dune lettering.
Blade Runner instruments.

The home page takes its cues from science-fiction interfaces: the graphic overlays of Blade Runner, paired with Dune Rise lettering. Icy blue edges, warm orange light, scanlines, and small signs of activity give it the feel of an instrument panel.

That idea appears in the holographic quote panel, the heartbeat between bioHACK and NET, expanding radar rings, and orbiting project markers. The Claude catalog follows a separate, Anthropic-inspired direction.

A small study in those cues. Motion is optional and respects reduced-motion preferences.

Let the work lead

Give the demo, word, or task the most space. Keep supporting information close to it.

Make structure visible

Use type, alignment, and fine rules to distinguish a heading, a fact, and an action.

Use color with a role

Separate reading, navigation, and status. Pair meaningful colors with words or symbols.

Page snapshots · September 2026 · follow a preview to explore the live page.

The technical notebook page preview

Home · projects · technical notes

The technical notebook

Charcoal, warm white, rust, and signal blue. The geometric wordmark sets the tone; compact prose, small labels, and fine rules carry the detail.

  • #16171A
  • #E8E6E0
  • #C2410C
  • #7DD3FC
The playable gallery page preview

SNES · demos · compiler work

The playable gallery

The same dark foundation, with horizontal shelves of pixel art, outlined controls, and compact technical tables. The running demo gets the strongest visual emphasis.

  • #16171A
  • #1F2125
  • #7DD3FC
  • #54D98C
The language notebook page preview

Languages · study material · school questions

The language notebook

Warm paper, dark brown ink, and terracotta. Generous cards and large words give study material room to breathe. The Spanish page also responds to a dark color preference.

  • #F3EFE7
  • #FFFDF8
  • #211D18
  • #A74830
The focused reviewer page preview

Flashcards · pronunciation · casting

The focused reviewer

One prompt at a time, a dark warm canvas, gold emphasis, and large answer controls at the bottom. The Spanish reviewer also has a light palette; the TV view scales the lesson for distance.

  • #151514
  • #24221E
  • #FAF6ED
  • #EDB95E
The working planner page preview

Thailand · tasks · decisions

The working planner

A wider navy canvas, coral navigation, and rounded task panels. Dates, checkmarks, progress, and written statuses make the relationships between tasks visible.

  • #0D1621
  • #F4F1E8
  • #FF805D
  • #43C6A4
The travel calendar page preview

Annual agendas · routes · stays

The travel calendar

The dark site identity wraps a dense calendar. Color groups travel types; labels and dated entries explain each event. The layout keeps the chronology central.

  • #16171A
  • #C2410C
  • #7DD3FC
  • #A78BFA
The plugin catalog page preview

Claude · tools · install instructions

The plugin catalog

A light, warm canvas with white cards, muted orange accents, and Inter for reading. Monospaced commands sit alongside recognizable project marks.

  • #F7F4F0
  • #FFFFFF
  • #6B6560
  • #C96442
The tabletop tool page preview

Bishop · Dominion score tracker

The tabletop tool

Brown panels, parchment-colored text, and gold details suit a tabletop score sheet. Large totals, editable player names, and grouped controls keep the page useful during play.

  • #15110D
  • #221A12
  • #F3EAD7
  • #E8C878

Older pages, including the CV archive, retain their own layouts. The guide describes the site as a collection of related spaces; the examples below are a reference for extending them.

02 / Typography

A voice for each level

Three faces anchor the shared design. Display lettering introduces a place; the reading face explains it; monospace keeps small technical details orderly.

Dune Rise

Display / 400

Make
things.

Wordmark and short titles. Keep it large, use a little tracking, and leave room around the letterforms. Long headings belong in the reading face.

Space Grotesk

Reading / 400–700

Small machines.
Interesting questions.

Build something you can run. Explain the parts that matter. Leave enough room for a reader to follow the experiment, inspect the result, and try it for themselves.

Body text starts at 16px with 1.6 line height. Use weight and size for hierarchy; keep paragraphs at a comfortable reading width.

JetBrains Mono

Labels / 500

BUILD / PLAY / OBSERVE
0123456789 · $80:8000 · 60 fps

Dates, status, code, keyboard hints, and short labels. Uppercase and wider tracking work for a few words; prose stays in the reading face.

Hierarchy in context

Experiment / 01

A small machine in motion

A short introduction explains what you can see and what you can do.

Supporting detail · controls, dates, or a source reference

The shared faces are self-hosted. The Claude catalog uses Inter; focused tools also use system fonts. Thai text uses a system font with Thai glyphs. Blade Runner is declared in the shared stylesheet but is not part of the core hierarchy shown here.

03 / Color

Warm ground, cool signal

Charcoal and warm white do most of the work on technical pages. Rust gives the identity its warmth. Signal blue picks out section headings, references, and interactive emphasis.

Canvas

--bg#16171A

The dark ground behind technical pages.

Surface

--bg-soft#1F2125

Cards, code samples, and inset panels.

Reading

--ink#E8E6E0

Headings and primary text.

Quiet text

--ink-dim#8A857A

Metadata, captions, and secondary labels.

Structure

--rule#2C2E33

One-pixel dividers and surface edges.

Rust

--accent#C2410C

The wordmark dot and warm accents.

Rust edge

--accent-soft#6B2407

Subtle outlines around related content.

Rust wash

--accent-bgrgba(194,65,12,0.14)

A translucent tint for highlighted surfaces.

Signal blue #7DD3FC

The cool accent used on the home page and SNES documentation. The shared --signal-blue token also colors compiler contribution icons and merged PR badges.

Swatches above read their values from the shared stylesheet. Page palettes in the overview are local variations. Choose the palette of the section you are extending, and check text against its actual background: the darker rust is useful for identity and surface accents, while this guide uses blue for reading links.

04 / Layout & spacing

Room to read. Room to work.

The home page uses a narrow reading column. Planners and study pages open out when their content needs it. Keep paragraphs contained even when the surrounding layout is wide.

Reading

One column
Home: 760px outer width

Working

Content-led grid
Thailand: up to 1180px

Reading measure
The home introduction uses a 62ch measure, roughly a 60-character line. Long technical notes use a similarly contained column.
Page gutters
The shared shell has 22px side padding. Wider pages set their own gutters; keep text and controls clear of screen edges.
Vertical rhythm
Small gaps join a label to its value. Larger gaps separate subjects. A thin rule marks a change of section.
Small screens
Stack cards and facts when columns become cramped. Keep wide tables and gallery shelves in their own scroll areas.

Useful spacing increments / px

4
8
12
16
24
32
48

A working rhythm for new pieces. Existing pages choose spacing locally; there is no single enforced spacing scale.

Use fine outlines and restrained corners for technical material. Study cards and planner controls use larger radii to make their groups easy to recognize. Reserve a full-width layout for a tool that needs it.

05 / Components

The small recurring pieces

A few familiar patterns make different kinds of content easier to scan. These specimens show their roles; the status badges use the same styles as the SNES player.

Section marker

Experiments

A small, tracked label between fine rules. It organizes a page without competing with the title.

Status badges

PassFailInconclusive

Green, red, and amber support a written verdict. A badge reports a state; it does not look like a button.

Code & keyboard hints

frame_count += 1;

Press Start to pause.

Monospace distinguishes literal code. Bordered keycaps identify inputs. Keep long code in a scrollable block.

Technical table

Example display dimensions
AxisPixels
Width256
Height224

Align numbers, label units, and separate rows with fine rules. Give the table a caption that explains what it measures.

Pixel-rendered Mandelbrot set from the SNES demo

Let the artifact be the image

SNES previews keep their original proportions and visible pixels. A dark frame separates the image from surrounding notes; captions and controls sit outside the artwork.

Explore the demo →

06 / Interaction & motion

Show what can happen

Links lead somewhere. Buttons perform an action. Selected, focused, and unavailable states should be visible without guessing from color alone. Try the controls below, or move through them with Tab.

This checkbox changes only this example. Its checkmark makes the selected state visible.

Open a supporting note

Use a disclosure for useful detail that would interrupt the main reading flow. Keep the summary descriptive and the expanded text near its trigger.

Hover changes the outlined link’s edge and glow. Keyboard focus draws a separate outline. Disabled controls remain visibly distinct.

Focus
Keep an obvious outline around keyboard focus and enough space that surrounding content does not clip it.
Touch
Give standalone actions a comfortable target: this guide uses at least 44px. Let rows wrap before labels collide.
Motion
The home page uses a pulsing wordmark dot, orbiting markers, and a soft entrance for project links. Use these effects sparingly; reading and task controls should stay steady.
Reduced motion
New effects should respect the reader’s motion preference. This guide removes its hover transitions when reduced motion is requested.

07 / Words & images

Explain what the reader can do

Name the action

Use labels such as “Play,” “Download ROM,” or “Show answer.” Link text should make its destination clear.

Keep detail useful

Lead with the result or the task. Put commands, measurements, dates, and evidence next to the claim they explain.

Show the real thing

Use actual demos, diagrams, and screenshots. Describe meaningful images; keep ornamental icons out of the reading order.

Sentence case works for prose and action labels. Reserve uppercase for short navigation or technical labels. Let an image carry its own colors; keep the frame and caption quiet.

08 / Site notes

What this is

bioHACK.NET is Will Norris’s working notebook: publishable experiments, runnable artifacts, field notes, and the tools around them. The SNES collection is both a gallery and a compiler stress-test battery.

Built with

Site
Astro, ordinary HTML, CSS, and JavaScript.
Typography
Dune Rise for display moments; Space Grotesk for reading; JetBrains Mono for technical labels and status.
Playable work
SNES demos run through the embedded bsnes-jg player.

About this guide

This guide is maintained alongside the site. Page previews were captured in September 2026.

Privacy & resilience

The site does not include an application analytics library. Some interactive language tools save their progress in this browser’s local storage; their reset controls remove that local data. A few focused experiences load an explicitly named external service, such as Google Fonts on the Claude plugins page or the Google Cast receiver SDK. Links and embedded media can contact their destination when opened.

Credits & contact

This site builds on projects including llvm-mos and the emulator projects used to validate the demos. Fonts and packages retain their own licenses. For correspondence, write will@biohack.net.