Appearance
The brief: one conversation before the work
The brief is what lets somebody who never spoke to the client build the site. Everything after it is an argument from it: if the page is wrong, the brief was. It is gathered once, before any building — every question in one message to the developer, not one at a time as each file needs its answer — and it is done when the developer has read it and said yes.
The rules
- Nothing is invented. Every fact carries where it came from: the client said it, the developer said it, the old site says it, or it was asked and not answered. A guessed opening hour ends up in the diary and in structured data, which is the platform offering a time the business never kept.
- What is missing is written down as missing. A brief with holes is workable; one with plausible filler is not, because nobody can tell which half to check. Mark a gap
NEEDS CLIENTand carry it to the launch as an open item — never a placeholder price, never «9:00–18:00» because most places are. - One conversation, before the work. Read what already exists first — the old site, the profile the developer points at — so the client is not asked what they have already said in public. Then ask the rest together.
- The developer says yes. Show the brief — the facts with their sources, the defaults below, the open items — and build when they have said yes to it. A default nobody confirmed is a fact invented by the kit.
A person without a developer
When the person in the chat is the business itself — claude.ai, a phone, no terminal — the brief is the same rule in one short exchange. Where they gave their old site, read it first, and open with the offer (below): what their site will do here that the old one does not. Then these questions together, in the same message, before create_site, never one a message:
- The languages — the site's own, and any others.
- What the site does — online booking (paid online or on the spot: ask), a shop, a blog. Each is a module
create_sitelays out. - The currency, only if the site will show prices.
- The design. Does the business have a website already — its address? Sites it likes — links? From those you can make a design of its own (say: a custom design takes a little longer); read them with your own browsing. Or start from jtakeit's quick template, in the design of Brumy (brumy.ch), jtakeit's maker, and adapt its colours and type to the business. Pass the answer to
create_siteasdesign:customortemplate. - The photographs. Ask now. They can drop them on
media_link's page, or its box in the chat (box: true— say first what the box is for and that you put the photographs on the site after). Pictures already on their old website come in throughmedia_linkwithsite, its address as they gave it: the platform reads the site's pages and brings in every picture they show, galleries drawn by script too — the way to take their photographs from their old site, rather than picking addresses out of its HTML. Where the site refuses the platform (site.refused), read its pages yourself and send the pictures' addresses inurls— a builder's resized copy comes in as its original. A public profile's pictures:media_link'surls, from addresses they give. Or the template's photographs hold the places for now and theirs replace them later — say so.
The offer
The person came with a site that does what it can; this one can do more, and they should hear what, about their business, before they answer anything. Read their site for what it does by hand or not at all, and say in a few lines what it becomes here — each line tied to something on their site, never a list of features. What the platform does, against what an old site usually has:
| On their site | Here |
|---|---|
| a booking link to Calendly, a form, «call to book» | the diary on the site: free times shown, booked online, paid online or on the spot, confirmed, in the panel and to Telegram or e-mail |
| a weekly plan or a monthly programme as text or a PDF | the classes as entries with their times, and the next two weeks drawn live from the diary with the places left — a timetable that keeps itself current |
| events, workshops, courses with dates | entries with their dates: the next one on the home page, a past one hidden or marked over by itself (ends_by) |
| a price list typed into a page | services with their prices and lengths, which the owner changes in the panel from a phone, the money in the site's currency |
| opening hours as text | the hours the diary keeps, and «open now» on the business's clock |
| things they sell — oils, vouchers, products | the shop: products, variants, stock, delivery, Stripe's checkout straight to their account |
| one language | its other languages, each page translated beside the original |
| news, a blog on Instagram | a journal on the site, written from the panel |
| reviews pasted in | testimonials the owner adds and orders |
| changes only through whoever built it | every word and picture edited by the owner on the page, from a phone |
Two or three lines that matter to this business, not the table read out — and what is shown in the catalogue (get_design_catalogue, a site's booking and prices pieces) is how it can look.
Then create_site. What it lays out is the kit's example: its words and its people (Alex, Maria and Sam Muster, an «Erstgespräch») are placeholders, never the person's site and never «ready pages». Write the site in the person's language from what you know — the name, what they do, this brief — before you tell them to look; the preview link may be given at once — it shows a waiting screen until your first build. On design: custom the design comes first (below), and the link waits until a build is designed. What you do not know, ask for; never leave the example's text in its place.
A custom design
design: custom is a stage of its own, before any page is built — the owner asked for a design «inspired by the old site» and got the template with its colours changed, called custom (18 November 2026). The site is laid out in the kit's bare look (where the kit has none yet, in its default, and the create's says tells you). The design comes before the content: it decides the blocks — which sections, in what order, with what message — and the words are written into the design the person chose, never into the bare look first; the same words read differently in another design, and a person shown their words in the bare look reads it as their site. The link keeps its waiting screen until a build is designed. Then:
- Look at what has been built:
get_design_catalogue— the studio's sites in pieces, pictures and code, browsed whole, then close. Study the person's site and the references they named: the palette, the type pairing, the grid and the spacing, how photographs are treated (full bleed, framed, cut out, black and white), the rhythm of the sections, the motion. The design lists the axes every site chooses on — the hero, the header, the overlap, the surfaces, the mark… — with the variants sites already built took; choose one per axis from the business's own material, or make a new one. - Write
DESIGN.mdat the site's root: a short design brief — the page's sections in order, each with its message; the choices in a few lines each, and where each came from — and the choices injtk/design.json'saxes. The floor in the design is kept whatever the look: the screen's height, fonts that don't jump, numbers that line up, the measures, one family of corners. - Show two or three directions as pictures, each with the business's own photographs, its name, its headline and the facts that carry the message — the rest of the words wait for the choice — declared in
jtk/design.json'sdirections, each a design of its own, three axes apart, the hero among them (the design, «Directions to choose from»): the person switches them on the preview;get_built_pagewithshotanddirectionpictures each. Look at each as a demanding designer would first —get_built_pagewithshot: "review"— and fix what that finds, two rounds. Let the person choose. - Build the chosen one: rewrite the hero, the header, the footer, the sections and their composition (the kit's
docs/compositions.mdis the vocabulary), not only the tokens; delete the template's files the site no longer draws, and the other directions anddirections. Then write the full content into its sections.
Every build counts the template's design files the site still wears, byte for byte the scaffold's (get_build → design); on a custom site whose design is mostly the template's, the build and preflight say JTK_W_TEMPLATE_DESIGN — advice, never a refusal. Never call a recoloured template custom: if the person settles for the template adapted, say exactly that, and the path is template.
Where the chat shows apps (claude.ai on the web, the desktop app, a phone), the site's preview appears under get_preview_link's answer, pictured in a real browser, and updates itself: «your agent is writing your site» until your first build, then the site — a content change at once where it is drawn live, a code change after its build. Call it when the person asks to see the site or at a milestone (the first version, a new design), at most once in a reply. The person can mark an area of a page there, or tap a text, and write what to change; «Send to Claude» brings you a message with their notes, and get_site's notes holds them with every field the area covers. Do what they ask in the files, tell them, and close each note with write_files' notes_done (alone, it needs no base).
What to ask
Keep it short — a fifteen-minute conversation, not a form:
- who the business is, where, what it sells — a sentence each;
- who actually comes: the last three customers, not a persona;
- the one thing a visitor should do on the page — call, book, write;
- which service they want more of: «what would you like the phone to ring about» — that and the city are the query the page is written for;
- what makes them different, in their own words; who they turn away, and why;
- what they dislike on competitors' sites;
- the language, the domain, the photographs — and, where the business is one person, a good photograph of them;
- the mark — a logo, the sign over the door, as a file (SVG best, or a square picture of 180px or more). It is the icon in every tab, on a phone's home screen and beside the site in search results, and nobody thinks to give it unless asked. Without one the scaffold's stand-in is the business's initials (
public/favicon.svg); say that back, and replace it when the mark comes.preflightchecks the icon and says when it is still the stand-in; - the design —
npx @jtakeit/astro createlays the site out in the design system of Brumy (brumy.ch), jtakeit's maker, as an example: ask whether the business has a look of its own (its sign, its colours, a site it likes). Say the example's look may be kept, and recommend adapting or redoing it for this business — a design of its own is A custom design above, never the example's look recoloured; then ask which of the example's sections the business needs, and take the others out before the first push — their blocks, their entries and their words; - a second language, only where the developer names one — it is a second site to keep written, every page and every post, for ever. Then
npx @jtakeit/astro create --locale de-CH --locales enlays it out: a translation beside every original, holding only the words, and the words that are not content fromnpx @jtakeit/astro copy <locale>; what people book is in every language, always (jtakeit:///guides/languages.md); - a blog, only where somebody will write it — an empty one says the business stopped caring.
jtk create --blogturns it on, with its listing at/blog; write the first posts before launch; - what the prices are in — the currency, three letters:
uahfor a business in Ukraine, asked where the site shows prices (with bookings or a shop it must be). Give it tocreate_siteascurrency; a site made without one takes it fromjtk/site.jsonat the import —"currency": "UAH"at the top ("business": {"currency": "uah"}on a contract-2 site) — and every build writes it back for the page. Once the site has its currency, a person changes it in the panel (The site → The business); a contract-3 import that brings a new one is refused,JTK_E_CURRENCY_SET(the one the last save wrote, from before that change, is left for the next save). One currency a site, set on the site and nowhere else: a page shows a price withsiteCurrencyfromsrc/lib/site.tsand never names a code or a sign of its own — preflight reads the built prices and fails one in another currency. A price is whole minor units of it —{"minor": 18000}is CHF 180,{"minor": 1000}is ¥1000 (a bare18000on a contract-2 site). No kit knows the currency (a kit is for every country), and it starts no payment; - whether a booking is paid online or on the spot — before anything else about the money, and never assumed. Read the current site: where people book and pay at the till today, say so («the site books without paying; people pay on arrival») and ask whether paying online is a feature the developer wants added, or whether the booking stays as it is. A rate without
costsis bookable and not payable, which is the ordinary state for a business that takes its money on arrival. And when the price depends on the day and the hour — a lane 25 € before six and 42 € on a Friday night — it is the rate'sratesinstead ofcosts, a row per span of the week (jtakeit:///guides/bookings-on-the-site.md, A price by the hour of the week), never a rate per price zone or a price near enough; - where the enquiries go: the Telegram chat or the email a person links in the panel (an agent cannot link one);
- whether the business sells goods online — then it is a shop, and the shop kit below is laid over the site whole. Every order is paid online (there is no paying on the spot in a shop), so what is asked is what it sells, where it ships and its VAT, as A shop says;
- whether the enquiry form takes photographs, and how many (1 to 7) — an order form for a website, a quote from pictures of the job. Declared as
photoson the form's block; the kit's<jtk-lead>draws the control, the platform cleans and keeps them privately and takes none a form did not declare (jtakeit:///guides/connecting-a-site.md, Photographs with an enquiry). Never health or other sensitive pictures; - the slug — the site's name, the first part of its handle (where its preview is), so that
create_sitefollows the brief at once and the studio sees the site in its list while you work; - where the code will live — on jtakeit (
push_code, nothing to install, the default when the copy has no GitHub remote), or in a GitHub repository: then which organisation or account, and who administers it. Our GitHub App has to be installed there by that person beforeattach_repoworks (https://github.com/apps/jtakeit-connect, Install, choose the repository; it readsContentsand nothing else;jtakeit:///guides/connecting-a-site.md, Where the code lives). It is the one step you cannot do, so ask for it now rather than when the work is waiting on it; - what the site is built with, when the developer has not said. Offer Astro: the platform ships its scaffold (
npx @jtakeit/astro create, with a kit laid out in one command), so a site on it is standing in minutes. Any other static generator is taken too — Eleventy, a Next export, Nuxt, SvelteKit, a script — and is laid out by you, to the list injtakeit:///guides/connecting-a-site.md(On another generator), with the forms,_meta.json, the kit and the tool that writes the schema from@jtakeit/kit. A developer who names a stack gets that stack; one who does not gets the question, with Astro as the answer you recommend and the reason beside it. Never a server-rendered site: the platform serves static files.
Bookings: the kit, whole
Bookings are not built from nothing, and they are not made simpler. Take the kit of the business's kind whole — every collection and the role the diary gives it (classes, places, seats, a resource's own hours and what it does), every rate with its fewest and most, every setting (a break after each booking, a gap between lettings, the hours a thing goes out and comes back, how long an unconfirmed booking holds its time) — and put the client's facts into it. What the platform does with them comes with it: a refused time offered the nearest free one instead, a stay in whole days, a class promised instead of a car, a party seated at the smallest table that fits, several services in one visit. A salon is not «a service and a master», and a rental is not «a car and a day».
Taking something out of a kit — the classes of a rental with one of each car, the party question of a restaurant that takes no groups — is a decision: name it to the developer, say what the visitor loses by it, and write it in the brief under Decisions. It is never a simplification made quietly.
Each kind below has two lists, and both are the kit's own:
- Ask — the facts only the business has. Ask each; what is not answered is
NEEDS CLIENT. - Taken by default — say it, get a yes. What the kit chose for the trade: confirmation, cancellation, payment, the hand-over hours, what visitors see, where the business hears of a booking. Say each back to the developer as a sentence; a «no» is a new value in the bookings' settings (
jtk/modules/bookings.json,jtk/bookings.jsonon a contract-2 site), and a yes is a fact with a source.
apartments (apartments)
Apartments by the night: check-in and check-out hours, the guests an apartment sleeps. — the kit.
Ask
- zone: the business's time zone — from its address; say it back rather than asking
- costs: the price of a night — the kit's rate is the unit, never a price
- the apartments: each one's guests, and what tells it from the others (a floor, a number) — shown to visitors when they choose one; not the street address unless the client wants it printed
Taken by default — say it, get a yes
- Every booking waits for the business to confirm it (
confirm: by_hand), holding its time for a day and then lapsing (hold) — or are bookings confirmed at once? - A visitor may cancel or move their booking themselves until 3 days before it starts; after that only the business can (
cancel_until). - Nothing is paid online: the visitor pays on the day (
payment: no) — or a deposit, or in full when booking? - Handed over at 14:00 and brought back at 12:00 on the last day (
hand_out,hand_back). - Bookable up to 365 days ahead (
horizon). - Bookable for today, with no notice (
lead: 0). - Shown to visitors: every apartment's name and its distinguishing marks, wherever a visitor may choose one; what is booked and their prices. Nothing goes into the marks that the client would not want printed.
- A new booking is sent where the site's enquiries go — the Telegram chat or the email a person links in the panel; an agent cannot link one. Ask which, and say it is theirs to link before the launch.
car rental (cars)
A car rental: cars by the day, grouped in classes that carry the price of a day; a visitor takes a class or a named car. — the kit.
Ask
- zone: the business's time zone — from its address; say it back rather than asking
- the classes the fleet is sold in, each with its price of a day. A letting in a class costs that price times its days, whichever rate the visitor took — the week is seven of them, and a weekly discount cannot be set beside class prices; if the client has one, it is an open question, not a number to adjust
- the rates' own prices (
costs) only if some cars are in no class: those are charged the rate - the cars: each one's class, and what tells it from its twins — a colour, a trim. The marks are shown to visitors beside the name when they choose a car: a plate goes there only if the client wants it printed
Taken by default — say it, get a yes
- Every booking waits for the business to confirm it (
confirm: by_hand), holding its time for a day and then lapsing (hold) — or are bookings confirmed at once? - A visitor may cancel or move their booking themselves until a day before it starts; after that only the business can (
cancel_until). - Nothing is paid online: the visitor pays on the day (
payment: no) — or a deposit, or in full when booking? - Handed over at 10:00 and brought back at 10:00 on the last day (
hand_out,hand_back). - Bookable up to 180 days ahead (
horizon). - Bookable for today, with no notice (
lead: 0). - No gap between one letting and the next: back in the morning, out again the same day (
buffer_stay: 0). - Shown to visitors: every car's name and its distinguishing marks, wherever a visitor may choose one; what is booked, the classes and their prices. Nothing goes into the marks that the client would not want printed.
- A new booking is sent where the site's enquiries go — the Telegram chat or the email a person links in the panel; an agent cannot link one. Ask which, and say it is theirs to link before the launch.
clinic (doctors)
A clinic or a dental practice: appointments by the hour with a doctor, confirmed by the practice. — the kit.
Ask
- zone: the business's time zone — from its address; say it back rather than asking
- hours: when it is open — the kit does not guess them
- the services: each one's takes and costs
- the doctors: who they are, their own hours, which services each one sees patients for
Taken by default — say it, get a yes
- Every booking waits for the business to confirm it (
confirm: by_hand), holding its time for a day and then lapsing (hold) — or are bookings confirmed at once? - A visitor may cancel or move their booking themselves until a day before it starts; after that only the business can (
cancel_until). - Nothing is paid online: the visitor pays on the day (
payment: no) — or a deposit, or in full when booking? - Bookable up to 180 days ahead (
horizon). - No sooner than 2 hours from now (
lead). - 5 minutes kept free after each booking, to get ready for the next (
buffer). - Start times offered every 15 minutes (
slot_every). - Shown to visitors: every doctor's name and its distinguishing marks, wherever a visitor may choose one; what is booked and their prices. Nothing goes into the marks that the client would not want printed.
- A new booking is sent where the site's enquiries go — the Telegram chat or the email a person links in the panel; an agent cannot link one. Ask which, and say it is theirs to link before the launch.
coworking (spaces)
A coworking space: desks and rooms by the hour inside opening hours, or by the day. — the kit.
Ask
- zone: the business's time zone — from its address; say it back rather than asking
- hours: when it is open — the kit does not guess them
- costs: the price of each rate
- the spaces: each desk or room, and how many it seats
Taken by default — say it, get a yes
- A booking is confirmed at once (
confirm: auto) — or does the business confirm each one by hand? - A visitor may cancel or move their booking themselves until 2 hours before it starts; after that only the business can (
cancel_until). - Nothing is paid online: the visitor pays on the day (
payment: no) — or a deposit, or in full when booking? - Bookable up to 30 days ahead (
horizon). - No sooner than 30 minutes from now (
lead). - Start times offered every 30 minutes (
slot_every). - Shown to visitors: every space's name and its distinguishing marks, wherever a visitor may choose one; what is booked and their prices. Nothing goes into the marks that the client would not want printed.
- A new booking is sent where the site's enquiries go — the Telegram chat or the email a person links in the panel; an agent cannot link one. Ask which, and say it is theirs to link before the launch.
equipment rental (equipment)
Equipment for hire: items by the day, each told from its twins by a serial number. — the kit.
Ask
- zone: the business's time zone — from its address; say it back rather than asking
- costs: the price of each rate, a day and a week — the kit's rates are units, never prices
- the equipment: each item, and what tells it from its twins — a serial number, a colour. The marks are shown to visitors beside the name when they choose an item
Taken by default — say it, get a yes
- Every booking waits for the business to confirm it (
confirm: by_hand), holding its time for a day and then lapsing (hold) — or are bookings confirmed at once? - A visitor may cancel or move their booking themselves until a day before it starts; after that only the business can (
cancel_until). - Nothing is paid online: the visitor pays on the day (
payment: no) — or a deposit, or in full when booking? - Handed over at 10:00 and brought back at 10:00 on the last day (
hand_out,hand_back). - Bookable up to 90 days ahead (
horizon). - Bookable for today, with no notice (
lead: 0). - Shown to visitors: every item's name and its distinguishing marks, wherever a visitor may choose one; what is booked and their prices. Nothing goes into the marks that the client would not want printed.
- A new booking is sent where the site's enquiries go — the Telegram chat or the email a person links in the panel; an agent cannot link one. Ask which, and say it is theirs to link before the launch.
hotel (rooms)
A hotel: rooms by the night, grouped in room types that carry the price of a night. — the kit.
Ask
- zone: the business's time zone — from its address; say it back rather than asking
- the room types, each with its price of a night. A stay in a type costs that price times its nights, whichever rate was taken
- the rates' own prices (
costs) only if some rooms have no type: those are charged the rate - the rooms: each one's type, how many guests it sleeps, and its number — shown to visitors when they choose a room
Taken by default — say it, get a yes
- A booking is confirmed at once (
confirm: auto) — or does the business confirm each one by hand? - A visitor may cancel or move their booking themselves until a day before it starts; after that only the business can (
cancel_until). - Nothing is paid online: the visitor pays on the day (
payment: no) — or a deposit, or in full when booking? - Handed over at 14:00 and brought back at 12:00 on the last day (
hand_out,hand_back). - Bookable up to 365 days ahead (
horizon). - Bookable for today, with no notice (
lead: 0). - Shown to visitors: every room's name and its distinguishing marks, wherever a visitor may choose one; what is booked, the classes and their prices. Nothing goes into the marks that the client would not want printed.
- A new booking is sent where the site's enquiries go — the Telegram chat or the email a person links in the panel; an agent cannot link one. Ask which, and say it is theirs to link before the launch.
photo studio (studios)
A photo studio: halls by the hour, with time to set the hall up again after each session. — the kit.
Ask
- zone: the business's time zone — from its address; say it back rather than asking
- hours: when it is open — the kit does not guess them
- costs: the price of an hour
- the halls: each one and what tells it from the others
Taken by default — say it, get a yes
- Every booking waits for the business to confirm it (
confirm: by_hand), holding its time for 12 hours and then lapsing (hold) — or are bookings confirmed at once? - A visitor may cancel or move their booking themselves until a day before it starts; after that only the business can (
cancel_until). - Nothing is paid online: the visitor pays on the day (
payment: no) — or a deposit, or in full when booking? - Bookable up to 60 days ahead (
horizon). - No sooner than 2 hours from now (
lead). - 30 minutes kept free after each booking, to get ready for the next (
buffer). - Start times offered every 30 minutes (
slot_every). - Shown to visitors: every studio's name and its distinguishing marks, wherever a visitor may choose one; what is booked and their prices. Nothing goes into the marks that the client would not want printed.
- A new booking is sent where the site's enquiries go — the Telegram chat or the email a person links in the panel; an agent cannot link one. Ask which, and say it is theirs to link before the launch.
restaurant (tables)
A restaurant: a table for the length of a sitting; a visitor says how many they are, and the smallest table that seats them is theirs. — the kit.
Ask
- zone: the business's time zone — from its address; say it back rather than asking
- hours: when it is open — the kit does not guess them
- the tables: each one's seats
- how long a sitting takes, if not two hours
Taken by default — say it, get a yes
- A booking is confirmed at once (
confirm: auto) — or does the business confirm each one by hand? - A visitor may cancel or move their booking themselves until 2 hours before it starts; after that only the business can (
cancel_until). - Nothing is paid online: the visitor pays on the day (
payment: no) — or a deposit, or in full when booking? - Bookable up to 60 days ahead (
horizon). - No sooner than an hour from now (
lead). - Start times offered every 15 minutes (
slot_every). - A visitor books for up to 8 at once (
party). - Shown to visitors: every table's name and its distinguishing marks, wherever a visitor may choose one; what is booked and their prices. Nothing goes into the marks that the client would not want printed.
- A new booking is sent where the site's enquiries go — the Telegram chat or the email a person links in the panel; an agent cannot link one. Ask which, and say it is theirs to link before the launch.
salon (masters)
A salon or a barbershop: services by the hour, masters who each keep their own hours and say what they do. — the kit.
Ask
- zone: the business's time zone — from its address; say it back rather than asking
- hours: when it is open — the kit does not guess them
- the services: each one's takes and costs
- the masters: who they are, their own hours when they differ, what each one does
Taken by default — say it, get a yes
- A booking is confirmed at once (
confirm: auto) — or does the business confirm each one by hand? - A visitor may cancel or move their booking themselves until 3 hours before it starts; after that only the business can (
cancel_until). - Nothing is paid online: the visitor pays on the day (
payment: no) — or a deposit, or in full when booking? - Bookable up to 60 days ahead (
horizon). - No sooner than an hour from now (
lead). - 10 minutes kept free after each booking, to get ready for the next (
buffer). - Start times offered every 15 minutes (
slot_every). - A visit may be several services, one after the other (
combine). - Shown to visitors: every master's name and its distinguishing marks, wherever a visitor may choose one; what is booked and their prices. Nothing goes into the marks that the client would not want printed.
- A new booking is sent where the site's enquiries go — the Telegram chat or the email a person links in the panel; an agent cannot link one. Ask which, and say it is theirs to link before the launch.
sessions (classes)
A studio of classes: each class keeps its timetable in its own hours and has places; a visitor books a place. — the kit.
Ask
- zone: the business's time zone — from its address; say it back rather than asking
- the services — the
servicescollection, one entry per kind of class (block typecourse): how long a session takes and what one place costs —per: "person", so a party of two pays two places (wiki/70) - the classes — the
sessionscollection, one entry per timetable (block typesession): its weekly hours, one row per session's start, and how many places it has
Taken by default — say it, get a yes
- A booking is confirmed at once (
confirm: auto) — or does the business confirm each one by hand? - A visitor may cancel or move their booking themselves until 12 hours before it starts; after that only the business can (
cancel_until). - Nothing is paid online: the visitor pays on the day (
payment: no) — or a deposit, or in full when booking? - Bookable up to 30 days ahead (
horizon). - No sooner than an hour from now (
lead). - Start times offered every 15 minutes (
slot_every). - A visitor books for up to 2 at once (
party). - Shown to visitors: every class's name and its distinguishing marks, wherever a visitor may choose one; what is booked and their prices. Nothing goes into the marks that the client would not want printed.
- A new booking is sent where the site's enquiries go — the Telegram chat or the email a person links in the panel; an agent cannot link one. Ask which, and say it is theirs to link before the launch.
A business none of the kits is for takes the nearest one, its kind and both of its lists, and writes over the words that do not fit — the trades an agent meets, each with its kit and what no kit has, as kits says:
| business | nearest kit | words to write over | what no kit has |
|---|---|---|---|
| barbershop | salon | none — «майстер» fits | — |
| nail or beauty studio | salon | none | — |
| yoga or dance studio | sessions | none — classes with places | — |
| personal trainer, one to one | salon | the resource: «майстер» → «тренер» | — |
| group trainer | sessions | none, or the class's name | — |
| photographer in a studio | photo_studio | none | — |
| photographer who comes to you | salon | the resource: «майстер» → «фотограф» | the customer's address: in the note |
| excursions and tours | sessions | the booking: «заняття» → «екскурсія», in letter.*, page.*, diary.* | a meeting point per tour: the kit's entries have no field for it — a field added to the schema, or the page's own text |
| tutor | salon (one to one) or sessions (a group) | both the resource and the booking: no kit says «урок» or «учень» | — |
| master who comes to the customer — a plumber, a massage at home | salon | the resource, and the booking where «запис» does not fit | the customer's address: there is no field for it, only the note |
| karaoke room, billiard table, a court by the hour | photo_studio | the resource: «зал» → «кімната», «стіл» | — |
| parking | coworking by the hour, equipment_rental by the day | the resource: «місце» → «паркомісце»; the booking | the car's plate: only the note |
| guest house | apartments, or hotel where rooms are of types | none | — |
| hovercraft or boat hire | equipment_rental | the resource | — |
Before it is handed over: the self-check
A site that takes bookings is not handed over until the server has walked a booking through the whole chain on the build published now. preflight with self_check: true asks for it. The server books as a visitor would — on rows nobody sees and nobody is told of, deleted when it ends — and walks it through what the owner and the customer do: the state it is made in, checked against the kit's rule (a kit that confirms at once books it confirmed); confirmed, refused, moved by the owner, another time offered and accepted, «it suits», moved and cancelled by the customer, cancelled by the owner, the time free again. Every letter on the way is written by the code that sends it, and read: no hole left, no field empty, no word of another kind of business, the site's language.
- Run
preflightwithself_check: true. - Read the steps under
self_check: each ispassed,failed,blocked— it could not be walked: no published build, or no free time in the next three weeks, which is the setup's fault — ornot_applicable: nothing of it on this site, as a kit that confirms at once has nothing to confirm. - Fix what a failed or blocked step names, build, publish, and run it again — once a minute at most.
- Do not say the site is done until
preflightsaysready. A site that takes bookings is not ready while the self-check has not run, failed, could not be walked, or is of an older build — a version published since.
What it does not check: the booking form's script on the page (try_booking books through the form), whether a letter is delivered, and the payment — it never pays. A site that takes money online is advised JTK_W_PAYMENT_UNCHECKED: check the payment by hand, and tell the owner it was not checked.
A shop: the shop kit
A shop is not built from nothing either. It is laid over the site with npx @jtakeit/astro add shop — whole, beside a booking kit or without one — and the business's facts are put into it: the products collection and the product type, the shipping settings it starts from (one zone, two methods with no price) and the storefront's components to copy. The shop kit is the platform's, the shop on the site says what it lays and what the page draws, and leaving something out of it is a decision, written under Decisions, as a booking kit's is.
It has the same two lists, and both are the kit's own:
Ask
- the catalogue: what it sells and roughly how many products — a spreadsheet, or a WooCommerce or Shopify export, with the SKUs and the stock it already has
- variants and customizations: whether any product has variants (sizes, colours) or customizations (a name on a tag) — customizations are written only for the products that have them
- the country it sends from: the zone the kit starts with — from the address; say it back rather than asking
- where it ships, and each method's price: flat or by weight, and free above a total
- pick-up: whether the business offers it, and where to collect
- VAT: which products are not ordinary goods — books, food, children's clothing — where the business charges it
Taken by default — say it, get a yes
- Stock is counted for every product (
tracked), and a product nobody stocked is sold out until its count is set — or is any made to order (tracked: false)? - A checkout holds what it sells for 31 minutes while the buyer pays on Stripe's page; the last item goes to the first who goes on to pay.
- Every order is paid online — by card, Apple Pay or Google Pay — a pick-up too.
- The buyer gets a confirmation, and an on its way email with its tracking link, or ready for pick-up, when the owner marks the order fulfilled.
- New orders go where the site's enquiries go — the Telegram chat or the email a person links in the panel, which an agent cannot link.
- VAT and paying in one's own currency are off until the owner turns them on, on the site's Payments screen.
A person's steps, said in the brief. An agent does none of them, and each is the business's to do in the panel: connecting the business's Stripe account (nothing is paid before it is), linking where new orders go (the Telegram chat or the email, in The site → Notifications), and switching VAT on and the buyer's own currency on, on the site's Payments screen. And the studio's: a shop line on its plan beside the site's, under Reselling, by its owner or admin — a site that sells is refused its launch without one. Say to the developer, in the brief, that these are theirs to do before the launch, and write each under Open.
The tax code. A product's tax_code is Stripe's — txcd_ and eight digits — and decides the VAT only where the business charges it. Ordinary goods unless the business says otherwise: a product with none is taxed as that. Ask which products are not ordinary goods and give each the code of what it is, from the short list the panel offers by name, or Another code, typed, for any other of Stripe's; never a rate, which Stripe applies for each country.
| the panel offers | tax_code |
|---|---|
| Ordinary goods | txcd_99999999 |
| Printed books | txcd_35010000 |
| Children's books | txcd_35010001 |
| Newspapers | txcd_35020100 |
| Magazines | txcd_35020200 |
| Food and groceries, not eaten on the premises | txcd_40040000 |
| Clothing and footwear | txcd_30011000 |
| Children's clothing and footwear | txcd_30011200 |
| Another code | any other of Stripe's, in the same shape |
Where it is written
BRIEF.md at the root of the site's repository, in this shape:
markdown
# <Business> — brief
Read on <date>. Sources: developer <date>, <old site>, <profile>.
## In one sentence
## The one action
## Facts
| Fact | Value | Source | <- every row sourced; `NEEDS CLIENT` where it is not
## Bookings
The kit: <kind>, whole — or what was taken out, under Decisions.
| Asked | Answer | Source |
| Default | Confirmed / changed to | Source |
## The shop
The kit: shop, whole — or what was taken out, under Decisions.
| Asked | Answer | Source |
| Default | Confirmed / changed to | Source |
## Decisions
## Open — NEEDS CLIENTIt is the client's repository too: nothing goes in it that you would not show them. The facts that the page prints — the name, the address, the phones — go into src/data/site.ts as well, confirmed ones only.
Done when
The list under this heading is a task list — - [ ] and - [x] — that jtk create seeds from this guide's lines and the kit's asks (add a line below that a scaffold did not seed), and that the panel shows the owner as the agent's own list, in your words, beside what the files say. Keep it true; nothing checks it but the person reading it.
- every fact has a source, and every gap is
NEEDS CLIENT; - the kit is taken whole, or each thing taken out is under Decisions;
- every default has been said back and answered;
- the icon: the business's mark, or the monogram said back and accepted;
- the design: adapted, or the developer said to keep the example's look;
- nothing of the example's words or photographs left, or each one kept by the developer's say;
- the developer has read the brief and said yes.