Skip to main content
Q-Code

Engagement · 3 modules

What are the engagement modules?

The engagement modules are the three that handle people getting in touch: forms and inbox, testimonials, and social profiles.

Each one turns something that normally leaks into an email account into a row you can see, answer and reuse on the site, scheduled posting included. They are the difference between a site that is a brochure and a site that is a channel.

Why this group exists

What engagement is for.

An enquiry that arrives as an email is an enquiry that is one deleted message from being lost, and a five-star review sitting in someone else’s app is a review doing nothing for the page it should be on.

These modules keep both on the site. Enquiries land in an inbox with a thread and a status, reviews become entries you place where they help, and the same posting queue that pushes to social keeps a record of what went out and when.

The modules

3 in this group.

Forms and inbox

@ccd/forms

Any form on the site, with the replies threaded in a shared inbox.

  • Works with JavaScript unavailable, because a contact form is the last thing that should need it.
  • Filters spam without a CAPTCHA in the visitor’s way.
  • Threads the reply, so a conversation is one place rather than a forwarded chain.

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.

Social profiles

@ccd/social

Your profiles in the footer and in the structured data, plus a posting queue.

  • Declares every profile once, so the footer links and the sameAs markup cannot drift apart.
  • Queues posts with the images already sized for each network.
  • Keeps what was posted and when, so a schedule can be looked at rather than remembered.

Q&A

Questions about the engagement modules

Do forms work if JavaScript fails?

Yes. Every form posts natively and is enhanced afterwards. A contact form that only works when a script loads is a contact form that quietly loses enquiries.

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.

Does the social module post automatically?

It posts what is in the queue at the times you set. Adding something to the queue is a decision you make; publishing it on schedule is the part it takes off you.

The other groups

Where to look next.

  • Foundations

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

  • Content

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

  • Commerce

    Catalogue engine, Payments, Bookings.

  • 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.