Am I not using Webflow CMS properly if I need more than 30 fields for each case study section? Can I add a non-collection section to a collection page in Webflow? Is there a better way to build case studies using Webflow that allows for more flexibility? Thank you.

If you're hitting the 30-field limit in Webflow CMS for your case study Collection, you may be pushing the CMS system beyond what it's designed for in a single Collection. Below is how to better manage this situation and explore flexible alternatives.

1. Understand Field Limits and Your Use Case

• Webflow CMS limits custom fields (excluding default fields) to 30 per Collection.
• If your case studies require more than 30 distinct pieces of content (e.g., multiple headlines, feature sections, quotes), you're likely using a single Collection to store too many types of data.
• This often indicates that your content model may need to be modularized for better scalability.

2. Use Multi-Reference or Reference Fields to Break Up Data

• Create separate Collections for repeating structured content like testimonials, team members, image galleries, etc.
• In your primary Case Study Collection, use Reference or Multi-Reference fields to connect to these reusable or repeatable items.
• Example: Instead of having fields like Feature Title 1, Feature Title 2, etc., create a Features Collection and link it with a Multi-Reference field.

3. Add Non-CMS Sections to a CMS Template Page

• Yes, you can absolutely add static (non-CMS) sections to a CMS Template page.
• Just scroll below or above your CMS-linked content in the Designer and add regular layout elements or Sections.
• This is useful for adding standardized content that doesn’t change between items, like footers, calls to action, or introductory sections.

4. Use a Modular Design with Symbols and Conditional Visibility

• You can use Webflow Symbols or custom component structures with conditional visibility to display optional CMS sections only when relevant.
• This minimizes the number of fields required and makes the CMS entry more manageable.

5. Consider Using Rich Text with Nested Styles or Custom Code

• If multiple fields are being used to display simple content blocks, you can often consolidate them into a Rich Text field.
• Rich Text supports headers, paragraphs, images, videos, and more—all inside a single field. It also allows custom HTML embeds if needed.
• Styling nested elements (like blockquotes or custom headings) can be handled via targeted CSS using custom classes within the CMS.

6. Optional: Use Webflow and an External CMS Together

• If your content needs exceed Webflow CMS limits significantly, you could explore integrations with external CMSs like Airtable or Contentful via tools like Zapier, Make (Integromat), or custom APIs.
• However, this adds complexity and is recommended only for larger-scale or dynamic websites.

Summary

If you're exceeding 30 CMS fields, you should refactor your case study structure using Reference fields, separate Collections, and more strategic use of Rich Text and static layout sections. This modular approach gives you more flexibility and keeps your CMS manageable for long-term scalability.