Home page recipe: choose a route, inspect one handle, carry the useful state forward.
Anatomy: surface for orientation, operators for handles, routes for return.
Output: proof cards, study routes, semantic contracts.
Feel: a readable room with lens switches, living terms, and a memory of what you touched.
Hold a living term to prime it, switch the lens to inspect the apparatus, or jump to a quick-start when you already know the next move.
Skim for prompt handles: a route, a material, a behavior, or a substrate. The loop is notice, name, test, leave a result note.
The interface teaches by return. A route remembers where you are, a chip hints what it does, and a shift in time, scroll, or context makes the same component behave like a different local spirit instead of a generic widget.
Current direction
The site helps me practice through recipes, components, spells, study plans, and session notes — then share what is worth reusing. The current metaphor is a cookbook with engineering notes in the margins. The test: can a pattern be read, reused, revised, and served to someone else without losing its source?
The site is built for adults still learning in the middle of ordinary life: parents keeping their minds warm, engineers who want theory without losing craft, people who need humor, fantasy, and nourishment to stay in practice.
The whole thing is a recursive editorial loop: make, inspect, reroute, repeat.
The center of gravity is spw-workbench,
with projections into Spw language design,
software routes, author craft,
math, tools,
texture.website,
RPG Wednesday,
and the broader publishing surface.
CSS describes constraints, spacing, overflow, and adaptation. Lower-level languages make memory, timing, and resource pressure speakable. A small set of rules can expand into many states — which is why software models stories, businesses, towns, and long-running projects better than most planning tools do.
The website holds the practice together instead of scattering it across apps, feeds, and moods. When structure holds, learning compounds instead of resetting. RPG Wednesday has run for over a year now — sessions, library cards, cast notes, and logs sedimenting into inspectable traces each collaborator can meet at their own rhythm.
Entry can be through soup, wings, a component, a character, a CSS state, or a trade ingredient — the underlying move is the same. Stock becomes context. Reduction becomes compression. Mise en place becomes dependency clarity. A session becomes a test kitchen for lore.
Culinary techniques ask for inventory. When a page says bloom, temper, deglaze, or reduce, it can also suggest a shopping list, a memory character, and a scene. A cook learns what to buy. A software engineer learns what operation is running. An RPG table gets a mnemonic creature that makes the concept stick.
The interface should feel like a marked-up field guide, not a pile of controls. Links still navigate. Buttons still announce themselves to assistive technology. But the visible language can call them handles, lenses, provisions, route clues, and pantry notes — so the page feels like somewhere to mosey through, not operate.
Much of this gets worked out in video. Speaking is practice, not a polished trait. The boonhonk idea is less a label than a disposition: a way to test how tone, force, and interactivity change when structure is allowed to recombine.
The site should feel learnable before it feels elaborate. Every interaction should show what changed, where to return, and whether the state is temporary or worth keeping. Depth appears through repeated handles, visible state, and small shifts in spacing, color, or copy. Resonance here means a visual relationship that teaches why a change matters.
