CMS & Content
Adding Fields
Fields are the building blocks of every CMS collection in Framer.
Beginner
6 min read
They define what information can be stored for each content item and ensure that every entry follows a consistent structure.
Whether you’re creating a blog, portfolio, case study library, or team directory, fields determine what content editors can add and how that content will be displayed across your website.
This guide explains how fields work, the different field types available, and how to design a field structure that remains organized as your website grows.
What Is a Field?
A field is a container for a specific type of content.
Think of fields as individual pieces of information that belong to a CMS item.
For example, a blog post may contain:
Each piece of information is stored in its own field.
Every entry inside the collection uses the same field structure.
Why Fields Matter
Fields create consistency.
Without fields, every content entry could contain completely different information, making it difficult to build reusable layouts.
Fields help:
Standardize content
Simplify editing
Support dynamic pages
Improve organization
Enable automation
Scale content efficiently
The better your field structure, the easier your CMS becomes to manage.
Understanding Field Structure
A CMS collection is typically organized like this:
Fields define the structure.
Entries contain the actual content.
Common Field Types
Different types of content require different field types.
Choosing the right field helps maintain consistency and improves editing workflows.
Text Fields
Text fields are used for short pieces of content.
Common examples:
Titles
Names
Categories
Labels
Subheadings
Example:
Text fields are among the most frequently used field types.
When to Use Text Fields
Use text fields when content is:
Short
Simple
Single-line
Easy to edit
Examples include:
Article titles
Team member names
Product names
Client names
Rich Text Fields
Rich text fields support long-form content and formatting.
Examples include:
Blog posts
Case studies
Documentation
Tutorials
Help center articles
Rich text fields allow content creators to add:
Headings
Paragraphs
Lists
Links
Formatting
This makes them ideal for content-heavy websites.
When to Use Rich Text
Use rich text when content includes:
Multiple paragraphs
Structured content
Headings
Lists
Detailed explanations
For example:
should almost always be a rich text field.
Image Fields
Image fields store visual assets.
Examples include:
Featured images
Team photos
Project thumbnails
Product images
Cover images
Image fields allow content editors to update visuals without modifying layouts.
Common Image Field Examples
These fields are common across most CMS-driven websites.
Date Fields
Date fields store date-related information.
Examples:
Publish dates
Event dates
Launch dates
Updated dates
Date fields help organize content chronologically.
Common Date Use Cases
Blog collections often contain:
Event collections may include:
Date fields are especially useful when sorting content.
Link Fields
Link fields store URLs.
Examples include:
Website links
Social profiles
Resource downloads
External references
These fields help create dynamic linking systems.
Common Link Examples
These values can be connected directly to buttons and links within layouts.
Boolean Fields
Boolean fields contain only two possible values:
or
They are useful for simple conditions and content management workflows.
Common Boolean Examples
Examples include:
Boolean fields are commonly used for filtering and highlighting content.
Building a Collection With Fields
A typical CMS collection combines multiple field types.
Example:
This structure supports both content management and page generation.
How to Add Fields
Step 1: Open Your Collection
Navigate to the CMS panel and select the collection you want to edit.
Example:
Step 2: Add a New Field
Select:
Framer will present available field types.
Step 3: Choose a Field Type
Select the type that best matches your content.
Examples:
Text
Rich Text
Image
Date
Link
Boolean
Choosing the correct type improves content consistency.
Step 4: Name the Field
Give the field a clear and descriptive name.
Examples:
Article Title
Featured Image
SEO Description
Author Name
Publish Date
Field names should immediately communicate their purpose.
Field Naming Best Practices
Good naming becomes increasingly important as projects grow.
Use Descriptive Names
Good examples:
These names are easy to understand.
Avoid Generic Labels
Poor examples:
These become confusing later, especially on larger projects.
Maintain Consistency
Choose a naming style and stick to it.
Example:
Consistent naming improves maintainability.
Required vs Optional Fields
Not every field needs to be completed for every entry.
Required Fields
Required fields must contain content before publishing.
Examples:
Title
Slug
Content
These fields are essential for the content to function correctly.
Optional Fields
Optional fields can remain empty when not needed.
Examples:
Secondary Image
External Link
Author Bio
Optional fields provide flexibility without forcing unnecessary content.
Planning Your Field Structure
One of the most important CMS skills is planning before building.
Ask yourself:
What information will every entry need?
What information is optional?
Which fields support SEO?
How will content be displayed?
A well-planned structure reduces future maintenance.
Example: Blog Collection
A typical blog setup may include:
This covers both content management and optimization.
Example: Portfolio Collection
Portfolio websites often use:
Every field supports a specific purpose.
SEO-Related Fields
Many websites benefit from dedicated SEO fields.
Common examples include:
These fields help optimize dynamic pages for search engines and social sharing.
Why SEO Fields Matter
SEO fields allow content editors to optimize pages without modifying layouts.
This becomes especially valuable for:
Blogs
Resource centers
Documentation websites
Large content libraries
Common Beginner Mistakes
Creating Too Many Fields
More fields do not automatically create a better CMS.
Unnecessary fields often:
Slow content creation
Confuse editors
Increase maintenance
Keep structures focused.
Poor Naming Conventions
Names like:
become difficult to understand later.
Always use descriptive labels.
Using the Wrong Field Type
For example:
Using a text field for long-form articles instead of a rich text field can create limitations.
Choose field types based on content requirements.
Ignoring SEO Fields
Many beginners build collections without considering:
Titles
Descriptions
Slugs
Adding these later is possible but planning ahead is easier.
Inconsistent Formatting
Content editors should follow consistent formatting standards.
Inconsistent capitalization, naming, and structure can reduce professionalism.
Best Practices
Plan field structures before creating collections
Use descriptive field names
Choose the correct field type
Keep required fields minimal
Create dedicated SEO fields
Avoid unnecessary complexity
Maintain consistent naming conventions
Design for future growth
Frequently Asked Questions
How many fields should a collection have?
Only include fields that serve a clear purpose. Simpler collections are generally easier to manage and maintain.
Can fields be optional?
Yes. Not every field needs to be required.
What is the difference between Text and Rich Text?
Text is designed for short content, while Rich Text supports formatting and long-form content.
Should every collection have SEO fields?
For content-driven websites, SEO fields are highly recommended.
Can I add fields later?
Yes, although planning fields before adding large amounts of content is recommended.
framerbaseio