Design Systems with Deno and Oceanwind
summary
A small design-system experiment builds a static-site generator on top of Deno runtime replaces Node, using typed-html maps JSX to strings for TypeScript-checked templates and Oceanwind generates CSS server-side so no Tailwind purge or client runtime is required. Development serves pages on demand (no full precompile), explores SWC for fast AST work and incremental compilation, and wires tiny state-in-HTML primitives instead of React hydration. The prototype works for development but is experimental and not yet production-ready.
AI-written summary · about
chapters (9)
- 0:00Project introduction
- 5:58Switching from Node.js to Deno
- 11:36Deno for static sites
- 15:32Design systems vs static sites
- 19:01Typed HTML and Oceanwind
- 27:14Introducing Tailspin
- 28:59Q&A: React components
- 33:13Q&A: State in HTML
- 37:05Frontend future and bundling
related talks
35mScalable Design Systems with TypeScript
21mDesign Systems 101: The Developer Approach to Better Frontends
57mDon't miss the Deno Train
14mBuilding a design system in Next.js with Tailwind
20mDesign Systems for the Rest of Us
29mDesign at scale with Web Components (and ducks)
38mEmpathetic Design Systems
45mDesign systems adventures with React and TypeScript