Where the name comes from#
Zi + DOM = Zidom.
Zi is taken from Zidane, the creator's son. DOM stands for the Document Object Model — the browser structure that turns interface code into the elements people see and use. Zidom brings those two ideas together: a personal beginning and a practical engineering purpose.
Why build another UI framework?#
Modern web interfaces already have excellent tools. Zidom started from a specific question: Can we keep component authoring expressive while making ordinary state changes more targeted and predictable?
That question became a small reactive engine and a JSX runtime that update dependent DOM bindings directly. Other pieces — routes, queries, forms, shared state, and a compiler — were added so developers could experiment with a coherent application stack.
Our design principles#
- Only what changes. Change the bindings that depend on the changed value.
- Make the behavior explainable. Prefer explicit signal lifetimes and predictable ownership over invisible magic.
- Useful by itself. Core signals do not require a renderer; the DOM runtime can work without the optional compiler.
- Tell the truth about maturity. Test results, incomplete features and release blockers belong in public documentation.
- Build for real applications. Keep learning from browser tests, accessibility, security and independent package consumers.
What the website should represent#
A small tribute does not need a loud visual gimmick. The identity is a calm, technical wordmark, a sharp violet-and-mint accent system and an emphasis on clear documentation. The name's origin belongs here; the homepage should make the framework useful to a developer within seconds.
Join the journey#
The repository is currently an experimental beta. Follow the roadmap and release blockers or explore the source.