Collection (Statamic)

In Statamic, a Collection is a named group of content entries that share a common structure and purpose. A blog is a Collection. So is a portfolio, a team roster, a product catalog, or a help documentation library. Each entry in a Collection is stored as its own flat file — typically a Markdown file with YAML front matter — inside a content/collections/ directory.

The closest WordPress equivalent is a post type. In WordPress, you might have a post type for blog posts, a page type for standalone pages, and custom post types registered via code or a plugin for things like portfolio items or testimonials. Statamic Collections serve the same organizational role, but they’re configured differently. Rather than registering a post type in PHP, you create a Collection through the Control Panel or by adding a YAML file to content/collections/. Each Collection gets a configuration file that defines its behavior.

Collections in Statamic are quite configurable. You can set the URL structure for entries (e.g., /blog/{slug} or /news/{year}/{month}/{slug}), choose how entries are ordered (by date, by a custom sort field, or manually), enable or disable drafts and scheduling, and attach one or more Blueprints that define the fields available on each entry. A Collection can have multiple Blueprints if different entry types need different fields.

During a WordPress to Statamic migration, mapping your existing content types to Collections is one of the first decisions to make. A standard WordPress setup migrates pretty directly: posts become entries in a Blog collection, pages become entries in a Pages collection. Custom post types become their own Collections. The migration guide walks through this mapping in more detail.

One practical difference from WordPress: there’s no global "pages vs. posts" distinction hardcoded into the system. Pages are just a Collection with a certain Blueprint and URL structure. That uniformity makes it easier to manage content consistently, since the same editing interface works across all content types.