WordPress 3.0 explained
WordPress 3.0 introduced the custom menu and the custom post type. Both still shape how every WordPress site is built.
What changed
Before 3.0, menus were hard-coded in theme templates and content types were improvised out of categories. The release moved both into the administration interface, which reorganised who is responsible for structure: it moved from the developer to the person running the site.
Why it mattered more than it looked
The consequences
- Custom post types made WordPress a content management framework, not just a blog engine
- Editable menus removed a category of routine developer work
- Multisite consolidated existing multiuser forks into core
- The theme became presentation rather than structure
How it looks today
The same separation underpins the block editor and full-site editing. Content modelling is now explicitly a data design decision, which is why we treat it as the first decision in any build. See WordPress.
Written retrospectively about a 2010 release. Kept because the structural shift it caused is still the reason WordPress scales.
Talk to us about your project
If you are planning a WordPress build, a WooCommerce migration or a growth programme, we will tell you honestly whether it is a fit.