Everything needed to model, build and scale content in the Framer CMS, from a first collection to programmatic page generation.
8 min read
Category and author pages should help visitors browse a meaningful set of content, not create hundreds of empty URLs. Use a stable taxonomy, useful introductions and clear links back to the individual items.
A dynamic CMS page needs a readable slug, a unique title and description, and a consistent canonical URL. Treat those values as content fields with editorial rules rather than styling details.
CSV imports save time when the column model is settled and the source data is clean. Test a small batch first, preserve stable identifiers and keep a rollback copy before bulk updates.
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.
Framer CMS fields should match what editors actually manage. Pick the simplest field type that works and keep layout out of editorial fields.
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.
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.
Reference fields connect one CMS record to another, while multi-reference fields connect one record to many. They are useful for authors, categories, services, related projects and reusable taxonomies.
Framer CMS lists become useful when visitors can narrow content by a meaningful property and scan results in a predictable order. Keep filters explicit and make empty states clear.
Send a couple of lines about your site and we'll reply within one working day.