Shellside

Packages

the shellside kit, one file each

• console-engine
  Terminal mechanics — parse/path/pipeline/runner/io plus fs and filter commands. Personality stays in the site.
• console-vfs
  Project filtered collections into a virtual filesystem — dirs, files, bins, char devices — for the console surface.
• content-model
  Schemas and the visibility contract — draft never leaks into public surfaces.
• dev-api
  DEV-only desk machinery — content editor and the gated HTTP handler behind the admin surface.
• edit-protocol
  The data-edit grammar, allowlists, path parsing, admin-preview URL helpers, and the typed preview-bridge contract.
• look
  Look roles, field-style maps, design-token and palette file factories, look history.
• site
  The config-driven host — this page is served by it.

Notes

• This demo site, explained

CV

• Education
• Experience

Docs

• README — what shellside is
  The kit's own front page — contracts over copies, both surfaces, the desk.
• Architecture — dual-surface system diagram
  How content, visibility, the console VFS, and the dev desk fit together.
• Extraction map — what stays site-local vs kit
  The ledger of every marquee piece promoted into a contract.
• Divergences — marquee↔kit alignment log
  Where the two trees speak differently, and what was reconciled.
• ADR — the site-instance contract
  site.config.ts + taste + content; the host injects generic surfaces.
• Roadmap — release bars and phases
  R1 portability, R2 packaging, and the inversion into config-driven sites.

Releases

• v0.1.0
  First cut — content-model, edit-protocol, look, dev-api contracts.
• v0.2.0
  console-vfs + reference /console — the VFS surface shipped.
• v0.3.0
  console-engine, @shellside/site host, create-site scaffold, leakAudit. Breaking (0.x): VFS node vocabulary.
• Marquee adoption
  charlesberret.net consumes vendored packages — field styles, design tokens, edit protocol, console engine — live in production.

Resume

• Experience