Connecting Your Live Site to the Marketora CMS

The Headless Architecture

Marketora uses a modern, decoupled architecture designed for both editorial flexibility and lightning-fast web performance. Your editorial interface and structured content repository are powered by the Marketora Headless CMS (Frappe), while your public-facing marketing site is rendered using Next.js with Incremental Static Regeneration (ISR).

How Content Travels from CMS to Live Web

1. Structured Content Storage: Articles, landing pages, guides, and templates are stored as structured documents in the CMS database.
2. The Validation Gate: When an author clicks Publish, the CMS enforces data integrity rules—ensuring required titles, routes, categories, and sanitization checks are met.
3. Automated Webhook Notification: Upon successful publication, the CMS triggers an internal revalidation webhook (/api/revalidate) sending the precise ISR cache tags affected by the change (such as help-article:{slug} or help-articles).
4. Instant Cache Purge: Next.js purges the cached static page on edge servers and re-renders the updated content on the next visitor request.

Publishing Pipeline Checklist

To ensure your published pages appear immediately:

• Verify that the document status is set to Published (Draft records are strictly excluded from public APIs).
• Ensure the route slug is clean, lower-cased, and without special characters.
• Confirm that your Next.js frontend has configured the matching REVALIDATE_SECRET in its environment settings.