Skip to main content
Q-Code

Content · 4 modules

What are the content modules?

The content modules are the four that let a site be edited without a build: pages, blog, media and brand voice.

Copy, posts and images become rows you change in a panel and see live, and every word the AI writes passes through one voice profile first. The result is that routine editing costs nothing and never queues behind a rebuild.

The 4 modulesAll 17 modules

Why this group exists

What content is for.

Most requests made of a website are content requests. A new paragraph, a swapped photograph, a post about a thing that happened last week. Sending those through a build is slow, and it spends a build on something that was never a code change.

So content lives in a database and renders at request time, and the AI that helps write it reads one voice profile before it writes a word. That profile is the reason two posts written six months apart still sound like the same site.

The modules

4 in this group.

Editable pages

@ccd/pages

Headings, paragraphs and images on any page become fields in a panel.

  • Marks a block as editable in the markup, and it appears in the panel with no further wiring.
  • Saves instantly, with no rebuild and no deploy.
  • Keeps the previous value, so a bad edit is one click from being undone.

Self-improving blog

@ccd/blog

A blog that reads the site’s own visibility report before it decides what to write.

  • Suggests topics from the keyword list and the gaps the audit found, not from a generic content calendar.
  • Drafts in the project’s brand voice, with the answer-ready opening the house style asks for.
  • Publishes on a schedule you set, and every post is a draft you approve first.

Media library

@ccd/media

Upload once and get every size, format and dimension the page needs.

  • Converts to AVIF and WebP, with the original kept as the fallback.
  • Writes width and height into the markup, so the page does not jump as it loads.
  • Asks for alt text on upload, and will not let an image onto a page without it.

Brand voice

@ccd/voice

One voice profile that every generated word on the project passes through.

  • Learns from the copy already on the site, then holds that register across posts, replies and descriptions.
  • Records the things to avoid as firmly as the things to do, which is the half most tools skip.
  • Applies to every module that generates text, so a catalogue description and a blog post match.

Q&A

Questions about the content modules

Does editing content trigger a rebuild?

No. Content modules read from the database at request time, so a saved edit is live on the next page view. Builds are for code and layout.

Will the blog publish without me seeing it first?

Only if you turn that on. The default is that every post arrives as a draft and waits for approval, because a post published in the wrong register is harder to take back than to review.

What does the brand voice module actually change?

It sits in front of every text generation on the project. The same request produces a different answer on a solicitor’s site than on a skate shop, because the profile describes register, vocabulary, sentence length and the things never to say.

The other groups

Where to look next.

  • Foundations

    Visibility engine, Domains and SSL, Branded email, Analytics.

  • 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