01
Not everything is a blog post.
Case studies, FAQs, services, locations, testimonials, authors, resources, and glossary items need repeatable structure.
Feature · Custom Content TypesContent Type Studio
Create structured content without building a custom admin panel.
Acrosite lets teams create project-specific Custom Content Types with Custom Fields, SEO fields, media fields, and publish-ready Markdown/MDX output for Git-backed websites.
Custom Content TypesCustom FieldsSEO fieldsMarkdown/MDXFrontmatter
The structured content problem
Every website needs content that does not fit neatly into blog posts.
Some content is structured by nature — it repeats, it has fields, and it needs to stay consistent. Forcing it into a blog post, or building a one-off admin panel for it, is where most website projects start to drag.
02
Custom admin panels are expensive to rebuild.
Every project-specific content type can become another custom form, editor, validation layer, and publishing path.
03
Generic CMS modeling can become too heavy.
Teams need structured content without turning a simple website project into an enterprise CMS implementation.
04
Field consistency matters.
Repeatable content should use consistent labels, required fields, media references, and SEO fields.
05
Content still needs review and scheduling.
Structured records should move through the same review, approval, scheduling, publishing, and logging workflow.
06
Output must match the website.
Published records should become Markdown/MDX and frontmatter in the paths the Git-backed website expects.
Content Type Studio
Define the structure once, then create repeatable content items.
Pick a Custom Content Type, set its labels, key, and content path, and arrange the Custom Fields it needs. Every content item created from it starts with that structure already in place.
Case StudyCustom Content Type · acme-project
Name · singularCase Study
Name · pluralCase Studies
Keycase-studies
Content pathcontent/case-studies
SEO enabledOn
PublishableOn
Fields7 fields · drag to reorder
Client NameclientNameTextRequired
ChallengechallengeRich TextRequired
SolutionsolutionRich TextRequired
Result SummaryresultSummaryTextOptional
Featured ImagefeaturedImageImageOptional
SEO TitleseoTitleSEO fieldOptional
Meta DescriptionmetaDescriptionSEO fieldOptional
Custom Fields
Add the fields each project actually needs.
Custom Fields let teams shape Posts, Pages, and Custom Content Types around the content their website needs — with a field label, a stable field key, required or optional state, help text, and validation.
Field types
Text
Rich Text
Number
Date
URL
Boolean
Select
Multi-select
Image
Media
SEO fields
ReferenceAdvanced
CTA LinkField · ServicesURL
Field LabelCTA Link
Field KeyctaLink
RequiredRequiredOptional
Default value/contact
Help textWhere the service CTA button should link.
Validationmust be a valid URL
Reference fields are marked Advanced. Stick to text, rich text, number, date, URL, boolean, select, multi-select, image, media, and SEO fields for most project-specific structures.
Repeatable content
Create content items from the structure.
Once a Custom Content Type exists, teams can create individual content items with the right fields already in place — each one tracked toward publish-readiness.
What is Git-backed publishing?Published
Required fieldsCompleteSEO fieldsCompleteReviewApproved
Published to content path
Can clients review content?In Review
Required fieldsCompleteSEO fieldsPendingReviewIn Review
Awaiting SEO fields
Does Acrosite publish to GitHub?Ready to review
Required fieldsCompleteSEO fieldsCompleteReviewNot started
Ready for review
Publish-ready output
Structured content becomes Markdown/MDX with frontmatter.
Published Custom Content Type items are written to the configured repository path as Markdown/MDX with frontmatter your website can read — no manual file editing required.
Acrosite content itemStructured field values
Content TypeCase Study
TitleSEO Campaign Case Study
Client NameAcme Dental
Result Summary42% organic growth
Featured Imageseo-campaign.webp
SEO TitleSEO Campaign Case Study
Output pathcontent/case-studies/seo-campaign.mdx
Examples
Use Custom Content Types for the structured content your site already needs.
Each of these is a starting structure, not a fixed template — keep the fields you need, rename them, and add your own. Every card maps to a content path and publishes as Markdown/MDX.
Case Studiescontent/case-studies
Client NameTextChallengeRich TextSolutionRich TextResult SummaryTextFeatured ImageImageSEO fieldsSEO
FAQscontent/faqs
QuestionTextAnswerRich TextCategorySelectRelated ServiceReferenceSEO fieldsSEO
Servicescontent/services
Service NameTextDescriptionRich TextCTA TextTextCTA LinkURLRelated LocationsMultiSEO fieldsSEO
Locationscontent/locations
CityTextStateTextAddressTextService AreaTextPhoneTextSEO fieldsSEO
Authorscontent/authors
NameTextBioRich TextAvatarImageSocial URLURLRoleText
Testimonialscontent/testimonials
Customer NameTextQuoteRich TextRatingNumberCompanyTextFeatured ImageImage
Resourcescontent/resources
Resource TitleTextSummaryRich TextDownload URLURLCategorySelectFeatured ImageImage
Glossary Itemscontent/glossary
TermTextDefinitionRich TextRelated TermsMultiCategorySelectSEO fieldsSEO
Project-specific
Each website can have the structures it needs.
Acrosite lets each project define its own Custom Content Types, fields, content paths, and output rules — without forcing every website into the same model.
acmeagencyWorkspace · 3 projectsSame publishing workflow
Dental WebsiteCustom Content Types
ServicesLocationsFAQsTestimonials
content/…
SaaS WebsiteCustom Content Types
Changelog EntriesAuthorsResourcesComparison Pages
content/…
Agency WebsiteCustom Content Types
Case StudiesTeam MembersServicesPortfolio Items
content/…
Different projects, different structures and content paths — but the same review, scheduling, publishing, and Publish Logs workflow across the workspace.
Workflow
Structured content still moves through review, scheduling, and publishing.
Custom Content Type items can use the same Acrosite workflow as Posts and Pages: draft, review, approve, schedule, publish, and log.
Draft
Create the structured item and complete required fields.
Review
Send the item to Team Members or Client Reviewers.
Approve
Move the item toward publishing when review is complete.
Schedule or Publish Now
Publish immediately or schedule for a future time.
Commit to GitHub
Acrosite writes the Markdown/MDX file to the configured content path.
View Publish Logs
See commit status, deployment trigger result, and retry visibility.
Clear boundaries
What Custom Content Types mean in Acrosite.
A focused way to model structured website content — here is what it is, and what it deliberately is not.
Custom Content Types are
- User-defined structured content
- Project-specific content structures
- Repeatable content items
- Custom Fields
- Required and optional fields
- SEO-enabled content structures
- Markdown/MDX output
- Frontmatter-ready publishing
- Review, scheduling, and publishing support
Custom Content Types are not
- Competitor-style content model terminology
- A visual page builder
- A generic enterprise CMS modeling system
- A replacement for your website frontend
- A database builder for every use case
- Unlimited content modeling without plan limits
- A reason to expose GitHub to clients
Setup checklist
What you need before creating your first Custom Content Type.
A short list to confirm before you start — most of it is just naming the structure and choosing where its files live.
1
Project
Choose the website project where the structure belongs.
2
Content type name
Define singular and plural labels, such as Case Study and Case Studies.
3
Stable key
Set a path-safe key such as case-studies.
4
Fields
Add the Custom Fields the content item needs.
5
Content path
Choose the repository path where files should be written.
6
SEO and publishing settings
Decide whether the structure is SEO-enabled and publishable.
Custom Content Types FAQ
Questions about structured content.
Field types, publishing, SEO fields, client review, per-project structures, and changing fields later — the specifics teams ask before modeling their content.
Open documentationA Custom Content Type is a project-specific structure for repeatable website content such as Case Studies, FAQs, Services, Locations, Authors, Testimonials, Resources, or Glossary Items.
Posts are recurring editorial content. Pages are standalone website pages. Custom Content Types are for structured content that needs its own repeatable fields.
Yes. You can add Custom Fields such as text, rich text, URL, date, image, select, boolean, and other supported field types depending on the project configuration.
Yes, if the content type is publishable and has a configured content path. Published items can be written as Markdown/MDX with frontmatter.
Yes. Publishable Custom Content Types can support SEO fields such as slugs, SEO titles, meta descriptions, canonical URLs, Open Graph fields, and noindex controls where configured.
Yes. Assigned Custom Content Type items can be sent through Client Review, just like Posts and Pages.
Yes. Each project can define the Custom Content Types and fields it needs.
No. Your website frontend remains yours. Acrosite manages structured content and publishes Markdown/MDX output to your connected repository.
Field labels and settings can be adjusted carefully. Stable field keys should be treated more cautiously once content exists because they affect stored values and frontmatter output.
Start here
Create structured content without another custom admin build.
Registration is coming soon. Contact us to talk through your publishing workflow, or read the docs to see how Acrosite works.
Registration opening soonCustom Content TypesCustom FieldsMarkdown/MDXGitHub App