Your First Content Piece

Draft a content piece end to end in m18t: pick a content type, write in the editor, set AI-assisted SEO, and send it to your CMS or social now or on a schedule.

What you'll learn

  • How the unified content table holds every format in one place.
  • How to draft a piece, set its SEO, and push it to a channel.
  • What's a single click today and what isn't.

m18t keeps every kind of writing — blog posts, news posts, web pages, help articles, social posts, video posts, and any custom type you define — in one content table with one editor and one status set. The reason is silo collapse: a social post and the blog post it promotes shouldn't live in two unrelated tools.

What keeps that single table organized is content types. A type is a template that carries its own rules — its URL prefix, its schema.org type, its supported locales, its SEO defaults. You set those once per (brand × type), and every piece of that type inherits them, so the metadata is mostly built for you by the time you sit down to write.

Make sure the right brand is selected in the Brand Switcher first — content is brand-scoped, and a piece is created under whatever brand is active.

Step 1 — Create a draft

  1. Open Content Manager in the sidebar (/studio/content).
  2. Confirm your active brand in the switcher.
  3. Start a new piece (the create action lives at /studio/content/create).
  4. Pick a content type — blog-post, social-post, or one of your own.
  5. Create the draft.

Step 2 — Write and format

The editor is block-style rich text.

  1. Title — give it one; a URL slug is derived from it automatically, and you can edit the slug.
  2. Body — write in the main editor. It supports headings, lists, tables, code blocks, blockquotes, and task lists.
  3. Cover image — assign one from your asset library or generate one in the Graphics Generator.

Your work autosaves. The content editor is organized into tabs — General, Content, Media, SEO, Localization — and a Publishing tab that appears only after the first save.

Step 3 — SEO

Because the piece is tied to a content type, m18t builds most of the SEO for you on the SEO tab.

  1. Canonical URL — computed from your brand's website URL + the content type's path prefix + the slug. See Canonical URLs.
  2. Meta title / description / keywords — editable fields. Don't want to write them by hand? Use Generate Meta with AI (the sparkles button on each field). The SEO prompt gets the resolved canonical URL injected, so the model can't invent a URL.

The AI buttons are BYOK-gated — they stay greyed out until you've added an AI key in the Secret Vault.

Step 4 — Publish

m18t is a workspace that pushes data out to channels — your headless CMS or a social network. To push to a CMS:

  1. Open the Publishing tab (visible after the first save).
  2. Choose Push to CMS (it reads Update in CMS after the first sync), pick the environment (Production / Development / Local), and run it.

m18t converts the rich text to the format your CMS wants, authenticates using the credential in your vault, sends the payload, and writes a sync-log entry. Publishing to Facebook and Instagram works the same way from the social channels — see Publishing to Facebook & Instagram.

Get one thing right early: a date and a send are two different acts. Setting Scheduled At puts the piece on the calendar, which is your plan. To have it go out on its own, queue the send: press Schedule pending on the Publishing tab, and it fires at that time without you. See Scheduling vs. Publishing.

FAQ

Why is the "Generate Meta with AI" button greyed out? You haven't added an AI key. SEO generation is BYOK-gated. Add an OpenAI, Google, or Anthropic key in the Secret Vault and the sparkles buttons light up.

Where's the Publishing tab? It only appears after you save the piece once. Save the draft, then it shows up alongside General, Content, Media, SEO, and Localization.

Will my post publish at its scheduled time? Only if you queued a send for that time. The date on its own is a plan; Schedule pending on the Publishing tab is what queues the send, and that send fires on its own. See Scheduling vs. Publishing.

Which CMS can I push to? Strapi, natively. Other CMS vendors (WordPress, Sanity, Contentful, Payload) are roadmap. If you push to a CMS, that's the one m18t supports today. See Pushing to Your CMS.

Can one piece go to several channels? Yes. A single content piece can push to your CMS and to Facebook + Instagram, with per-channel publish state tracked on the same row.

What's next

Was this article helpful?