{"canonical_url":"https://engineer.company/glossary/wordpress/","content_markdown":"# WordPress\n\n## What it is\n\nWordPress is an open-source content management system: PHP software that keeps\na site's posts, pages, media records, users and settings in a MySQL or MariaDB\ndatabase and assembles pages from them on request. Uploaded media files\nnormally live outside the database. Its name is often shortened to WP, the\nsame prefix its own files and folders carry (wp-config.php, wp-content,\nwp-admin). It is released under the GPLv2 (or later), so the software costs\nnothing to download, run or change.\n\nThree layers make up a WordPress site. Core is the shared code that everyone downloads and updates.\nA theme controls presentation and plugins add behaviour, which is where the project's own theme\nhandbook draws the line. Both reach into core through hooks, named points in the WordPress code\nwhere other code is allowed to run, and hooks come as actions and filters. An action runs at a\nmoment, such as a post being saved, and returns nothing. A filter receives a value, changes it and\nhands it back. This one shortens automatic post excerpts from the default 55 words to 30:\n\n```php\nadd_filter( 'excerpt_length', function ( $length ) {\n    return 30;\n} );\n```\n\nThemes have changed shape over the years. Classic themes use the PHP template system that arrived\nwith WordPress 1.5 in 2005, and they are still in wide use. Block themes are the current approach:\ntheir templates are HTML files built from blocks, editable in the Site Editor, with colours, fonts\nand spacing held in a theme.json file. Hybrid themes are classic themes that have taken on some of\nthe block features.\n\nContent also leaves the site as JSON through the REST API, which the block editor itself is built\non. A request to the site's /wp-json/ address returns a map of every route it offers, public content\nis readable without signing in, and anything private needs authentication. Any program can fetch the\nthree latest posts like this:\n\n```sh\ncurl -s 'https://example.com/wp-json/wp/v2/posts?per_page=3'\n```\n\nTo run it, the project recommends PHP 8.3 or greater, MySQL 8.0 or MariaDB 10.11 or greater, and\nHTTPS, preferably on Apache or Nginx. Joomla and Drupal are content management systems of the same\nkind, and the two other routes to weigh it against are a custom application on a framework such as\nDjango and a static site generator.\n\n## Why it matters\n\nThe real decision behind WordPress is who changes the site after launch, and who keeps it safe while\nthey do. WordPress hands non-technical staff a complete editor: they can publish a page, swap an\nimage, add a user or rework a menu without opening a ticket. On a site that changes every week, the\ncheapest edit is the one that needs no developer.\n\nThe licence is free, but the site is not. The GPL covers the software, and wordpress.org takes the\nview that plugins and themes are derivative works that inherit the same licence. The spending moves\nelsewhere: hosting that runs PHP and a database, the hours to choose, set up and test a theme, and\nthe ongoing work of keeping core, plugins, themes and the PHP version current. That last cost runs\nfor the life of the site, and a quote should name who carries it.\n\nThe upkeep follows from WordPress being a live application. Uncached page\ngeneration runs PHP against a database; a full-page cache can serve a saved\npage. Plugin code runs with the same access as core,\nand the login screen sits on the open internet unless someone puts a second\nlock in front of it. Background core updates arrived in version 3.7. New\ninstallations from 5.6 onward enable both minor and major core updates by\ndefault, subject to configuration and update eligibility; older installations\nretain their previous settings unless changed. PHP keeps a separate update\nschedule.\n\nA custom build fits data and workflows that look nothing like pages and posts,\nand its editing workflows need to be built and maintained. A static build\nremoves the PHP and database application from the request path, while its\nserver and build tools still need upkeep. Its editors usually work through\nfiles and a build step. WordPress fits the wide middle: a fairly standard site\nthat its owners will run themselves, where the editing screens are worth the\nupkeep they bring. Lock-in stays modest, because the code is GPL, the content\nsits in an ordinary SQL database, and the REST API serves posts, pages and\ntaxonomies as JSON.\n\n## What it looks like in practice\n\nIn this company's work WordPress is one answer among several, picked on purpose.\n[The write-up of a hundred web applications](/portfolio/developed-100-web-applications-using-html-html5/)\ncovers 2003–2014 and states the rule behind the choice. When a client needed something custom, the\nbuild was HTML/HTML5, CSS/SCSS and Django. When a client needed a more standard site that they could\nalso look after themselves, WordPress or Joomla got there sooner and made more sense.\n\nWhat that write-up values is the judgement, not the tool. Part of the work it describes was telling\nthe two cases apart: talking a client out of a bespoke build they did not need, and into one when\nthe need was real.\n\nPut as questions a buyer can answer before asking for any quote, the judgement looks like this:\n\n- Will people without a developer edit the site every week, or will it change a few times a year?\n- Does the content fit pages, posts, categories and media, or does it need its own data model and\n  rules?\n- Who will keep core, plugins and PHP current for as long as the site is live?\n- Will the site lean on a handful of well-kept plugins, or on dozens of them stitched together to\n  imitate an application?\n\nWeekly edits, content that fits, a named maintainer and a short plugin list point to WordPress or a\nCMS like it. Unusual data, or nobody to keep it current, points to a custom build or a static one.\n\n## Where it goes wrong\n\n### A routine update breaks the site\n\nSomeone updates a plugin, and a page starts showing an error or the dashboard refuses to load. The\nsite had gathered plugins for years, some of them abandoned by their authors, each one third-party\nPHP running with full access, and two of them clashed. Keep the list short, and delete every plugin\nthe site has stopped using, as the hardening handbook asks. Take a backup before every update, try\nmajor ones on a copy first, and prefer plugins whose authors still ship releases.\n\n### Custom changes vanish after an update or a redesign\n\nA tweak that worked for months disappears the day the theme updates, or a feature the business\nrelies on goes missing when the site gets a new look. In the first case someone edited the files of\na theme they did not write, and the update replaced them; the theme handbook warns that a function\nadded straight into a theme's functions.php disappears with its next update. In the second,\nsite-critical behaviour lived in the theme, so it left with the theme. Put changes to someone else's\ntheme in a child theme, and put features in a small plugin of your own that hooks into core, so the\ntheme carries presentation and nothing else.\n\n### An admin password turns into code on the server\n\nWhoever steals one administrator's password can go from editing posts to running their own PHP,\nbecause the dashboard ships with an editor for theme and plugin files. One line in wp-config.php\nswitches that editor off, which has the same effect as removing the edit_themes, edit_plugins and\nedit_files capabilities from every user:\n\n```php\ndefine( 'DISALLOW_FILE_EDIT', true );\n```\n\nIt closes one route among several, and the handbook says plainly that it will not stop an attacker\nwho can upload malicious files. Pair it with strong passwords, two-step authentication for every\nadministrator, and as few administrator accounts as the work allows.\n\n### The site falls behind the current release\n\nThe dashboard shows a new-version banner for months while the site runs a\nmajor release, or a PHP version, well behind the current one. A site\nconfigured for minor core updates only can keep patching itself while its\nmajor version and PHP fall behind, until a plugin it depends on demands\nsomething newer. New installations from 5.6 also enable major core updates by\ndefault, but configuration can change that. Put major updates on a calendar,\ncheck the PHP version against the project's requirements page at the same\ntime, and test both on a copy before the live site.\n\n## Further reading\n\n- [WordPress Documentation](https://wordpress.org/documentation/)\n  — the project's manual for running a site, from publishing and media to installing and\n  maintaining it.\n- [Requirements](https://wordpress.org/about/requirements/)\n  — the PHP, MySQL and MariaDB versions the project recommends today.\n- [Upgrading WordPress](https://developer.wordpress.org/advanced-administration/upgrade/upgrading/)\n  — background, one-click and manual updates, with the backup to take first.\n- [Hardening WordPress](https://developer.wordpress.org/advanced-administration/security/hardening/)\n  — file permissions, database privileges, the switch for the file editor and plugin hygiene.\n- [Plugin Handbook: Hooks](https://developer.wordpress.org/plugins/hooks/)\n  — how actions and filters let code change WordPress without touching core.\n- [REST API Handbook](https://developer.wordpress.org/rest-api/)\n  — routes, endpoints and authentication for the API the block editor is built on.\n\n\u003chttps://engineer.company/glossary/wordpress/\u003e\n","date_modified":"2026-11-09T21:50:25Z","description":"How WordPress builds a site from PHP, a database, a theme and plugins, when it beats a custom build, and the update habits that keep it safe.","formats":{"gemtext":"https://engineer.company/glossary/wordpress/index.gmi","gopher":"https://engineer.company/glossary/wordpress/gophermap","html":"https://engineer.company/glossary/wordpress/","json":"https://engineer.company/glossary/wordpress/index.json","markdown":"https://engineer.company/glossary/wordpress/index.md","pdf":"https://engineer.company/glossary/wordpress/index.pdf"},"kind":"page","language":"en","title":"What is WordPress?","url":"https://engineer.company/glossary/wordpress/","version":1}