Prompt
I'm building a marketing site with previews, workflows, and reusable content blocks
Latest observation
Oct 21, 2026
OpenAI APIWeb search: off
That sounds like a great fit for a flexible content system.
A solid approach is to structure it around reusable blocks + workflow states + previewable variants. For example:
- Content blocks: hero, feature grid, testimonial, CTA, FAQ, etc.
- Previews: draft/approved/published previews, device breakpoints, and page-level preview routes.
- Workflows: author → review → approve → publish, with optional scheduling and rollback.
- Reuse: shared blocks or templates that can be placed across multiple pages and updated centrally.
A few implementation ideas:
- Use a component-based CMS model so editors assemble pages from blocks.
- Store each block as structured data rather than raw HTML.
- Add a preview API that can render unpublished content safely.
- Build versioning so workflows can compare, approve, and restore previous revisions.
- Consider global blocks vs page-specific blocks to support reuse without duplication.
If you want, I can help you design:
- a content model/schema,
- a preview architecture,
- or a workflow system for approvals and publishing.