evonx
Log in
App template

Content CMS template for editorial and marketing teams

Plan, draft, review, and publish content with workflows that match editorial calendars. This CMS template models entries, locales, and publish states—not a page builder toy—so marketing and content ops ship on schedule with clear ownership.

Get started freeBrowse templates
cms.acme.mediaEditorial
Publishing calendar

Manage content entries through draft, review, and publish with scheduling.

In review17
Scheduled9
Published 7d28
  • Launch guide — ENScheduled Tue 9am
  • Launch guide — ESIn translation · Writer Ana
  • Changelog 0.42Approved · Publisher queue

What's included

Manage content entries through draft, review, and publish with scheduling.

Intended users

  • Editors
  • Writers
  • Marketing ops

Suggested stack

  • PostgreSQL
  • Next.js
  • CDN for assets

Core features

Content types and fields

Editorial calendar

Review and approval

Scheduled publishing

Locale variants

Main workflows

Submit for review

Writer finishes draft, assigns reviewer.

Approve and schedule

Editor approves, sets publish time.

Publish locale

Ship language variant independently when ready.

Database model / entities

Distinct domain entities — not a renamed generic CRUD list.

Content typeSchema for articles, pages, or releases.
EntryContent instance with status and publish time.
Locale variantTranslated or localized version of an entry.
ReviewApproval step with comments and decision.

User roles

  • Editor in chief
  • Writer
  • Reviewer
  • Publisher

Possible integrations

Applications built from this template can connect to these services via their APIs.

  • Resend
  • Slack
  • Cloudflare CDN
  • GitHub

Example prompt

Copy this into Evonx to start from a production-shaped brief instead of a blank canvas.

Build a content CMS with content types, entries, locale variants, and reviews. Include editorial calendar, scheduled publish, and role-based approvals. Use PostgreSQL with writer, reviewer, and publisher roles.

How Evonx customizes this template

Start from the domain model above, describe the workflows your team needs, and Evonx generates a working preview you can refine. For teams with an existing codebase, the same agent can extend repositories instead of starting from a blank project.

Related resources

Build CMS with AIContent teams evaluating a CMS with AI should expect models, drafts, and publish workflows in owned code. Use this page CRM templateTrack leads, accounts, and pipeline stages with activities your team can evolve in production. This template maps a B2B SaaS templateLaunch a multi-tenant product skeleton with auth, settings, and billing integration points.Admin dashboard templateCentralize configuration, user management, and monitoring for internal operators.Customer portal templateLet customers view orders, tickets, documents, and profile data without emailing your team.Inventory management templateTrack SKUs, warehouses, adjustments, and low-stock signals for fulfillment teams.

FAQ

Can locales publish on different schedules?

Yes. Locale variants carry their own status and publish times so translations are not blocked by each other.

Who can hit publish?

Publisher or editor-in-chief roles control go-live; writers stay in draft and review states.

Does this include a visual page builder?

It focuses on structured content workflows. Visual builders can be layered if your content types need layout blocks.

How do reviews leave an audit trail?

Review decisions and comments stay attached to the entry version that was approved.

Build production software with Evonx

Start from a template or connect an existing repository. Evonx helps you ship real applications with preview, evolution threads, and pull-request delivery—not disposable demos.

Get started freeSee AI for existing software