WordPress powers a remarkable share of the web, from personal blogs to news sites, company pages, and online shops. It started in 2003 as blogging software and grew into a full content management system: software that lets people publish pages and posts, upload media, and manage a site without writing HTML for every page. Its popularity is its own advantage, because almost every hosting company supports it and almost every web problem has already been solved for it somewhere.

A WordPress site has two sides. The public side is what visitors see. The admin dashboard is where owners write posts, approve comments, install themes that control appearance, and install plugins that add features, like contact forms, search optimisation, or a shop. That split is why non-developers can run a WordPress site: publishing content needs no code, while developers can still customise everything underneath.

Under the hood, WordPress is PHP with a MySQL database. Content lives in the database, themes and plugins are PHP files, and the theme decides how content is displayed. The feature that surprises newcomers most is how much can be done with a small piece of PHP. A shortcode, for example, lets an editor drop a reusable piece of output into any post by typing a bracketed tag.

function pdp_greeting_shortcode($atts) { $atts = shortcode_atts( array('name' => 'reader'), $atts, 'greeting' ); return '<p>Hello, ' . esc_html($atts['name']) . '! Welcome to this site.</p>'; } add_shortcode('greeting', 'pdp_greeting_shortcode');

Put this in a theme's functions file or a small plugin, and typing [greeting name="Alex"] in a post prints "Hello, Alex! Welcome to this site." shortcode_atts fills in the default name when none is given, so [greeting] alone still works. esc_html escapes the name before it reaches the page, which stops a visitor-supplied value from injecting markup into the output, a small line that prevents a real class of security bug. add_shortcode registers the tag name with the function, connecting the editor's bracketed text to PHP code.

Themes and plugins are also WordPress's biggest risk, because they come from many authors of varying quality. A bloated theme or a dozen overlapping plugins can slow a site and open security holes, especially when updates are ignored. The discipline is simple: use well maintained themes and plugins with recent updates and many installs, delete what you do not use, and keep WordPress, themes, and plugins updated.

The honest trade

WordPress trades performance and fine control for speed and ease. A hand built site can be leaner and faster, and a custom app can do things WordPress was never designed for. But for content sites, blogs, and small shops, WordPress gets a working, editable site live in hours, with a huge ecosystem of themes, plugins, and people who know it. When a project outgrows it, that usually means it needed custom software all along, not that WordPress failed.

Publish first, perfect later

The fastest way to judge WordPress is to install it, pick a simple theme, and publish three real posts. You will learn more about themes, the editor, and plugins from one live site than from a week of reading comparisons, and you can always change the theme later without losing your content.

Originally published at https://practicaldevblog.blogspot.com/2026/11/wordpress-explained-software-running.html