The stack is not the product
For a small publishing team, the product is the weekly machine: draft, edit, publish, promote, monetize, recover. Themes and page builders are secondary. If the machine is slow, the brand suffers no matter how polished the homepage looks.
The five jobs a publishing stack must cover
1. Editorial flow that matches reality
Writers, editors, and publishers need clear roles. Drafts should move forward without shared passwords or Slack screenshots. If two people can overwrite the same live article by accident, the CMS is not ready.
2. Paid access without duct tape
Metered or subscription access has to be boring and reliable. Payment failures, expired sessions, and subscriber-only pages should be tested as carefully as the lead story layout.
3. Growth surfaces that staff can operate
Newsletters, SEO basics, and analytics only help if someone on the team owns them. A half-configured plugin farm is worse than a short list of tools with clear owners.
4. Recovery that does not depend on one hero
Backups, staging, DNS notes, and a rollback path matter more than a new animation library. Ask: if the site breaks on Friday evening, can the owner restore without us?
5. Handoff that survives turnover
Publishing teams change. The operating docs, access inventory, and maintenance cadence must outlive any single contractor relationship.
A practical evaluation scorecard
Score each candidate stack 1–5 on:
| Requirement | Why it matters |
|---|---|
| Role-based publishing | Stops accidental live edits |
| Subscription / paywall reliability | Protects revenue |
| Backup + staging path | Protects uptime |
| Owner documentation quality | Protects continuity |
| Security baseline | Protects trust |
Ignore marketing claims that do not map to those five.
Bottom line
Choose the stack that makes Tuesday's publishing day calm. Fancy architecture that only the original builder can operate is a liability dressed as craftsmanship.