Babul wiki
68 pages · last verified 2026-10-23
Concepts 7
| Page | Owns |
|---|---|
| architecture-overview | The whole system on one page: the parts, where each runs, what it is built with, and how a change travels from a captured site to a version of main and into code. The… |
| branch-verify-merge | How a change moves from an edit to a version of main. |
| capture-reads-the-product | Capture turns a live URL into primitives. It opens the product in a real browser at each size the site supports, reads what a user would see, and files it as tokens,… |
| design-set | Static HTML and Tailwind from the CDN, one screen per file, declared in routes.js. No script renders a screen. The set is the spec; the app follows it. The set was… |
| journeys | A journey is a set of pages and the links between them. Journey shows the whole product as page frames joined by arrows, and filters it by who uses it. |
| onboarding-steps | 1. Company — its name, prefilled from the email domain. 2. Your product — the name; the way in (from a URL, from images, blank); the address; the sizes the… |
| tenant-isolation | Three layers, all in the database, so a mistake in application code cannot leak a company's data. Each is covered by a test in packages/db/src. |
Entities 5
| Page | Owns |
|---|---|
| access-levels | What a person can do in a product. The four levels are the whole list. |
| babul-kit | DECISION.2026-10-23.NO-KIT |
| demo-tenants | DEMO.NORTHWIND |
| example-northwind | The redesigned screens, the docs' screenshots and the landing page all draw one company, Northwind. Change a value here first, then the screens. The app's seed still… |
| plans | A free month, then Team. There is no free plan. The owner set the Team price on 2026-10-12 and chose the free month on 2026-10-16 (2026-10-16-free-month). |
Surfaces 26
| Page | Screen |
|---|---|
| analysis | What the last capture found: three scores, what was found, the gaps, and a ranked list of fixes. The first screen after a capture. |
| architecture | How Babul is built, in six small diagrams and one overview, opened from the architecture chip in the bar. |
| auth | The screens around sign-in and sign-up: verify email, forgot and reset password, and accepting an invite. |
| branches | A branch is not a page of its own. Switch to it and Journey, Pages, Components and Styles show it, as Complete or Delta. |
| components | One component at a time, drawn as a set: every variant and every state at once. |
| docs-article | One docs article. Quickstart, the four guides, CLI and MCP server use it. |
| docs-changelog | The order Babul is built in, as releases v0.1.0 to v1.0.0, each marked Next or Planned. |
| docs-home | The docs home: search, the three start guides, install snippets, and topics. |
| docs-search | ⌘K search over the docs, shown as a dialog on the docs home. |
| journey | The whole product as a map: every page as a small render with the roles that reach it, joined by its real links, each labelled with what you press. |
| landing | The public landing page. |
| legal | Privacy, Terms and Security on babul.dev, linked from the landing footer. |
| onboarding-capture | Onboarding step: Capture. Who uses the product (Open and roles with test sign-ins) and how to walk it, then Capture. |
| onboarding-capturing | The live capture: your site in a frame on the left, what has been found on the right; one role at a time. |
| onboarding-company | Onboarding step: Company. Name the company. Prefilled from the email's domain; the address in Babul is derived from it. |
| onboarding-product | Onboarding step: Your product. Name, the way in, the address, the sizes the site supports, one design or one per size, and the detected product stack. |
| pages | One page of the product at a time: the list by who reaches each page, the page drawn large, and what is true of it. |
| products | Every product in the company, as cards: a picture, main's version, the scores, open branches, how it came in, and who works on it. |
| review | Review turns your draft into one commit on a new or an open branch. |
| settings | Three separate settings: the product's, the company's and yours. Each has its own panel and no rail. |
| share | A preview link: someone with no account clicks through a product as one ref has it. |
| sign-in | Sign in with Google, or an email and a password; Forgot password links to the reset flow. |
| sign-up | Create an account: Google, or a work email and a password. |
| states | What the app shows when there is nothing yet, while it loads, when it is read-only, and when something is wrong. |
| styles | The product's tokens and icons, one group per page. |
| versions | Every version of main, a compare of two, and Revert. |
Flows 1
| Page | Owns |
|---|---|
| first-capture | The main path of the product: from the landing page to a first branch merged into main as a new version. It is the spine of the flow chart in routes.js; the chart's… |
Decisions 28
| Page | Decided |
|---|---|
| 2026-10-12-stack | · Part · Choice · ·---·---· · Repo · Turborepo + pnpm · · Web and API · one Next.js app (App Router), React, Tailwind. The API is tRPC inside it · · Capture · a Node… |
| 2026-10-13-product-access | |
| 2026-10-14-git-model | Trunk keeps a product's design the way git keeps code. |
| 2026-10-16-branch-page | DECISION.2026-10-23.NO-BRANCH-PAGE |
| 2026-10-16-free-month | DECISION.2026-10-22.ONBOARDING-THREE-STEPS-FREE-AI |
| 2026-10-17-analysis-read-only | Analysis is read-only. It shows the live product as captured: scores, findings, the AI analysis and its ranked fixes. Nothing on it changes the design. There is… |
| 2026-10-17-cli-and-mcp | One read API, /api/v1, signed in with a personal API token sent as Authorization: Bearer trk…. A token is a person's, for one company, and reads what… |
| 2026-10-17-drawn-elements | DECISION.2026-10-22.REDESIGN-FROM-SCRATCH |
| 2026-10-17-get-code | The capture describes each variant once, with no framework in it: a component spec. It is a tree of elements with tag, role, text as content, the attributes that… |
| 2026-10-18-editor-redesign | DECISION.2026-10-22.REDESIGN-FROM-SCRATCH |
| 2026-10-18-schema-0020 | DECISION.2026-10-22.REDESIGN-FROM-SCRATCH |
| 2026-10-19-plain-pages-and-styles | DECISION.2026-10-22.REDESIGN-FROM-SCRATCH |
| 2026-10-19-walk-free-automatic-team | Every plan can walk it yourself, and it is the free month's way to capture. Automatic capture is Team. |
| 2026-10-20-edit-state-and-caching | DECISION.2026-10-22.REDESIGN-FROM-SCRATCH |
| 2026-10-21-components-like-figma | DECISION.2026-10-22.REDESIGN-FROM-SCRATCH |
| 2026-10-21-images-can-be-drawn | DECISION.2026-10-22.REDESIGN-FROM-SCRATCH |
| 2026-10-21-no-patient-data | Trunk is not built for health data. The terms forbid capturing real patient data (PHI) or other special-category data. A product behind a sign-in is captured with… |
| 2026-10-21-ref-in-the-path | Every editor address names what it shows: main, a branch or a tag. It is the segment after the product, always written, main too. |
| 2026-10-21-schema-0024 | DECISION.2026-10-22.REDESIGN-FROM-SCRATCH |
| 2026-10-21-settings-placement | DECISION.2026-10-22.REDESIGN-FROM-SCRATCH |
| 2026-10-22-name-babul | The product, the packages (@babul/), the CLI (babul), the MCP server (babul-mcp), the project file (babul.json) and the environment variables (BABUL) are… |
| 2026-10-22-onboarding-three-steps-free-ai | Three steps: Company → Your product → Capture, then Analysis. - Your product: name, the way in (URL, images, blank), the address, the sizes the site supports… |
| 2026-10-22-redesign-from-scratch | Babul is redrawn from a blank page, one screen at a time, each approved by the owner before the next: version control for design (Capture → Journey → Pages →… |
| 2026-10-23-infrastructure-babul | The repo, folder, databases, roles, Vercel and Neon are called Babul too. |
| 2026-10-23-no-branch-page | There is no branch page and no Branches list. Switching to a branch shows Journey, Pages, Components and Styles as the branch has them, with Complete · Delta beside… |
| 2026-10-23-no-kit | Babul ships no component kit of its own. A product's components come from its capture, from an imported design system, or are made in Babul. packages/kit and… |
| 2026-10-23-schema-redesign | A new schema of 40 tables (from 50), in packages/db/prisma/schema.prisma. It replaced the old one on approval; the database is dropped and the one migration written again (no da… |
| 2026-10-23-stack-revisited | Keep the core (Turborepo, Next.js 16, tRPC, Prisma, Postgres, Playwright, Better Auth, the table queue) and settle what 2026-10-12 left open or what has changed since: |
Synthesis 1
| Page | Owns |
|---|---|
| compliance | Where Babul stands on SOC 2, GDPR and HIPAA, what is already in place, and what is left, in order. |