Skip to main content
Q-Code

Content · 5 modules

What are the content modules?

The content modules are the five behind the words, pictures and structure a visitor reads: blog, FAQ, testimonials, gallery and footer.

Posts, reviews and images become rows changed in a panel and seen live, every photograph is stored once and sized at the edge, and the footer collects the links every other module has registered. Routine editing costs nothing and never queues behind a rebuild.

The 5 modulesAll 20 modules

Why this group exists

What content is for.

Most requests made of a website are content requests: a new post, a review worth showing off, a swapped photograph, a footer link that should exist. Sending any of those through a build is slow, and spends a build on something that was never a code change.

So each of these lives in a database and renders at request time or at the next publish, and what gets written passes through the project’s own brand voice first, which is why a blog post and a testimonial reply on the same site still sound like they came from the same place. The blog reads the site’s own visibility report and keyword list before it decides what to write, which keeps generated posts on the right side of Google’s people-first content guidance and its spam policies on scaled content.

The modules

5 in this group.

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.

FAQ

@ccd/faq

A visible questions-and-answers page, marked up as FAQPage for exactly what it shows.

  • Renders every approved entry into the static build, so the structured data matches what a crawler can see.
  • Refreshes in the browser the moment an answer changes, without waiting for the next publish.
  • Emits FAQPage markup for exactly the questions on the page, never more.

Testimonials

@ccd/testimonials

Collect, approve and place customer quotes, as a wall or a carousel.

  • Sends a one-question request by email and turns the answer into a pending entry.
  • Publishes nothing until you approve it.
  • Emits review markup only for the quotes actually visible on the page.

Q&A

Questions about the content modules

Does editing content trigger a rebuild?

Only the footer’s links do, because they are read at build time. Blog posts, FAQ answers, testimonials and gallery uploads all save straight to the database and appear on the next page view.

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.

Can I show a testimonial before approving it?

No, and that is deliberate. Entries arrive pending and appear on the site only once you have approved them.

The other groups

Where to look next.

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