CMS & Content
Creating a CMS Collection
CMS collections are the foundation of dynamic content in Framer.
Beginner
6 min read
Every CMS-powered website starts with one or more collections that store and organize structured content.
Whether you’re building a blog, portfolio, resource center, team directory, or case study library, collections allow you to manage content efficiently without creating every page manually.
This guide explains how CMS collections work, how to create them, and how to structure them for long-term scalability.
What Is a CMS Collection?
A CMS collection is a container that stores related content.
Think of a collection as a database table where every item follows the same structure.
For example, a blog collection might contain:
Each article contains the same set of fields, such as:
Title
Featured Image
Publish Date
Author
Content
The collection stores the data, while the design determines how the data is displayed.
Why Collections Matter
Collections are what make dynamic websites possible.
Without collections, you would need to:
Create every page manually
Update content individually
Duplicate layouts repeatedly
With collections, you can:
Add content quickly
Generate pages automatically
Maintain consistency
Scale websites efficiently
The larger a website becomes, the more valuable collections become.
When Should You Use a Collection?
Collections are ideal whenever content follows a repeatable structure.
Common examples include:
Blog posts
Portfolio projects
Team members
Testimonials
Resources
Case studies
Directories
Job listings
Product showcases
Documentation articles
If content can be described using the same fields repeatedly, it usually belongs in a collection.
Understanding Collection Structure
Every collection contains two main parts:
Fields define the structure.
Entries contain the actual content.
What Are Fields?
Fields are the individual content properties inside a collection.
For example:
Every blog post uses the same fields.
This consistency is what allows Framer to generate pages automatically.
What Are Entries?
Entries are the individual content items stored inside a collection.
Example:
Each entry contains content for all defined fields.
How to Create a CMS Collection
Creating a collection is one of the first steps when building a CMS-powered website.
Step 1: Open the CMS Panel
Inside the Framer editor, open the CMS panel.
This is where all collections, fields, and content entries are managed.
Step 2: Create a New Collection
Select:
Framer will create an empty collection ready for configuration.
Step 3: Name the Collection
Choose a clear, descriptive name.
Good examples:
Blog Posts
Projects
Team Members
Resources
Testimonials
Case Studies
Avoid vague names such as:
Data
Content
Collection 1
Collection names should immediately communicate their purpose.
Step 4: Add Fields
Next, define the structure of your content.
Examples:
Title
Description
Image
Rich Text Content
Category
Author
Publish Date
Think carefully about what information every entry should contain.
Step 5: Add Content Entries
Once fields exist, begin creating content.
You can:
Add entries manually
Copy content from existing sources
Import content when appropriate
Each entry will follow the structure defined by the collection.
Planning Your Collection Before Building
One of the most common beginner mistakes is creating collections without planning.
Before adding content, determine:
What content type you’re managing
Which fields are required
Which fields are optional
How pages will be displayed
Whether content needs categories or tags
Planning first prevents major restructuring later.
Example: Blog Collection
A blog collection might include:
This structure supports both content management and SEO.
Example: Portfolio Collection
A portfolio collection might contain:
Every project follows the same format.
Example: Team Collection
For team directories:
This structure makes it easy to add or remove team members.
Understanding Slugs
A slug is the URL-friendly version of an entry.
Example:
Article title:
Slug:
Generated URL:
Slugs are important for both SEO and usability.
Why Slugs Matter
Good slugs are:
Short
Readable
Descriptive
Keyword-focused
Visitors and search engines should immediately understand what a page is about.
Good Slug Examples
These are clean and easy to understand.
Poor Slug Examples
These provide little context and are less useful for SEO.
Organizing Collections Properly
As websites grow, collection organization becomes increasingly important.
Separate Different Content Types
Create separate collections for fundamentally different content.
Example:
Each content type should have its own structure.
Avoid Duplicate Collections
A common mistake is creating multiple collections that serve the same purpose.
Poor example:
Better:
with categories inside the collection.
Use Consistent Naming
Collection names should follow a consistent pattern.
Examples:
Consistency improves maintainability.
Categories vs Collections
Many beginners create separate collections when categories would work better.
Instead of:
Create:
and add a Category field.
This simplifies management significantly.
Thinking About Scale
When planning collections, consider future growth.
Ask yourself:
Will this collection contain 10 items or 1,000?
Will more content types be added later?
Will multiple people manage content?
Will SEO become important?
A scalable structure saves time later.
Common Beginner Mistakes
Creating Too Many Collections
More collections do not always mean better organization.
Keep structures as simple as possible.
Adding Unnecessary Fields
Every field should have a purpose.
Unused fields create clutter and confusion.
Poor Naming Conventions
Names like:
become difficult to understand later.
Always use descriptive names.
Ignoring SEO Fields
Many users forget to include:
Slugs
Meta descriptions
SEO titles
These should be considered early in the process.
Changing Structure After Adding Content
Major changes become more difficult once dozens of entries exist.
Plan first, then build.
Best Practices
Plan content structures before creating collections
Use descriptive collection names
Keep fields simple and purposeful
Create SEO-friendly slugs
Use categories instead of unnecessary collections
Build for future growth
Maintain consistent naming conventions
Review structure before adding large amounts of content
Frequently Asked Questions
Are slugs required?
For dynamic pages, slugs are highly recommended because they create readable URLs and improve SEO.
Can I add fields later?
Yes, although planning fields before adding large amounts of content is recommended.
Should every content type have its own collection?
Usually, yes. Different content structures typically belong in separate collections.
How many collections should a website have?
Only as many as needed. Most websites work best with a small number of clearly defined collections.
Can CMS generate pages automatically?
Yes. Dynamic pages can be created automatically from collection entries.
framerbaseio