How to Build a Webflow CMS Collection for a Food Editorial Brand

The food editorial industry in Singapore is built on content that's rich, seasonal, and constantly changing. A recipe library for a subscription cooking club needs to be discoverable, navigable, and manageable by a small team without any technical overhead.

This is a walkthrough of the CMS architecture we built for a food editorial client — the exact collection structure, field decisions, and the CMS filters that make it work at scale.

Key Takeaways

• A food editorial CMS needs at minimum four collections: Recipes, Chefs/Authors, Cuisines/Categories, and Ingredients
• Multi-reference fields between collections enable powerful filtering without duplicating content
• Rich Text fields handle long-form content; structured fields (Option, Reference) handle filterable metadata
• Getting the schema right before building the Designer saves significant rework time
• This architecture scales from 50 recipes to 5,000 without structural changes

The Collections

A food editorial site needs a minimum of four CMS collections working together. Recipes is the primary collection — every recipe is an item here. Chefs is a reference collection for recipe authors. Cuisines handles the primary category taxonomy. Ingredients is an optional but powerful collection if you want ingredient-level filtering or search.

Additional collections depend on the editorial scope: a Techniques collection for how-to content, a Producers collection for supplier spotlights, a Video Episodes collection if video is part of the editorial mix.

The Recipe Collection Schema

This is the core collection. Here's the field structure we use:

Name (plain text, required). Slug (auto-generated from name). Hero Image (image). Body (rich text — the full recipe content, introduction, steps). Excerpt (plain text — 2–3 sentences for recipe cards and meta). Chef (reference to Chefs collection). Cuisine (reference to Cuisines collection). Secondary Cuisines (multi-reference to Cuisines — for recipes that span multiple traditions). Ingredients List (rich text — formatted ingredient list). Difficulty Level (option: Easy, Medium, Advanced). Prep Time in Minutes (number). Cook Time in Minutes (number). Servings (number). Published Date (datetime). Members Only (switch — for gated premium content). SEO Meta Title (plain text). SEO Meta Description (plain text). Featured Recipe (switch).

The Cuisines Collection

Simple but important. Name, Slug, Description (plain text), Cover Image (image), Display Order (number — controls sort order in navigation). The Display Order field is often overlooked but essential for editorial control of how cuisines appear in menus and filters.

The Chefs Collection

Name, Slug, Photo (image), Bio (rich text), Nationality (plain text), Signature Style (plain text), LinkedIn or Instagram URL (link). Connecting each recipe to a chef record via a Reference field means updating a chef's bio once updates it everywhere their recipes appear.

Building the Filter System

Webflow's native CMS filtering handles the most common use cases: filter by Cuisine, filter by Difficulty Level, filter by Chef. These are set up on the collection list component using Webflow's built-in filter conditions — no custom code required.

For more advanced filtering (multiple simultaneous filters, ingredient-based search), Finsweet's CMS Filter attribute library is the standard solution. It's free, well-documented, and handles complex filter logic without custom JavaScript.

CMS Permissions for the Editorial Team

For a food editorial client with a small team — an editor, a recipe tester, and a photographer — we set up Webflow's Editor role so each team member can add and edit CMS items without touching the Designer. The recipe submission and review workflow happens entirely in the Webflow CMS Editor interface, which is clean and accessible to non-technical users.

Building an editorial CMS or scaling an existing one? We've designed content architectures for food, travel, and lifestyle brands across Southeast Asia.