Case Study Template
Suggested fields for client name, challenge, solution, result summary, featured image, and SEO fields.
Back to Templates
Custom Content Types
FAQ Template
A repeatable Custom Content Type structure for FAQ question, answer, category, and related service.
1
When to use this template
Use this template when you publish a library of FAQs as a Custom Content Type — each item a single question and answer that can be grouped, searched, and reused across pages.
A shared structure keeps answers consistent and lets you surface the same FAQ items on multiple service or location pages.
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
QuestionquestiontextRequired
AnsweranswerMDXRequired
CategorycategoryselectOptional
Related ServicerelatedServicetextOptional
SEO TitleseoTitletextSEO
Meta DescriptionmetaDescriptiontextareaSEO
3
Required fields
The minimum fields every item should have before it can move to review.
Field labelField keyTypeStatus
QuestionquestiontextRequired
AnsweranswerMDXRequired
4
Optional fields
Useful additions you can include per item, or leave out when they don't apply.
Field labelField keyTypeStatus
CategorycategoryselectOptional
Related ServicerelatedServicetextOptional
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
questionIs there a free trial?
answerYes — Acrosite includes a 14-day free trial.
categoryBilling
relatedServicePlans & Pricing
seoTitleAcrosite Free Trial FAQ
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.
---
question: "Is there a free trial?"
category: "Billing"
relatedService: "Plans & Pricing"
seoTitle: "Acrosite Free Trial FAQ"
---
# Answer
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.