As standard

What comes as standard

Every Q-Code site includes an admin area, a contact form and inbox, a blog, live editable content and the full search kit, from its first build.

None of it is a tier or an add-on. It is in the shared template, which means no site is ever missing a piece because nobody thought to ask for it, and improving the template improves every site built from it.

In every build

The foundation

Findable by people and by machines

Titles, descriptions, Open Graph cards, canonical links, a sitemap, structured data and an llms.txt summary, generated from the site rather than bolted on. Search engines and answer engines are both first-class readers.

An admin area you actually use

Testimonials, questions and answers, your enquiry inbox, social links and the posting schedule, each with its own panel. Content edits are database writes: about a second, no rebuild, nothing spent.

A contact form that reaches you

Submissions land in an inbox on the site, with spam traps that answer politely and store nothing. Replies are sent from an address on your own domain, not from a shared one.

A blog that can write itself

Ask for a post and get a finished one: researched against the site, written to a fixed style contract, illustrated, checked, and held as a draft until you publish it. Or set a schedule and let it run.

Your domain, your certificate

Bring a domain you own, delegate it, or keep your DNS where it is and add the records the panel gives you. All three are supported, and the panel never sends you to a dashboard to work something out.

Accessible and fast by construction

Semantic landmarks, one main heading per page, visible focus, enforced alt text, contrast-checked colour, and images that reserve their space so nothing jumps as the page loads. Checked on every single build.

Admin

The panels you actually open

Each of these writes to a database rather than rebuilding the site. An edit takes about a second, spends nothing, and the build machine stays asleep.

Inbox: Enquiries from the contact form, searchable and sortable, with read state. Replies go out from an address on your own domain, and a draft can be written for you from what the site already says.
Testimonials: Add, edit, reorder and remove reviews. Ratings are optional and stay optional, because a rating invented to fill the stars is published as a claim a customer never made.
Questions: The questions and answers shown on the site and marked up for answer engines. An answer can be drafted from the site's own knowledge, and it will tell you when the site cannot honestly answer something.
Blog: Ask for a post, review the drafts, publish or withdraw. Drafts are readable here without ever appearing in anything served to the public.
Schedule: Posting on a schedule, in your own timezone, stating in plain words when the next one runs and what will happen. Fully automatic still means draft, check, then publish.
Social links: A URL is the switch. Add one and the icon appears in the footer; clear it and the icon goes. The same links are declared to search engines, so the two cannot drift apart.

Blog posts are the deliberate exception. A post carries generated images, a feed entry, a sitemap URL and its own structured data, so writing or publishing one is a build. The panel says so rather than implying it is instant like the rest.

Infrastructure

Underneath

Your code, your repository

Every publish pushes the whole project to a private GitHub repository of yours. The build machine is a working copy, not the only copy, and that is not a promise: it is how a project was recovered intact after its workspace was lost.

A domain, three ways

Use one already here, delegate one you own, or keep your DNS where it is and add the records the panel generates. Every value has a copy button and every waiting state says what is being waited on.

Attach only ever adds

A snapshot is taken of your DNS before any write and compared field by field afterwards. If a single pre-existing record changed, the whole thing stops. Mail records are never touched.

Static where it counts

The published site is files on a global network. It keeps serving whether or not the build machine is awake, which is also why it costs nothing to keep online.

How the search kit works is on search visibility, what each kind of change costs is on what it costs, and how any of it is protected is on security.