CMS & Blogging

Publish posts, manage content, and run a blog on your Ploy site.

Ploy has a built-in content system, so you can run a full blog without a separate CMS. You don't write any code — just ask Ploy's Agent to draft, edit, and publish posts in plain language, and it handles the structure, styling, and SEO for you. When you'd rather keep editing in a tool you already use, you can also connect an external CMS and securely server-side render its content — API keys stay safe as Environment Variables, never exposed to the browser.

What a Blog Includes

Ask Ploy's Agent to set up a blog and it builds the whole thing for you:

• Index page — A /blog listing of all published posts, sorted by date.
• Post pages — Each post rendered as a styled article that matches your design system.
• Tag pages — Automatic /blog/tag/<tag> pages grouping related posts.
• Consistent structure — Every post shares the same fields — title, description, date, tags, author, cover image — so nothing is missed.
• SEO — Per-post titles, meta descriptions, Open Graph images, and structured data.

Creating & Editing Content

Just describe what you want — Ploy's Agent drafts the post, builds the page, and wires up the routes:

• "Set up a blog with an index page and tag filtering"
• "Write a post titled 'Our Series A' and publish it"
• "Tighten the intro on my latest post and add a closing CTA"
• "Import these posts from our Notion database"
• "Turn this LinkedIn post into a blog article"

Editing works the same way — point Ploy's Agent at any post and tell it what to change. Existing long-form content — legal text, prior blog posts — is moved in verbatim, not rewritten.

Tip: Prefer working in code? Posts live as files in your project, so you can also edit them directly and republish — but you never have to.

Always review before publishing. Ploy's Agent helps you draft and edit posts, but every piece of content on your site is yours to verify — a human should review it for accuracy, tone, and brand fit before it goes live. Search engines actively penalize unedited, low-quality AI-generated content, so use drafts as a starting point, not a final answer.

Draft & Published States

Every post is either a draft or published, so you can write ahead of time without anything going live before you're ready.

Moving a post between the two is just a quick ask:

• "Keep my next post as a draft for now"
• "Publish the Series A post"
• "Move that announcement back to draft"

Tip: Keep a backlog of drafts and have Ploy's Agent publish them on your schedule — nothing is visible until you say go.

Rich, Interactive Posts

Posts aren't limited to text, headings, and images. Because they're built on the same engine as the rest of your site, Ploy's Agent can bring real interactive elements right into the body of a post to make it come alive — just describe the moment you want:

• Interactive components — Tabs, accordions, carousels, calculators, and live demos inline with your copy.
• Charts & data — Charts, tables, and visualizations built from your own numbers.
• Embeds & media — Videos, code playgrounds, callouts, and CTAs that match your design system.
• Reusable blocks — Any section or component from your site, dropped into a post.

Ask for something like "add a pricing calculator after the second paragraph" or "embed a chart of our growth here," and Ploy's Agent builds it and places it for you — no code on your end.

Connecting an External CMS

Prefer to author in a dedicated CMS? You have a few options, in order of how tightly they integrate:

1. Native content — Draft and edit with Ploy's Agent. Fastest, fully owned, best performance.
2. Webhooks — Have your CMS send an event when content changes to trigger a Ploybook that updates and republishes your site. See Webhooks.
3. Reverse proxy — Serve a blog hosted elsewhere (e.g. a marketing CMS) under a path on your domain like /blog. See Reverse Proxy.
4. API + SSR — Pull content from a headless CMS at request time using server rendering, with API keys stored as Environment Variables.

Tip: Most teams start with native content for speed and SEO, and reach for an external CMS only when non-technical editors need a separate workflow.

What's Next?

• Understand the stack — See Site Builder for how pages, sections, and the design system fit together.
• Automate updates — Use Webhooks to sync content from external systems.
• Go live — Read Publishing & Deploys to ship your blog.