Skip to main content
Q-Code

Foundations · 4 modules

What are the foundation modules?

The foundation modules are the four every Q-Code project installs first: visibility, domains, mail and analytics.

They are what turns a built site into a published one — a real address, a real sending identity, honest numbers, and a score that says whether anyone can find it. Nothing else in the library assumes a site is reachable until these are in place.

The 4 modulesAll 17 modules

Why this group exists

What foundations is for.

A site that builds but cannot be found, cannot send an email and cannot tell you what happened is not finished, it is a demo. These four close that gap, and they are deliberately boring: they do the part that is the same on every project so that no project has to solve it again.

They also share one rule. Everything they configure lives on infrastructure in your name — the Cloudflare zone, the DNS records, the sending domain, the analytics token. Uninstalling a module removes the code that reads them, never the accounts that hold them.

The modules

4 in this group.

Visibility engine

@ccd/visibility

One score across SEO, AEO, LLMO, conversion and agent readiness, measured on the built HTML.

  • Audits the pages a crawler actually receives, not the source they were written in.
  • Explains every finding in plain English, then hands it back as a fix you can approve.
  • Adds the SEO settings panel: title templates, canonical host, social image, crawler policy.

Domains and SSL

@ccd/domains

Attach a real custom domain three different ways, with a certificate issued in minutes.

  • Registers a new domain, moves one you own, or points one you would rather leave where it is.
  • Writes the DNS records for you and verifies them before it claims to be done.
  • Keeps the zone on a Cloudflare account you hold, so you can leave without asking.

Branded email

@ccd/mail

Send from the site’s own address, with SPF, DKIM and DMARC set up properly.

  • Sends form replies, receipts and broadcasts from hello@your-domain rather than a shared relay.
  • Publishes the three authentication records and re-checks them, because one typo is silent.
  • Logs every send, so a message that did not arrive has somewhere to be looked up.

Analytics

@ccd/analytics

Server-side page and event counts with no cookies and no consent banner.

  • Reports pages, referrers and countries without storing anything that identifies a visitor.
  • Needs no cookie banner, because it sets no cookie.
  • Marks the events that matter to you as goals, so conversion is measured rather than guessed.

Q&A

Questions about the foundations modules

Do I have to install all four?

No. Each is independent and a site works with none of them. In practice a project that is going to be published installs all four within its first week, which is why they are grouped rather than scattered.

Does the analytics module need a cookie banner?

No. It counts requests server-side and stores nothing that identifies a person, so there is no cookie to ask permission for. Adding a second tracker on top would change that answer.

What happens to my domain if I stop using Q-Code?

Nothing. The domain and its DNS zone sit on a Cloudflare account in your name. Removing the module removes the code that reads the zone; it does not touch the zone.

The other groups

Where to look next.

  • Content

    Editable pages, Self-improving blog, Media library, Brand voice.

  • Commerce

    Catalogue engine, Payments, Bookings.

  • Engagement

    Forms and inbox, Testimonials, Social profiles.

  • Growth

    Newsletter, Lead capture, Agent interface.

Describe the feature, not the module.

You are not expected to know which of these you need. Say what the site should do and the build reaches for the parts that already exist.

See how a build worksThe whole library