CMS & Migration Glossary | WP to Statamic

301 Redirect

A 301 redirect tells browsers and search engines that a URL has permanently moved to a new location. It’s the standard tool for preserving SEO equity when URLs change during a migration.

Read more →

An addon is the Statamic equivalent of a WordPress plugin — a packaged extension that adds functionality to your Statamic site. Addons are installed via Composer and can add new fieldtypes, Control Panel sections, integrations, commands, or site features.

Read more →

Advanced Custom Fields (ACF)

Advanced Custom Fields (ACF) is a WordPress plugin that adds a flexible custom field system to posts, pages, and custom post types. It’s the most popular solution for structured content in WordPress, and migrating ACF data is a central part of most WordPress-to-Statamic migrations.

Read more →

Antlers

Antlers is Statamic’s built-in templating language. It handles variable output, loops, conditionals, and tag calls using a double-curly-brace syntax that’s specific to Statamic.

Read more →

Artisan (CLI)

Artisan is the command-line interface built into Laravel, and by extension, into every Statamic site. It provides commands for common development tasks and can be extended with project-specific or addon commands.

Read more →

Asset Container

An asset container is Statamic’s way of organizing and managing media files. Each container is a defined storage location — local disk or cloud storage — with its own configuration, field metadata, and browser interface in the Control Panel.

Read more →

Bard (Field Type)

Bard is Statamic’s rich text and block-based field type. It lets editors mix prose, images, and custom content blocks in a single field, storing the result as structured data rather than raw HTML.

Read more →

Blade (Templating)

Blade is Laravel’s templating engine and an alternative to Antlers in Statamic projects. It gives developers direct access to PHP within templates using a clean directive syntax.

Read more →

Blueprint (Statamic)

A Blueprint defines what fields are available on a piece of content in Statamic — things like title, body, featured image, or any custom field you need. It’s how you configure the editing interface and the data structure for your content types.

Read more →

Canonical URL

A canonical URL is the preferred version of a page that you want search engines to index. It’s used to consolidate ranking signals when the same or similar content is accessible at multiple URLs.

Read more →

CDN (Content Delivery Network)

A CDN is a distributed network of servers that caches and serves your site’s assets from locations close to your visitors. It reduces load times and takes traffic load off your origin server.

Read more →

Collection (Statamic)

A Collection in Statamic is a container for related content entries, each stored as its own file. Collections replace WordPress’s post types and define how content is structured, ordered, and routed.

Read more →

Composer

Composer is the standard package manager for PHP. You use it to install Statamic, manage Laravel dependencies, and add third-party packages to your project. Most Statamic workflows involve running Composer commands from the terminal.

Read more →

Content Management System (CMS)

A content management system is software that separates content from code, letting editors update a site without touching templates or databases directly. WordPress and Statamic are both CMSes, but they take very different approaches to storing and serving that content.

Read more →

Content Modeling

Content modeling is deciding how your content is structured before you build it — what types of content you have, what fields each type needs, and how different content types relate to each other. In Statamic, your content model is expressed through Collections, Blueprints, Taxonomies, and Fieldtypes.

Read more →

Control Panel

The Control Panel is Statamic’s admin interface — the browser-based UI where editors manage content and developers configure the site. It’s accessible at /cp by default and serves a similar role to the WordPress Dashboard.

Read more →

Core Web Vitals

Core Web Vitals are a set of performance metrics from Google that measure real-world user experience: how fast a page loads, how quickly it responds to input, and how stable the layout is. They factor into search rankings.

Read more →

Custom Post Type

A Custom Post Type (CPT) is a WordPress feature that lets you define content types beyond the built-in posts and pages — things like team members, case studies, events, or testimonials. In Statamic, collections serve a similar purpose with a cleaner architecture.

Read more →

Eloquent

Eloquent is Laravel’s built-in ORM for working with databases using PHP objects. In Statamic, Eloquent drivers can replace the default flat-file storage for content, users, or other data when a database is the better fit.

Read more →

Entry (Statamic)

