Purpose

What Babul is for, who it is for, and what it is not. From the repo's own pages.

What it is

Version control for design. Babul starts from the running product: it captures a live URL into tokens, components, pages and journeys (capture-reads-the-product). Every change after that is a commit on a branch, verified against the live product and merged as a version (scope, versioning). It answers PROB-0001: a hand-drawn design drifts from the product that shipped.

Who it is for

Teams that already have a live product and design on it, preferably US companies that use Figma today (marketing context).

What it is not

• Not a component kit: components come from a capture, an imported design system, or are made in Babul (scope).
• Not a hand-drawn design tool: a design starts from what is running.

Status

babul.dev is live (0.0.1, owner, 2026-11-01) (release.yml). The app is being rebuilt to the approved designs. Nobody has paid yet (PROB-0005). Words used here: glossary.