Updated October 9, 2026.
WordPress is a content management system, or CMS: software for creating, organizing and publishing website content. It gives staff an editing interface rather than requiring them to change website code for every article or image update.
If you already have a WordPress site, understanding its parts helps you manage it and discuss changes with a developer. If you are planning a new website, compare the editing and maintenance arrangements as carefully as the design.
The main parts of a WordPress website
WordPress combines publishing software with a theme and, where needed, plugins. Its official feature overview describes content publishing, themes, plugins and user management.
| Part | What it does | Question for your web partner |
|---|---|---|
| WordPress core | Provides the main publishing and administration system | Who keeps it updated and tests changes? |
| Theme | Defines much of the presentation and page layout | Which parts can staff edit safely? |
| Plugins | Add or change features | Which are necessary, licensed and maintained? |
| Content and media | Supply the pages, posts and images visitors see | Who owns the content and has access to exports? |
| Hosting and data storage | Run the site and store its files and database | What is backed up, and who can restore it? |
The free software license is only one part of the budget. Hosting, paid themes or plugins, configuration and ongoing work can all have costs. Request an itemized quote instead of treating a free CMS as a free finished website.
WordPress.com and WordPress.org
WordPress.org is where you can obtain the open-source software and community resources. You can run that software with a hosting provider of your choice, subject to the provider’s technical requirements and terms.
WordPress.com is a hosted service built around WordPress. Its plans bundle hosting and other features, with inclusions and restrictions that vary. WordPress.com’s comparison explains the relationship between the service and self-hosting.
Avoid deciding from an old feature table. As checked October 9, 2026, WordPress.com’s plugin documentation says plugin installation is available on all paid plans. Confirm that your particular plugins and required features are supported before buying.
Both arrangements can serve business websites. The useful distinction is who operates the system, what you can change, and what support you receive.
Editing content versus changing the design
An editor might need to publish a project, update a service description or replace a photo. Those tasks do not necessarily require control over every layout setting.
WordPress has a block-based editing workflow, while some sites use an additional visual page builder. Ask for a demonstration on a representative page. Have the person who will maintain the site try it:
- Change a heading and paragraph.
- Add an image with appropriate alternative text.
- Preview the mobile layout.
- Save a draft, obtain approval and publish.
- Find out how to reverse an unwanted change.
Confirm what happens when the theme or builder changes later. Content, layouts and plugin-specific features may need separate migration work. Do not assume that switching a theme preserves the entire presentation.
Plugins should solve a named requirement
A plugin can provide a form, booking integration or other feature. Before adding one, identify the problem it solves and check whether the current setup already covers it.
Ask who maintains the plugin, how updates and paid renewals work, and what happens if it becomes unavailable. Check compatibility with the actual site. A small plugin count alone does not establish speed or safety, and buying a security plugin does not replace a maintenance process.
For an online store, the decisions also include payments, orders and fulfillment. Our WooCommerce explainer separates those operating requirements from the website’s design.
Give maintenance a clear owner
Agree who handles updates, backups, access and incidents. WordPress’s hardening guidance covers keeping software current, trusted sources, access protections and recoverable backups. Treat these as continuing responsibilities rather than a one-time installation checklist.
A practical handover should identify:
- The hosting, domain, administrator and recovery accounts controlled by the business.
- The person responsible for monitoring update notices and applying fixes.
- A test environment and a way to reverse changes that fail.
- Backup coverage for the database, uploaded files and custom code, plus restoration instructions.
- Support contacts and what their agreements actually cover.
Use individual accounts and grant only the access each person needs. WordPress’s roles and capabilities reference distinguishes administrators from content roles such as editor and author. Plugins can alter permissions, so verify access on your own site. When someone leaves, remove their access while preserving and reassigning business content as needed.
Should you keep WordPress or choose something else?
Keep a working site when it supports your publishing, customer tasks and maintenance budget. A new framework is not, by itself, a business reason to rebuild.
When evaluating a new site or a substantial replacement, compare:
- Editing: who publishes, how often, and with what approval process?
- Functionality: which forms, accounts, bookings or commerce features are essential?
- Care: who maintains each part, and how quickly can they respond?
- Portability: what content, data and source files can the business take elsewhere?
- Cost: what is included at launch and over the next few years?
A hosted builder, WordPress or a custom site can each fit different combinations of those requirements. Our Astro and WordPress comparison examines the platform decision; the website planning guide helps define the project before selecting tools.
Our website development services use Astro, with a CMS when the project needs an editing workflow. We do not offer new WordPress builds, theme development or general WordPress support.