Understanding Pages, Posts, and Custom Post Types

WordPress gives you a few different ways to organize and publish content — most commonly Posts, Pages, and Custom Post Types. While they may look similar in the editor, each one is designed for a different purpose.


How content types work

The key difference isn’t how you create content — it’s how that content is structured, organized, and displayed across your site.

Each content type supports a different way of organizing content:

  • Posts are organized over time and grouped using categories and tags
  • Pages are structured hierarchically and represent core, standalone content
  • Custom Post Types are designed for specific content types with defined structure and behavior

Choosing the right content type helps:

  • Keep your content organized and easy to manage
  • Support consistent layouts and display patterns
  • Make it easier for users to navigate and find content
  • Ensure your site scales effectively as content grows

Before creating new content, it’s important to understand which content types are available on your site — and how each one is intended to be used.


Posts

Posts are typically used for time-based or regularly updated content.

Common use cases:

  • Blog articles or news updates
  • Announcements or editorial content
  • Content that benefits from categories, tags, or archives

Posts are designed to be dynamic and time-based, often appearing in feeds or automatically generated lists.

How posts are organized

Posts use taxonomies — most commonly categories and tags — to group and organize content.

  • Categories group related posts into broader topics
  • Tags provide more specific labels or keywords

This structure makes it easier to:

  • Filter and display related content
  • Create category-based pages or archives
  • Help users navigate large amounts of content

Pages

Pages are used for static, evergreen content that doesn’t change frequently.

Common use cases:

  • Homepage
  • About page
  • Contact page
  • Landing pages

Pages are typically standalone and not organized by date or taxonomy in the same way as posts.

How pages are organized

Pages use a hierarchical structure, meaning they can have parent and child relationships.

  • A parent page is a top-level page
  • A child page sits beneath a parent and inherits part of its URL

For example:

  • /about/ (parent)
  • /about/team/ (child)

This structure helps:

  • Organize content into logical sections
  • Create clear, readable URLs
  • Reflect site navigation and hierarchy

Custom post types

Custom Post Types (often called CPTs) are used for structured content with specific goals or repeatable formats. They are custom-built to support more complex content needs.

Not every site includes custom post types. If your site does, they have been intentionally designed to support specific types of content.

Common examples:

  • Case Studies
  • Events
  • Team Members
  • Resources or Publications

While this content could be created using Posts or Pages, custom post types provide:

  • More intentional content structure
  • Better organization and filtering
  • Cleaner, more consistent URL structures
  • Support for dynamic displays (like listings or archives)

How custom post types are structured

Custom post types are designed based on your site’s content needs, and may behave like Posts, Pages, or a combination of both.

Depending on how they’re built, a CPT may include:

  • Taxonomies (like categories or tags) for grouping and filtering content
  • Hierarchical structure (parent/child relationships), similar to Pages

Some CPTs use one approach, while others may support both. Because of this flexibility, it’s important to follow the intended structure of each custom post type rather than assuming it behaves like a Post or Page.

Working with custom post types

Custom post types are specific to your site and are not documented in Learn.tri.be.

If your site includes custom post types:

  • Refer to your project-specific training materials
  • Follow the established structure and fields
  • Use them consistently for their intended purpose

Custom post types may be added through the ModernPress framework or via plugins and extensions. For example, plugins like event management tools (such as The Events Calendar) may introduce their own custom post types to manage specific types of content.


Best practices

Become familiar with your content types

Before adding new content, take time to review which content types are available on your site — including any custom post types. Choosing the right type upfront helps avoid rework later and keeps content organized.

Be consistent

Use the same content type for similar content. For example, don’t mix Case Studies between Pages and a custom Case Studies post type. Consistency makes content easier to manage and display across the site.

Follow the intended structure

Each content type is designed with a specific purpose.

  • Posts are for time-based content
  • Pages are for structured, evergreen content
  • Custom post types are built for specific content types

Use each one as intended rather than adapting it for unrelated use cases.

Keep scalability in mind

If you expect content to grow over time, Posts or Custom Post Types are usually a better fit than Pages.


  1. WordPress.org Post vs Page documentation — Please note that your implementation may include customizations that affect how content types behave
  2. Creating Posts
  3. Creating Pages