New case study: a Framer studio site where one CMS collection drives thirteen project pages through a single template — the collection, fields, pages and text styles were all generated through the Framer Plugin API from a JSON source of truth, so the build is repeatable. Live link inside.

One CMS collection driving thirteen project pages is the kind of Framer restraint that actually scales. Generating fields and text styles from a JSON source of truth makes the template feel like a system, not a stack of one-off pages.

My own site, built to be edited in one place. Every section reads from a single data folder, so adding a project or a skill means editing one file, not the UI.

It ships with the SEO work done: sitemap, robots, schema.org structured data, social preview images generated at build time, and a plain-text summary for AI assistants. Verified in Google Search Console and Bing.

Stack: Next.js, TypeScript, Tailwind CSS, Framer Motion, deployed on Render.

Live: https://nahid-yf63.onrender.com

The single data folder makes the site easy to update without opening the components. I'd add a build check that stops the deploy when a project is missing its title or social image.