Growth · 3 modules
The growth modules are the three aimed at what happens after someone finds you: newsletter, lead capture and an agent interface.
The first two turn attention into a list and a pipeline. The third accepts that a growing share of visitors are not people, and gives them something better to read than scraped HTML — which is what the agent interface publishes.
Why this group exists
Traffic that arrives and leaves without becoming a name is traffic you paid for once. A list and a pipeline are how a visit turns into something you can follow up.
The third module is here because the shape of a visit is changing. Answer engines and assistants now read pages on behalf of people, and a site that publishes a clean machine description gets summarised accurately instead of approximately.
The modules
@ccd/newsletter
A list you own, sent from your own domain, with double opt-in as the default.
@ccd/leads
Turn enquiries, bookings and downloads into one pipeline with a status each.
@ccd/agents
A machine-readable description of the site, for the visitors that are not people.
Q&A
No. The list lives in the project’s own database and exports in full on request, addresses and confirmation timestamps included.
Because an answer engine that has to infer what a site is for will sometimes infer wrong, and a page it misreads is a page it cites badly or not at all. A short, accurate description is cheap insurance.
You can block the ones that collect training data, and that setting is one flag. Search and citation crawlers stay allowed, because blocking those removes the site from AI answers without protecting anything.
The other groups
Visibility engine, Domains and SSL, Branded email, Analytics.
Editable pages, Self-improving blog, Media library, Brand voice.
Catalogue engine, Payments, Bookings.
Forms and inbox, Testimonials, Social profiles.
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.