Keeping product education in step with frontier AI models
Recraft builds its own image models and ships fast. Its pages, docs, and launches had to keep up, for users who were often new to generative AI.
At a glance
- Client
- Recraft, generative AI design platform
- Work
- Product documentation, landing pages, launch content, blog, and newsletter
- Engagement
- May 2025 to February 2026
- System
- Wordful (early version)
Before
- Every release meant rewriting landing pages, model pages, and documentation
- The product story lived mostly with the founder, and the rest was spread across teams
- There was no documentation, and many users had never used generative AI
The turning point
Write the documentation first. Every part of the product was walked through and the people who built it were interviewed, and the docs became the source of truth. Landing pages, model pages, launch posts, and the newsletter were all built from them, so the marketing described the product the way the product described itself.
What we built
- Recraft's product documentation and prompting guide, written from scratch
- A landing page system for each audience, from individual creators to design teams and enterprise
- Launch content aligned across docs, blog, newsletter, and landing pages
After
- One source of truth for every page, post, and support answer
- Landing, model, and launch pages built from reusable structures instead of from scratch
- Messaging that stayed consistent as new models shipped
Read the work
- Recraft Studio documentation
- Prompting guide
- Recraft for enterprise
- AI models supported
- How to create remarkable vector art
Read the full story
The problem
Each release meant Recraft's landing pages, model pages, and documentation needed rewriting. The product story was scattered: much of it lived with the founder, and the rest was spread across product, design, engineering, marketing, support, and leadership. There was no documentation, so concepts like prompting, style controls, and image editing needed explaining from the beginning. And individual creators and professional design teams evaluate Recraft for different reasons, so each audience needed its own pages.
Documentation first
Every part of the product was walked through, and subject-matter experts were interviewed, to write the Recraft Studio documentation and a prompting guide. The docs explain features and workflows in language a first-time user can act on, and they became the source the rest of the content drew from.
One record of what Recraft could say
Approved claims, messaging guidelines, and compliance language sat in one record alongside the docs. Customer interviews fed the audience definitions and messaging. When the product changed, the docs and the record changed first, and every page drew from them.
Landing pages as a system
Page structures, headings, FAQs, and content patterns were designed once for search, AI answers, and readability, then reused. Each new landing page, model page, or launch page started from that structure.
AI in the workflow, editors on the judgment
AI handled source gathering, outlines, draft variations, and revision passes inside a structured process. Editors set the message, structure, and accuracy, and decided what was ready to publish.
What Recraft keeps
- Product documentation that new pages, posts, and support answers can build on
- One record of approved claims, messaging guidelines, and compliance language
- Reusable structures for landing, model, and launch pages
If this sounds like you
Your product changes faster than your content? Tell us what you need. No prep needed.
Prefer to talk? Book a free scoping call.