Skip to content

jtakeit ​

A back office for small businesses, with the website it runs: a CMS the owner edits by tapping their own page, bookings, enquiries, payments, analytics and hosting, behind one panel. Nobody is expected to hand-write a site here: an agent writes the schema, the pages and the content, a repository versions them, and the platform runs the part a studio does not want to operate — the panel the business owner uses, the enquiries, bookings and orders, the billing, the backups, the domain.

Of all of it, the diary is the part no agent writes in an evening: rates by the hour of the week, a stay by the night or a hire by the day, several of one class in one booking, a party seated at the smallest table that fits, seats and spots, add-ons with no time of their own, paid online or on the spot — ten kits with a trade's defaults, and preflight booking and cancelling end to end before anybody else does.

In a hurry: start here — the first site in twelve steps, the rule at each.

The agent in your session writes the site. The platform gives your client an admin panel they can use, a preview to sign off on before they pay, somewhere for the enquiries, bookings and orders to go, a host to serve it from, and a way for you to get paid. Hand over the client without handing over the code.

What the studio gets out of it, in one breath: reselling — a wholesale price per live site and nothing for a site before its launch, its own price to its client on top, and the difference kept whole; the choice of invoicing the client itself or billing them through the platform on its own Stripe, which is part of every site and never a percentage; a diary that takes paid bookings straight to the business's Stripe; a handover that walks the studio out of the loop with one link; and a dev session that frames the local dev server with the owner's real text before anything is pushed. The panel, by hand has each of these by screen and by person.

This is 0.x. The contract may still change between versions, and the changelog says what moved and what to do about it.

The shape of it ​

Three things are true, and everything else follows from them:

Git owns what is published; the database owns what is being edited. A site's design, its schema and its published content all live in that site's own repository. Drafts live in ours. This is what makes a build hermetic, what lets you keep your code, and what makes "give me this client as they were in March" a checkout rather than a support request.

The repository decides what a site is; the admin only fills it in. There is no "add a page" button and no "add a block" button, and their absence is deliberate. A form that could invent a block your template does not render is a form that produces a broken site in front of your client. What the admin can do is bounded by what your schema, jtk/schema.json, declares, and you write that file.

A new site is a row, not a deployment. One service, one database, one edge worker, however many sites. Nothing is provisioned per client.

Start here ​

For agents ​

llms.txt is the map. llms-full.txt is every page in one file, in reading order — about a hundred thousand tokens, so read single pages unless you need the whole. Both are resources of the MCP server too, and every link a resource carries is a jtakeit:/// URI the server can open.

Every refusal — from the schema judge, from a build, from the annotation lint — carries a JTK_E_ code with a path and a line of what to do. Look it up in the error reference rather than interpreting the prose.