Pushing to Your CMS
What you'll learn
- Why m18t feeds your headless CMS instead of being one.
- How to push a content piece to Strapi, and what gets sent.
- How environments and localized siblings are handled.
The concept: m18t writes, your CMS serves
A CMS like Strapi serves data to your website's front end. m18t is where you write, review, and optimize — then it pushes the finished piece across to your CMS. You keep one writing surface across every brand and a clean separation: drafting and SEO live in m18t; delivery to your site lives in your CMS.
Native CMS support today is Strapi v5. Other vendors (WordPress, Sanity, Contentful, Payload) are roadmap — the adapter architecture exists, but only Strapi is wired right now. If your stack is Strapi, this is a first-class path; if it isn't, this article is a preview of where it's headed.
When you push, m18t converts the rich-text body to Markdown, assembles the SEO metadata, and sends it to your brand's connected Strapi instance for the chosen environment.
How to push content to Strapi
- Set up the Strapi connection for the brand first — instance URL, API token, environment. Tokens live in the vault.
- Open the content piece and go to the Publishing tab (it appears after the first save).
- In the Push to CMS section, pick the environment: Production, Development, or Local.
- Click Push to CMS. If this piece has already been synced, the button reads Update in CMS instead, and the section shows the existing document ID.
The section tells you whether the piece is synced yet and, once it is, shows its Strapi document ID so you can confirm the link.
Localized content
If the piece belongs to a locale group, the Push to CMS section shows a Localization Sync Status panel listing the current piece and each sibling, with whether each has been pushed. Tick Sync current and all unsynced sibling locales to push the current piece plus any unsynced siblings and link them through Strapi's localization API in one operation. See Locale Groups & Translation for the full picture.
Common variations
Multiple environments per brand. A brand can hold separate Strapi connections for production, development, and local. The environment select on the push controls which one you're targeting, so you can push to a staging instance before production.
Checking the result. The Publishing tab has a Recent Activity log, and View All Logs opens the full record. If a push fails, the error is recorded there.
FAQ
Can I push to WordPress / Sanity / Contentful / Payload? Not natively today — Strapi v5 is the only wired CMS. Other vendors are roadmap. Don't plan around them being live yet.
Where does the content type matter? Your m18t content type maps to the target collection in Strapi. Make sure your Strapi collection exists and (for translations) has i18n localization enabled, or Strapi will reject the payload.
What's the difference between "Push to CMS" and "Update in CMS"? First push creates the entry and the button says Push to CMS. After that, m18t knows the document ID, so the button becomes Update in CMS and subsequent pushes update the same entry.
Does pushing to my CMS also post to social? No. CMS push and social publishing are separate actions on the Publishing tab. Each destination is triggered on its own.
Will it push automatically when I schedule a date? No. There's no auto-publish — pushing to your CMS is a manual click. See Scheduling vs. Publishing.