Documentation
This page covers everyday use: you open the admin panel, build your pages, organise your menu. Not a line of code, not a single API call. Running the site through an agent is described separately, and stays optional — everything below works without it.
Three settings shape the look of every page to come. Set them first, and you will not have to rework each page afterwards.
Identity
Settings ▸ Site identity. Name, logo, tab icon, contact details and type of business. This information also feeds the structured data that search engines read: you never enter it twice.
Colours
Ten theme colours, including accent, background, text and muted text. Every page refers to them by variable rather than by value: change the accent here and it changes everywhere, buttons and links included.
Fonts
Eleven roles — headings, body, links, buttons, menu — set separately on desktop, tablet and mobile. Always set a role and its hover state together: a different hover size makes the button jump under the cursor.
A page is a stack with four levels. It is the only concept you need: everything else follows from it, and the editor never offers to create an element without its parent.
Page
└─ Section a horizontal band: its background, its margins
└─ Row a row, split into 1 to 12 columns
└─ Block a cell in a column
└─ Content text, image, button, form, calendar…
The section carries the background and the vertical space. The row carries the column layout. The block is the cell, and the content is what you put in it. A section with no row is perfectly valid: it gives the page room to breathe.
Columns are counted out of twelve
A three-column row is laid out as 4-4-4, two unequal columns as 8-4. The total is twelve. Above all: you need as many segments as blocks — three blocks on a one-segment layout end up squashed.
Four devices, always
Phone up to 767 px, tablet up to 991 px, laptop up to 1199 px, desktop beyond. Every setting exists for all four. Three columns on desktop happily become one on a phone: 12-12-12.
The routine is always the same, whatever the page.
Check the page on a phone before publishing. A site that looks right only on its designer's screen is a broken site for most of its visitors — and the editor lets you switch from one device to another without saving anything.
Two separate mechanisms that are often confused: categories organise pages among themselves, the menu guides the visitor. One does not imply the other — a page can live in a category without appearing in the menu, which is the usual case once a site grows past a dozen pages.
Categories and subcategories
They give you a working tree, and optionally a path in the address. Show the category in the URL and the page lands at /category/subcategory/page/ — which is what this site does: this page is filed under “documentation”.
Menus
A main menu and a footer menu, each an ordered list of entries pointing to pages or free addresses. The menu has its own style, independent of the site fonts; that is where you set its font, not in the general settings.
Each one is managed from its own tab and placed in a page as a block. They are independent: a showcase site does not switch on the store or the courses, and never sees them.
Products, variants, stock, VAT, shipping, orders. Structured data for product pages is generated automatically.
Appointment types, availability, time slots, automatic reminders. The calendar goes into any page as a block.
Scored tests, profiles and combinations of criteria. The result can trigger an email, a redirect or access to content.
Learning paths, modules, progress, quizzes and certificates. Access is granted on enrolment or after payment.
Sixty-seven events, each with its own editable template. Mandatory emails cannot be switched off.
Twenty-four content types, including fourteen dynamic blocks: FAQ, tabs, carousel, pricing table, countdown.
What runs without you, and the one step that stays manual.
Updating
Settings ▸ Update JEIKO. A badge appears when a newer version is released, and the page tells you which one. The update verifies the package checksum, backs up the database, applies migrations and restarts the service. It is the only manual step.
The cache
The site caches the site object, page bodies and rendered menus. There is nothing to configure: every saved change purges exactly what it needs to. A purge button still exists in the settings, for when you want to be sure.
Performance
Images are generated in six sizes on upload and served through srcset, stylesheets are minified on publication, costly template fragments are cached. A PageSpeed audit runs from the admin panel and keeps its history.
Backups
The database is backed up before every update. Beyond that, backups are your hosting's job: JEIKO runs on your server, with your data — that is the whole point, and it leaves that responsibility with you.
Step by step, from the first setting to the richest module.
From installation to the first live page, in seven steps.
The Settings menu and every variable of the .env file.
How a page is built, and the twenty-three blocks.
Profiles, combinations, dimensions mode, simulation.
Outline, videos, quizzes, paid or granted access.
Types, slots, payment, waiting list.
Subject, body, variables, preview, default version.
The commands to install, update and remove a site.
Hand the building and upkeep of the site to Claude.
Products, subscriptions, discount codes, invoices, Google Shopping.
Email, Stripe, Google Merchant, PageSpeed, Google Calendar, social login, licence.
Lists, proof of consent, scheduled sending, tracking, CRM.
Everything above can also be done by a program. You then create an agent: a named mandate, with its roles, its expiry date and its call limit. That mandate — and nothing else — is what you give to an assistant. The agent never touches the database, and goes through the same checks you do in the interface.
Creating one takes a minute, from Settings ▸ AI agents:
The assistant then needs no documentation from you: the API's manual is served by the API itself, generated from the code.
The simplest route is the connector: Claude plugs into your site from claude.ai, the mobile app or Claude Code, with no key to copy. The step-by-step guide takes three steps.