WP-C key terms

Software that lets people create, store, edit, and publish digital content through a browser interface, separating the content from the code that displays it. WordPress is the most widely used example.

A collection of templates and stylesheets that controls how a WordPress site looks and how its pages are laid out, without altering the stored content itself.

A theme that inherits the design and functionality of a parent theme while holding its own customizations, so parent updates do not overwrite your changes. It requires a style.css header naming the parent.

An installable package of PHP code that adds or extends functionality on a WordPress site without editing core files. Plugins can hook into the system at defined points.

A content type in WordPress. Built-in types include posts and pages; developers can register custom post types for content such as events or products, each with its own editor and archive behavior.

A system for grouping content in WordPress, such as categories and tags for posts or custom taxonomies for other post types. Terms are the individual items within a taxonomy.

A single item within a taxonomy, such as one category or one tag. Terms can have names, slugs, descriptions, and parent-child relationships that form hierarchies.

Extra structured data attached to a post, page, or other content object and stored as a key-value pair. It lets templates display information beyond the standard title and body.

The block-based editor introduced in WordPress 5.0, where content is built from discrete blocks such as paragraphs, images, and columns. It replaced the earlier classic editor as the default.

A self-contained content or layout unit in the WordPress editor, such as a heading, image, or group. Blocks are stored as annotated markup and can carry their own settings and styles.

A theme built primarily with block templates and global styles instead of PHP template files, edited through the Site Editor. It relies on theme.json for settings and supports full site editing.

A saved block or group of blocks that can be inserted on multiple pages and edited in one place, with changes syncing everywhere it appears. Now commonly called a synced pattern.

The ordered set of rules WordPress uses to decide which theme file renders a given request, trying the most specific template first and falling back to broader ones such as index.php.

The permanent URL of a piece of content. WordPress permalink settings control the structure of these URLs, and clean structures using slugs generally help usability and search visibility.

The URL-friendly version of a title or term name, containing lowercase letters, numbers, and hyphens. It identifies content in permalinks and should be unique within its context.

Data that describes other data. In WordPress it includes post meta, term meta, and user meta, stored in database tables and retrieved through dedicated functions rather than direct queries.

A named point in WordPress execution where plugin or theme code can attach a callback function to run at that moment, such as when a post is published or a page is loaded.

A named point where code can intercept a value, modify it, and return the result for further processing. Filters change data rather than triggering side effects at a moment in execution.

The core configuration file holding database credentials, authentication keys and salts, debugging settings, and the table prefix. It sits in the site root and should never be publicly readable.

The string prepended to WordPress table names, defaulting to wp_ but often changed for security or to share one database. It is set in wp-config.php and must match the actual tables.

Random secret strings in wp-config.php used to hash authentication cookies and signed values. Rotating them invalidates existing logins and helps recover from a compromised site.

A one-time token tied to a user session and action, used to verify that a request came from the site itself. It protects forms and links against cross-site request forgery.

A permission assigned to a user role, such as editing posts or managing options. Code checks capabilities rather than role names so permissions can be reassigned flexibly.

A named bundle of capabilities given to users, such as administrator, editor, author, contributor, or subscriber. Custom roles can be created with tailored capability sets.

A constant in wp-config.php that turns on PHP error reporting for development. Related constants control whether errors display on screen or are logged to a file instead.

WordPress's pseudo-scheduler, which runs scheduled tasks such as publishing scheduled posts or checking updates when a page is visited, rather than on a true system timer.

Storing rendered pages, queries, or objects so later requests are served faster without repeating expensive work. Layers include page cache, object cache, and browser cache.

A store for the results of database queries and computed data during and across requests. A persistent backend such as Redis or Memcached can survive between page loads.

A temporary cached value with an expiration time, stored in the options table or a persistent object cache. It is commonly used to store results of remote API calls.

A plugin placed in the mu-plugins directory that is loaded automatically and cannot be deactivated from the admin. It is often used for site-wide, always-on functionality.

A server or application rule that sends a visitor from one URL to another, typically with a 301 for permanent moves or a 302 for temporary ones. It preserves link equity and avoids broken links.

A copy of site files and database content kept separately so the site can be restored after failure, attack, or accidental deletion. Regular tested backups are a core operational safeguard.

A duplicate of a live site used to test updates, plugins, and design changes before they reach production. It should be isolated and never indexed by search engines.

Practices that help content rank and display well in search results, including clear titles, descriptive URLs, structured headings, fast pages, and relevant internal links.

Designing and building content and interfaces so people with disabilities can perceive and operate them, using semantic markup, keyboard support, sufficient contrast, and alternative text.

A written statement defining the deliverables, timeline, assumptions, and boundaries of a project. It protects both client and provider by clarifying what is and is not included.

A documented agreement to modify an existing project's scope, price, or schedule after work has begun. It prevents unpaid extra work and keeps expectations aligned.

A recurring fee a client pays for ongoing services such as maintenance, updates, and support. It provides predictable revenue and defines a set level of monthly work.

A contract clause or document specifying expected service levels, such as response times and uptime targets, plus remedies when those levels are not met.

The full lifetime cost of a website, including hosting, licenses, maintenance, updates, training, and staff time, not just the initial build price. It informs budget and platform decisions.