9. Marketing & Content (CMS)
Purpose — Blog with a DIY WYSIWYG editor, testimonials (auto-collected post-install), reviews, FAQ, case studies, campaigns, SEO, and newsletters. Powered by Payload CMS + Listmonk.
Personas served
Marketing admin, Customer (reads/reviews), Super admin.
Key capabilities
- Blog / resource center — DIY block WYSIWYG (Payload); buying guides, "how to size your inverter," energy-saving content; strong SEO. (notes #2)
- Testimonials / reviews / ratings — product + service reviews; auto-request 1 week after installation via delayed BullMQ job (Eventing); moderation → publish. (notes #4)
- Case studies / installations gallery — "projects we've done" (big for solar).
- Landing pages, banners, coupons, CMS — campaign pages; coupon codes tie to Medusa promotions.
- Campaigns — incl. broken/cracked-panel repair marketing (notes #5) targeting external-asset audience.
- FAQ / product Q&A / comparison guides.
- Calculators — ROI / bill-savings (solar) lead magnets (Storefront).
- Newsletters — authored in Payload, sent via Listmonk (Newsletter).
- Email/SMS/WhatsApp campaigns — via Notifications.
- Multilingual content — Payload localization (i18n).
Data owned
Mongo (Payload): post, page, testimonial, faq, caseStudy, banner, media metadata. See cms-content. Coupons reference Medusa promotions.
Events
- Emits:
content.published,testimonial.submitted,campaign.launched. - Consumes:
installation.completed(→ delayed testimonial request),segment.changed(audiences).
APIs
- Payload REST/GraphQL for content (locale-aware).
POST /testimonials(customer submit),GET /content/:slug(storefront, localized)POST /campaigns,GET /faq
Tenant-config knobs
Enabled content types; testimonial delay (default 7d) + template; default locale; campaign templates; review moderation on/off.
Dependencies
Newsletter, Notifications, CRM, FSM, i18n.
Open questions
- Reviews tied strictly to verified purchase/asset, or open?
- Newsletter authoring fully in Payload or partly in Listmonk's own editor?