FAQ Template
A repeatable structure for FAQ question, answer, category, related service, and SEO context.
Back to Templates
Custom Content Types
Case Study Template
A starter Custom Content Type structure for client stories, project outcomes, and portfolio proof.
1
When to use this template
Use this template when you publish repeatable client stories or project outcomes as a Custom Content Type — case studies, portfolio entries, or proof pieces that share the same fields across many items.
It keeps each story consistent: the same challenge → solution → result structure, the same SEO fields, and the same media references, so your team can produce them quickly and reviewers always know what to check.
2
Suggested fields
A starting set of fields for this structure. Adapt the labels, keys, and which fields are required to match your project.
Field labelField keyTypeStatus
Client NameclientNametextRequired
Project SummaryprojectSummarytextareaRequired
ChallengechallengeMDXRequired
SolutionsolutionMDXRequired
Result SummaryresultSummarytextRequired
Featured ImagefeaturedImagemediaOptional
Services / TagstagslistOptional
Publish DatepublishDatedateOptional
SEO TitleseoTitletextSEO
Meta DescriptionmetaDescriptiontextareaSEO
3
Required fields
The minimum fields every item should have before it can move to review.
Field labelField keyTypeStatus
Client NameclientNametextRequired
Project SummaryprojectSummarytextareaRequired
ChallengechallengeMDXRequired
SolutionsolutionMDXRequired
Result SummaryresultSummarytextRequired
4
Optional fields
Useful additions you can include per item, or leave out when they don't apply.
Field labelField keyTypeStatus
Featured ImagefeaturedImagemediaOptional
Services / TagstagslistOptional
Publish DatepublishDatedateOptional
5
SEO fields
Search metadata for the item. Keep titles and descriptions unique per item.
Field labelField keyTypeStatus
SEO TitleseoTitletextSEO
Meta DescriptionmetaDescriptiontextareaSEO
6
Example content item
clientNameAcme Dental
resultSummary42% organic growth in 6 months
challengeLow local visibility for high-intent service searches.
featuredImage/images/case-studies/seo-campaign.webp
tagsSEO, Local, Healthcare
7
Markdown / MDX frontmatter example
How the structure looks as frontmatter in a Git-backed content file. Field keys map directly to your content type.
---
title: "SEO Campaign Case Study"
clientName: "Acme Dental"
resultSummary: "42% organic growth"
featuredImage: "/images/case-studies/seo-campaign.webp"
tags: ["SEO", "Local", "Healthcare"]
seoTitle: "SEO Campaign Case Study"
---
# The challenge
Content body…8
Review & publishing checklist
Confirm these before publishing the item through GitHub. The trigger result is recorded in Publish Logs.
All required fields completedFill every field marked Required before moving to review.
Featured Image reference resolvesConfirm the media path exists in your repo.
SEO Title and Meta Description setWithin recommended length, unique per item.
Sent to Client Reviewers for approvalAdd review context so reviewers know what changed.
Scheduled or ready to publishConfirm date, time, and timezone if scheduling.
Deployment trigger profile configuredTrigger result is recorded in Publish Logs after publishing.
Turn templates into a publishing workflow.
Use Acrosite to create the structure, review content, schedule publishing, and keep output in GitHub.