Draft a Webflow CMS schema from a Figma design
Share a Figma screenshot or Dev Mode link and get a clean Webflow Collection schema back, including multi-reference fields, before you build anything.
Here are screenshots / a Figma Dev Mode link for the design.
Draft the best Webflow CMS structure to build this:
- Which Collections I need (e.g. Blog Posts, Authors, Categories).
- The fields inside each Collection, with the right field type for each (plain text, rich text, image, date, switch, reference, multi-reference).
- How the Collections link to each other, and where a multi-reference is the right call versus a single reference.
Explain each choice in one line so I understand the trade-offs, and warn me about anything that would be hard to change later once content is in.
<FIGMA LINK OR SCREENSHOTS>Walkthrough
The most expensive Webflow mistakes are CMS mistakes. Once you have built a Collection and added items, restructuring it is painful, so it pays to get the shape right before you create a single field.
A Collection is a content type (Blog Posts, Team Members, Case Studies). A field is a piece of information on each item (a title, an image, a date). A reference links oneitem to another, for example linking a blog post to its author, and a multi-reference links to several at once, for example tagging a post with three categories.
Share the design as Figma screenshots or a Dev Mode link and Claude reads the layout, works out what content is repeating, and proposes the Collections, fields, and the relationships between them. It handles the tricky part well: deciding when something should be its own Collection rather than a field, and when a multi-reference is the right tool. You get a plan you can build against once, correctly, instead of discovering the gaps halfway through.