Skip to content

Start here: the first site, in twelve steps ​

The card: each step's tool or command, the rule that bites there with its code, and the page that says why. Read the pages when a step is yours.

  1. The brief — every question at once, before create_site; build on the yes: the stack (offer Astro), the currency, paid online or on the spot (ask, never assume), where enquiries go, the language, the design, the photographs, the icon. Bookings take their kind's kit whole; a shop, jtk add shop. → the brief, kits, the shop

  2. Make the site — create_site with the slug, the name, locale, locales, bookings (a kit's kind), shop, blog, design; with bookings or a shop the brief's currency (asked, never guessed). The kit's jtk create commits contract 3, the quick template in Brumy's design (brumy.ch) — design: custom is a stage; its words and people are placeholders — write the site in their language before they look. next says the first build; give a person get_preview_link now. With a terminal: scaffold: false, then npx @jtakeit/astro create <dir> (the same options), the dev server, open_dev_session and its run; give the developer the localhost. Fill BRIEF.md from the first answer. → connecting a site, working on a site locally

  3. Declare the blocks in src/content/blocks.ts; npx @jtakeit/astro schema writes jtk/schema.json, mints missing ids and _keys — JTK_E_UNNAMED. A service has takes; a price is costs or rates; two rows on a minute are two prices — JTK_E_DIARY_NOT_READY. A date, an hour, a link is the owner's even unshown: no_tap_target, beside its field — JTK_W_OWNER_LOCKED. Entry types: form, ends_by (ended), JTK_W_DATE_HIDES. → the schema, modules

  4. Write the content — a page jtk/pages/<path>.json, {id, path, name, seo, blocks}; an entry jtk/entries/<collection>/<slug>.json, its values under fields; the text on every page jtk/shared.json. A value is its kind's: minutes for a time, {"minor": 4500} for money, an id for a ref — JTK_E_DOCUMENT_INVALID. Another language is <name>.<locale>.json beside the original, of its id, only the words by _key — a price there is JTK_E_TRANSLATION_SHARED; what is booked is in every language; get_site says what is left to translate. → the files under jtk/, several languages

  5. The settings — jtk/modules/bookings.json is {"v": 1, "settings": {…}}, each row with its _key. A business open past midnight writes the hours after it on the calendar day whose clock shows them. A service priced by the hour of the week covers every open hour, or the uncovered hour is not sold — JTK_W_UNPRICED_HOURS. → bookings on the site

  6. Judge before the push — validate_schema with the schema, the jtk/ files, translations too (jtk schema --judge from the tree), and site_id: the settings, the entries and the currency in one answer. Act on advice — a service as a post, hours typed twice — JTK_W_MODULE_POST, JTK_W_MODULE_TWIN. → the contract

  7. Annotate — every field a person taps carries data-jtk-path, read off the built HTML, never the component: jtkit lint dist/ on your build — JTK_E_UNANNOTATED_FIELD. An enquiry form's controls are the block's asks — JTK_E_FORM_FIELD_UNDECLARED. → connecting a site · annotations

  8. Push, then commit_and_build — nothing public. get_site says where the code lives (code). First push: a GitHub remote in the copy → ask once (that repository, with our App a person installs, and attach_repo; or jtakeit); none → push_code, run its command, and say so. get_build until it settles, else get_build_log. «That slug is taken» with no id is another account's site. → draft, saved, published, where the code lives

  9. Read what was built, and look at it — get_built_page is the HTML; with shot: "phone", the page as a visitor's phone draws it, in frames.

  10. Preflight — preflight with try_booking (a shop: try_order) before saying done: the form says what it sends in data-sends, and a field the platform does not take is dropped from a stranger's booking — JTK_E_BOOKING_FIELD_UNKNOWN. → bookings on the site · the form

  11. Hand over what is a person's — the launch, the channel the enquiries go to, the domain, another agent: the panel does those, and preflight says whose step each is. You cannot read the client's customers. → driving it from an agent, your client's data

  12. Later — pull first (git pull, or pull_code and jtk pull); commit; push_code or import_branch; commit_and_build. Content not imported — a git push, or a document where you and the person's unsaved work changed one field (JTK_E_DRAFT_AHEAD, named in waited) — waits in the branch until the next save or the editor's opening brings it in under the draft; after launch the words are the panel's, the shape and seed text the repository's. get_site says what the panel holds unsaved, and on a launched site a build is a candidate a person publishes. → working on a site locally

When a tool refuses, the code is the page: every error code.