An entry is the fundamental unit of content in Statamic. It belongs to a collection, has fields defined by a blueprint, and typically corresponds to a single page or content record on your site.

Read more →

Fieldtype

A Fieldtype is the building block of a Statamic field — it determines what kind of data a field holds and what UI control an editor uses to interact with it. Statamic ships with around 40 fieldtypes covering most common content needs.

Read more →

Flat-File CMS

A flat-file CMS stores content as files on the filesystem instead of in a database. Statamic uses this model by default, which changes how content is deployed, backed up, and version-controlled.

Read more →

Globals (Statamic)

Globals are Statamic’s system for storing site-wide content and settings that aren’t tied to a specific page or entry. They’re available in every template automatically, making them useful for things like contact details, social links, and navigation labels.

Read more →

Gutenberg (Block Editor)

Gutenberg is the block-based editor built into WordPress since version 5.0. It stores content as block markup in the post content field, which affects how content is extracted and migrated to other systems.

Read more →

Headless CMS

A headless CMS handles content storage and management but leaves rendering entirely to a separate frontend. Content is delivered via API rather than built into HTML by the CMS itself.

Read more →

Laravel

Laravel is the PHP framework that Statamic is built on. It provides the routing, authentication, file handling, and overall application structure that Statamic runs on top of.

Read more →

Page Builder

A page builder is a visual drag-and-drop interface for building page layouts without coding. They’re common in WordPress, but their output often comes at a performance and portability cost that makes migrations more complicated.

Read more →

robots.txt

robots.txt is a plain text file at the root of your site that communicates crawling rules to search engine bots. It tells them which areas they’re allowed to access and which to skip.

Read more →

Schema Markup (Structured Data)

Schema markup is structured data added to your pages that helps search engines understand what your content is about. It can unlock rich results in Google Search, like star ratings, FAQ dropdowns, and event details.

Read more →

Statamic

Statamic is a Laravel-based CMS that stores content in flat files rather than a database. It’s the destination platform for most WordPress-to-Statamic migrations.

Read more →

Static Caching

Static caching is a Statamic feature that stores rendered page HTML as static files on disk. When enabled, returning visitors are served cached HTML directly without triggering a PHP request — which makes pages load faster and reduces server load.

Read more →

Static Site Generator (SSG)

A static site generator compiles your content and templates into plain HTML, CSS, and JavaScript files during a build step. Those files are served directly without a server-side language or database running at request time.

Read more →

Taxonomy

A Taxonomy in Statamic is a classification system — a set of terms used to group and filter content. Tags, categories, and topics are all common examples. Like everything in Statamic, taxonomy terms are stored as flat files.

Read more →

Version Control (Git)

Version control — Git in particular — tracks every change made to your project files over time, allowing you to review history, revert mistakes, and collaborate without overwriting each other’s work. Statamic’s flat-file architecture makes it uniquely suited to version-controlling content alongside code.

Read more →

WordPress Multisite

WordPress Multisite is a built-in feature that lets you run multiple websites from a single WordPress installation. It’s powerful for managing networks of related sites, but migrating away from it requires careful planning.

Read more →

XML Sitemap

An XML sitemap is a structured file that lists the URLs on your site, helping search engines find and index your content. It’s a standard part of any SEO-conscious site setup.

Read more →

Glossary

The jargon, translated

301 Redirect

Addon

Advanced Custom Fields (ACF)

Antlers

Artisan (CLI)

Asset Container

Bard (Field Type)

Blade (Templating)

Blueprint (Statamic)

Canonical URL

CDN (Content Delivery Network)

Collection (Statamic)

Composer

Content Management System (CMS)

Content Modeling

Control Panel

Core Web Vitals

Custom Post Type

Eloquent

Entry (Statamic)

Fieldtype

Flat-File CMS

Globals (Statamic)

Gutenberg (Block Editor)

Headless CMS

Laravel

Page Builder

robots.txt

Schema Markup (Structured Data)

Statamic

Static Caching

Static Site Generator (SSG)

Taxonomy

Version Control (Git)

WordPress Multisite

XML Sitemap

Ready to explore migration?