Meowland
Build interfaces with Meowland
Build interfaces with a signal-driven runtime, a shared style system and components that fit together.
Six packages
Start with the component library, or use the pieces your project needs.
The rendering runtime: a tree of nodes, signals bound to the DOM, and one isolated runtime per application.
v0.1.1-alpha.1Tokens, options and CSS generation: declared values, one stylesheet, and the style axes a component may vary along.
v0.1.1-alpha.0The component library: cross-application components, semantic layout, the standard theme and the complete Assistant.
v0.2.0-alpha.3The presentation engine: the player, pages and steps, reveals, media, presentation layouts and themes.
v0.1.0-alpha.0The component workbench: a story index, an isolated canvas and an ordinary browser test entry point.
v0.1.2-alpha.1The site generator: content reading, page rendering, themes, assets and the build pipeline for static sites.
v0.1.1-alpha.1Components
136 components. Each one lists its style axes and DOM parts; the ones the stories cover also show a live example and the code behind it.
The workbench is the same gallery the library ships: every story the components declare, in one list.
How the pieces fit
One rendering graph, one theme assembly, one set of contracts.
meowjsx renders a tree of nodes and lets a component bind a signal to an attribute, so a later change reaches the DOM without re-rendering the tree. meowcss compiles tokens and style fragments into one stylesheet, and a component declares its parts and style axes instead of carrying its own CSS. meowtail is the component library those two rules produce.
meowbook turns the stories a package declares into a workbench and a live canvas. meowslides is the presentation engine on top of the same components. meowpress is the site generator that writes this page.