Who this is for
You built the site in Webflow, the blog collection has four items in it, and two of them are placeholders. Writing into a CMS collection is more friction than writing into a text editor: there are fields to fill, images to upload, a slug and a meta description to remember, and no reason to do any of it until there is an article worth publishing.
PrismDraft removes the part before that. Your Webflow site address becomes a project with your brand voice and the image style your pages already use. Topics arrive with a primary keyword and a search intent each. The outline is proposed and approved before prose, for free. The article is written section by section with an image per section and alt text, and the meta title, meta description and slug are written from the finished text and editable.
What reaches Webflow is a complete collection item: the body as rich text, the images hosted and referenced, the slug, and the SEO fields. It is created when you approve the article, not before.
- Publishes into a Webflow CMS collection through the Webflow API with a site token.
- Writes the fields `name`, `slug`, `post-body`, `post-summary` and `main-image`, so a collection with those slugs needs no setup.
- The body is HTML for the rich-text field; the cover and the section images are hosted by PrismDraft and referenced.
From your Webflow site to a CMS item
- 01
Give it your site address
PrismDraft reads your pages and drafts the project, the audience, the brand voice and the image style — including the look your existing imagery has.
- 02
Pick a topic worth the design
Suggestions carry a working title, a primary keyword, a search intent and a cluster. A keyword the project already covers is not proposed twice.
- 03
Approve the outline
A heading per section with its job, keywords and target length, free to generate and free to change. Long Webflow pages live or die on structure, and this is where it is decided.
- 04
Run the article
Each section written against its own heading, one image per section prompted from the paragraphs beside it, alt text in the article's language. About 7 credits for 1,200 words and three images, quoted first.
- 05
Approve, then create the item
Review, edit, approve. The collection item is created with the body, the images, the slug and the SEO fields; publish it from Webflow or let the connection publish it live.
Ten topics for a Webflow studio's own blog
From one site address. Each suggestion carries the keyword it targets and the intent behind it.
The outline for the migration piece
A migration article is the kind a studio gets found by, and the kind that is easy to write badly. The outline is where the promise gets limited to what you can actually deliver.
- H2What actually causes a drop after a migrationName the three real causes before any reassurance.
- H2The redirect mapThe single most important artefact, described concretely.
- H3What to do with pages you do not wantA decision, not a redirect-everything reflex.
- H2Matching the content model to the old URLsWhere Webflow's collections help and where they fight you.
- H2A launch-week checklistShort, ordered, and genuinely the one you use.
- H2What we would do for your siteClose with the service, having earned it.
An outline costs no credits, which is why it is the step to argue with. The draft is written against the headings you approved, section by section.
What arrives in the collection
The item is created with five fields: `name` from the title, `slug` from the slug you edited, `post-body` from the article rendered as HTML for a rich-text field, `post-summary` from the meta description, and `main-image` from the cover. A blog collection generated by Webflow's own template already has those field slugs; a collection you designed yourself may need them renamed to match.
Each section image is referenced from inside the body HTML with the alt text you approved, and is served from PrismDraft's storage rather than uploaded into Webflow's asset manager. Because the connection creates a collection item and never touches the design, nothing about your templates changes.
The connection either publishes the item live or leaves it as a draft in the CMS, which is the setting to use if you would rather give it a last look in the Designer. A publishing plan can give each article a date instead.
Questions
Which Webflow collection do the articles go into?
The one whose id you give when you create the connection. PrismDraft creates items in it and never creates or alters its fields, so the collection must already have `name`, `slug`, `post-body`, `post-summary` and `main-image`.
Does the body arrive as rich text?
The article is rendered as HTML and written to the `post-body` field, so headings, lists, quotes and images keep their structure in a rich-text field rather than arriving as one block of text.
Where are the images hosted?
Images are generated, resized, stripped of metadata and compressed by PrismDraft, and served from its storage; the published item references them. They are not uploaded into Webflow's asset manager. Alt text is written in the article's language and is editable before you approve.
Can I schedule posts?
Yes. A publishing plan gives each article a date, and a plan with Autopilot switched on writes, approves and publishes its entries on their day up to the plan's credit cap. Without Autopilot, you approve each one.
What does it cost per article?
About 7 credits for 1,200 words with three images, shown before the run starts. Plans include 150 credits for €29 a month, 450 for €79 and 1,400 for €199; failed runs cost nothing.
Can I use the API instead?
Yes. There is a documented REST API with workspace-scoped keys, a typed SDK and signed outbound webhooks, so you can trigger runs and react to publishing events from your own pipeline.