Posts vs Pages vs Custom Content Types
When to use a Post, a Page, or a Custom Content Type — the three kinds of content an Acrosite project holds, and how each one is structured and stored.
Every Acrosite project holds three kinds of content: Posts, Pages, and Custom Content Types. They use the same editor and the same publishing pipeline, but each one models a different kind of content. Choosing the right one keeps your repository tidy and your site templates predictable.
The three content kinds
- Posts — recurring editorial content: blog articles, news, updates, release notes. Posts are a built-in (system) content type, so every project has them from day one.
- Pages — standalone website pages: an About page, a Pricing page, a landing or service page. Pages are also a built-in system content type.
- Custom Content Types — your own repeatable structures, such as Case Studies, Testimonials, FAQs, Services, or Locations. You define these per project, and each one can carry its own Custom Fields.
Posts and Pages are always available. Custom Content Types are ones you create when the same set of fields repeats across many items.
How to choose
Ask what you are modelling:
- Is it a stream of dated, editorial entries? Use a Post.
- Is it a single, mostly one-off site page? Use a Page.
- Is it a repeatable record with the same fields every time? Create a Custom Content Type so each item captures the same structure.
A good rule: if you find yourself copying the same custom fields onto many Posts, that content probably wants to be its own Custom Content Type instead.
What they share
All three kinds use the same editor (title, slug, body, excerpt, featured image, Custom Fields, and SEO), move through the same review and publishing flow, and are committed to your repository as Markdown with frontmatter. The difference is only the structure and the folder each one publishes to. See Generated Markdown and frontmatter for the output, and The Content Structure page for where each type lives.