Turn customer stories into pages without rebuilding each one.
Overview
Case studies convert, and most brands sit on a backlog of them because every story costs a page build, and by the sixth copy-paste the pages have drifted into six designs. This workflow sets the section up as a collection instead: define what a case study contains once, design the template once, and every story after that is an entry, not a build. Come with two or three real stories so the template gets designed against actual content.
Before you start
- The raw case-study material: docs, links, or old pages to migrate
The prompt
Paste this into the agent. The bold values are yours to change:
Create a content collection called [Case Studies] with fields: [title, customer, industry, pull quote, results, body]. Mark [title and body] required.
Design two templates in my brand: a listing page at [/case-studies] with filters by [industry], and a detail page per entry.
Migrate my existing [six case studies] into the collection as entries: [links or files].
From now on, when I add or edit an entry, only that content changes; the templates stay fixed. Publish the listing page and the first two entries, keep the rest as drafts.
The same recipe works for any page family: press mentions, locations, FAQs, guides. Swap the fields and the routes.
What the agent does
- Creates the collection with your field shape, so every case study has the same bones: required fields enforced, optional ones visible only when filled.
- Designs the listing and detail templates once, in your brand.
- Migrates your existing case studies in as entries. The last copy-paste those pages will ever need.
- Publishes the listing plus the entries you approve; drafts stay invisible.
- From then on, a new customer story is a new entry, written by you or by another workflow.
Try it on your store
The prompt opens in the agent ready to edit, with your store and tools connected.