To display multiple CMS items with different content inside a single Rich Text element, Webflow doesn’t support dynamic injection of multiple CMS entries into one Rich Text field directly—but here’s how to organize and display them effectively:
1. Understand Rich Text CMS Limitations
- A Rich Text element can only be bound to one Rich Text field from a single CMS item.
- You cannot pull content from multiple CMS items into the same Rich Text field directly within Webflow.
2. Use a Collection List Instead
- Place a Collection List on the page and connect it to your CMS Collection.
- Within the Collection List, add a Rich Text element.
- Bind the Rich Text element to the appropriate Rich Text field for that CMS item.
- Each Rich Text block will now show the content for one CMS item, and they’ll render consecutively.
3. Sort and Filter Collection Items
- Use the Sort Order and Filters under the Collection List settings to control:
- Which CMS items appear (e.g., only featured posts, specific categories).
- The order in which they show (e.g., by date, alphabetical).
4. Combine Content Using Reference or Multi-Reference Fields (Optional)
- If you want one CMS item to “collect” content from several others:
- Create Reference or Multi-Reference fields in your main CMS collection.
- Reference other CMS items and display their content through a nested Collection List.
- Still, each content block will render separately—you can only merge them visually with consistent styles, not as continuous Rich Text.
5. Use Custom Code (Optional Advanced Approach)
- To merge actual rich text fields from multiple CMS items into one output:
- You’d need to use JavaScript to pull in multiple CMS item contents and inject them into a single Rich Text container.
- This method requires manual setup and is not officially supported by Webflow Designer alone.
Summary
Webflow doesn’t support combining multiple CMS items into one Rich Text element directly. Instead, use a Collection List to display multiple CMS items—each with its own Rich Text content—and control layout with filters, sorting, and styling. For full content merging, a custom-code workaround is necessary.