Back to Framer CMS

Add fields with purpose.

Framer CMS fields should match what editors actually manage. Pick the simplest field type that works and keep layout out of editorial fields.

Framer CMS · 8 min read · Updated 2026-06-06

Field design rules

Start with the question the field answers. A field called Category answers which group an item belongs to; a field called Gold Text does not describe content and will become difficult to maintain.

  • Use plain text for titles, labels and short values.
  • Use rich text for structured editorial copy that needs headings or links.
  • Use images for content assets rather than pasted URLs where possible.
  • Use dates for publishing and event dates so sorting stays reliable.
  • Use references for relationships instead of repeating the same author or category text.

Connect fields to the interface

Follow the sequence below from start to finish. The order matters: later steps assume the earlier ones are done.

  1. Select the text, image or link layer in the CMS-connected component.
  2. Choose the matching collection field from the content connection menu.
  3. Preview several records, including the longest title and an empty optional field.
  4. Add a deliberate fallback or conditional treatment for optional content.
If editors need to change it without opening the canvas, it probably belongs in the CMS. If it changes spacing or appearance, it belongs in the component.

Field naming checklist

A few moving parts are involved here. The points below cover each of them, so you can see the full scope before deciding where to start.

  • Use singular, plain-language names.
  • Keep one meaning per field.
  • Document units for numbers, prices and durations.
  • Avoid duplicate fields with slightly different names.

Handover notes for editors

When a collection goes live, give editors a short field guide: what each field is for, whether it is required, and any character limits imposed by the layout. This prevents an editor filling a summary field with three paragraphs and breaking a card layout months after launch.

Common field mistakes

This comes down to a handful of concrete details. Work through the list below and flag the ones you have not covered yet.

  • Storing a colour or icon choice in a text field instead of a controlled option.
  • Using a rich text field for a single short label, which allows accidental formatting.
  • Adding a boolean called Type1 instead of a readable option like Featured.
  • Leaving a field required when it is genuinely optional for some records.

Questions

Plain text stores a single unformatted string suited to titles and labels. Rich text stores formatted content with headings, links and lists, and should be reserved for genuine editorial copy rather than short labels.

No. Marking a field required when some records legitimately have no value forces editors to enter placeholder content, which then leaks into the live page.

Set realistic character guidance in the handover notes, and design the component to wrap or truncate gracefully rather than relying on editors to always type a short value.

Outgrowing Framer?

We rebuild Framer sites as fast, custom-coded ones and protect your rankings through the move.

See the service

Related guides

Framer CMS field types explained

The useful Framer CMS field types are the ones that match how content is authored and queried. Text, rich text, images, dates, links, booleans and references each solve a different problem.

Dynamic CMS pages in Framer

A dynamic CMS page is a single Framer template rendered with different collection records. It gives every article, project or listing a consistent URL and layout without manually building each page.

How to create a Framer CMS collection

A Framer CMS collection is a structured content table for repeatable items such as blog posts, projects or team members. Create the model before designing the template so every page has the fields it needs.