Module library
The Q-Code module library holds 17 installable modules, grouped into foundations, content, commerce, engagement and growth.
A module is a feature that has already been built, argued about and hardened on other projects, so installing one is a switch rather than a build. Each brings its own admin panel, its own structured data and its own audit rules with it.
Five groups
Not by size or by price. Each group answers one question about a project, and most projects work through them roughly in this order.
Visibility, domains, mail and analytics: the four modules every Q-Code project installs first, and what each one actually does once it is on.
Visibility engine
@ccd/visibility
Domains and SSL
@ccd/domains
Branded email
@ccd/mail
Analytics
@ccd/analytics
Pages, blog, media and brand voice: the four Q-Code modules that make copy, posts and images editable in a panel rather than in a build.
Editable pages
@ccd/pages
Self-improving blog
@ccd/blog
Media library
@ccd/media
Brand voice
@ccd/voice
Catalogue, payments and bookings: the three Q-Code modules for selling a thing, selling a slot, or listing stock that is not for sale.
Catalogue engine
@ccd/catalogue
Payments
@ccd/payments
Bookings
@ccd/bookings
Forms and inbox, testimonials, and social posting: the three Q-Code modules that turn a brochure site into somewhere people actually reach you.
Forms and inbox
@ccd/forms
Testimonials
@ccd/testimonials
Social profiles
@ccd/social
Newsletter, lead capture and an agent interface: the three Q-Code growth modules for what happens after someone finds the site.
Newsletter
@ccd/newsletter
Lead capture
@ccd/leads
Agent interface
@ccd/agents
What a module is
A library is only worth having if its parts behave predictably. These are the rules a module has to satisfy before it goes in.
A bug found on one project is fixed in the module, and every project that has it installed gets the fix. That is the whole economic argument for a library.
A module that adds data adds the screen for editing it. No module leaves you with a database table and no way to reach it.
Structured data comes with the module and describes only what the module actually renders, so installing one cannot quietly cost you a point of visibility.
A module that adds a page registers its own navigation link. A module that adds a section registers for a slot. Installing it puts it somewhere a visitor can find.
Uninstalling removes the code and the links. It does not remove your data, and it never touches an account in your name.
Modules use the guaranteed token vocabulary rather than their own colours, so an installed module looks like the site it landed on instead of like a widget.
All of them
Sorted by group. The install name is the real one, and a few of these are already load-bearing in the template itself.
| Module | Group | Package | What it does |
|---|---|---|---|
| Visibility engine | Foundations | @ccd/visibility | One score across SEO, AEO, LLMO, conversion and agent readiness, measured on the built HTML. |
| Domains and SSL | Foundations | @ccd/domains | Attach a real custom domain three different ways, with a certificate issued in minutes. |
| Branded email | Foundations | @ccd/mail | Send from the site’s own address, with SPF, DKIM and DMARC set up properly. |
| Analytics | Foundations | @ccd/analytics | Server-side page and event counts with no cookies and no consent banner. |
| Editable pages | Content | @ccd/pages | Headings, paragraphs and images on any page become fields in a panel. |
| Self-improving blog | Content | @ccd/blog | A blog that reads the site’s own visibility report before it decides what to write. |
| Media library | Content | @ccd/media | Upload once and get every size, format and dimension the page needs. |
| Brand voice | Content | @ccd/voice | One voice profile that every generated word on the project passes through. |
| Catalogue engine | Commerce | @ccd/catalogue | One listing engine that reshapes itself for cars, property, products or services. |
| Payments | Commerce | @ccd/payments | Stripe Checkout on your own Stripe account, with receipts from your own domain. |
| Bookings | Commerce | @ccd/bookings | Real availability, real time zones, and a deposit taken at the point of booking. |
| Forms and inbox | Engagement | @ccd/forms | Any form on the site, with the replies threaded in a shared inbox. |
| Testimonials | Engagement | @ccd/testimonials | Collect, approve and place customer quotes, as a wall or a carousel. |
| Social profiles | Engagement | @ccd/social | Your profiles in the footer and in the structured data, plus a posting queue. |
| Newsletter | Growth | @ccd/newsletter | A list you own, sent from your own domain, with double opt-in as the default. |
| Lead capture | Growth | @ccd/leads | Turn enquiries, bookings and downloads into one pipeline with a status each. |
| Agent interface | Growth | @ccd/agents | A machine-readable description of the site, for the visitors that are not people. |
Q&A
A build, which is minutes. It is not a bespoke development job, because the module already exists — what the build does is wire it into this project and place it on the pages where it belongs.
Yes. Anything can be built for a single project, and the ones that turn out to be generally useful become modules afterwards. That is where most of these came from.
Not measurably. Pages stay static HTML and ship no JavaScript unless a module genuinely needs interactivity, and the ones that do are loaded only when they scroll into view.
It stays in the project database and is exportable. Uninstalling removes the code that reads it and the links that pointed at it.
No. The library comes with the platform. What you pay separately for is what any of them consumes on your own accounts — Cloudflare, Stripe, mail — billed to you directly rather than resold.
You do not need to know which module you want. Describe what the site should do and the build picks the parts that already exist.