⚡️ Flexible Sections & Components inside CMS Pages
R
Robert W. Schönholz
When using Framer CMS for blog pages, all entries share the same rigid structure. While this is great for consistency (header, author, date, etc.), it limits flexibility for individual posts.
It would be very helpful to have a free, customizable section inside CMS pages where designers can place regular Framer components (layouts, images, videos, grids, custom elements), while the surrounding blog structure stays consistent.
The current Formatted Text (Rich Text) field is too limited for this use case. Layout control is very basic (no proper alignment, sizing, positioning, or advanced compositions), which makes all blog pages look very similar.
Possible solutions could be:
• Allow inserting Framer components inside the Formatted Text field, or
• Add a dedicated “Custom Section” area to CMS pages that supports full component-based design.
This would greatly improve design flexibility and enable more unique, high-quality blog layouts while still benefiting from CMS-driven content.
Log In
Autopilot
Merged in a post:
Some way to do news/articles
M
Migue Lorente
Right now I'm achieving this by putting components in a rich text of the CMS but in some cases they don't fit well and if I need to make variants for small breakpoints like Phone, it means having two CMS with one rich text each. There should be a native way to be able to create articles or news pages more easily
Autopilot
Merged in a post:
Free-Form Sections for CMS Collection Pages
D
Damian Claassens
Framer's CMS is great for structured content. When everything follows the same template, it just works. But most real projects need a little wiggle room—and right now, that wiggle room is kind of a pain to build.
The problem:
Say you're building a portfolio. Most of your case studies follow the same layout, but one project needs a custom video player. Another needs an interactive prototype embed. A third just needs the standard template.
Your options right now:
- Add fields to the entire collection that 90% of items won't use
- Write conditional code to show/hide components based on whether fields are populated
Both work. But as exceptions pile up, your CMS gets cluttered with "optional_thing_1" and "optional_thing_2" fields, and your template code starts to look like a nested mess of if statements.
What I'm proposing:
Let us define free-form zones within CMS templates—areas where editors can optionally drop in components on a per-page basis. And let editors add multiple blocks within those zones, not just one.
How it could work:
- Template designers control where these zones can appear
- They're opt-in, not required
- Editors can add as many components as needed within a zone—stack a video, then a pullquote, then an image gallery, whatever the page calls for
- The overall page structure stays intact
Think of it like... I don't know, designated flex space within a fixed layout. The template still defines the page, but you get a release valve for the stuff that doesn't fit the mold.
Example:
Portfolio collection. Standard template handles hero image, description, image gallery. But on one project page, I want to add a before/after slider, followed by a client testimonial block, followed by a custom animation. On another page, just a single prototype embed. On most pages, nothing extra at all.
Instead of adding fields for every possible combination, I'd just have a free-form zone in the template. On pages that need it, I could drop in two blocks, five blocks, whatever. Pages that don't need it, ignore it.
I know what you're thinking:
"This breaks consistency."
• Fair. But designers would control whether to enable it and where it appears. It's not forced on anyone.
"Sounds complicated."
• Maybe. But the workaround we're doing now—conditional rendering via custom code—is already complicated. This would just make it more manageable.
"Collections are supposed to enforce structure."
• Totally agree. And they still would. The template defines the structure. This just acknowledges that edge cases exist, and right now handling them is clunky.
Why it matters:
Most projects don't fit perfect templates. Framer handles the common cases beautifully, but when you hit an exception, you're either hacking something together or redesigning your whole CMS structure. Free-form sections would give us a cleaner way to handle the 20% that doesn't fit the 80%.