Every WordPress release comes with a blog post explaining how transformative it is. Most of them are not. A handful of the changes over recent years genuinely altered how sites get built, and this is an attempt to separate those from the noise.
Key takeaways
- The block editor is the change that mattered. Everything since has been iteration on it.
- Full Site Editing lets you edit headers and footers without touching theme files, if your theme supports it. Many do not, and that is a legitimate choice.
- Performance improvements arrive quietly and benefit you without any action.
- Auto-updates for plugins and themes are the most useful under-used setting in the admin.
The block editor
WordPress replaced its single text box with an editor built from blocks: paragraph, heading, image, table, each independently movable.
It was unpopular on arrival and much of the complaint was fair at the time. It is considerably better now, and importantly it produces clean, portable markup rather than the shortcode soup that page builders leave behind. Content written in blocks survives a theme change. Content written in a proprietary builder frequently does not.
If you are still on the classic editor, that is a defensible choice rather than a failure. It also means each new release is doing progressively less for you, since nearly all editor work now goes into blocks.
Full Site Editing
With a block theme, the header, footer and templates become editable in the same interface as your content, instead of requiring theme files or a page builder.
The honest assessment: it is powerful and it is not always pleasant. Editing a template is more fiddly than editing a page, and it is easy to change something globally while believing you changed it locally.
It also only applies if your theme is a block theme. A large share of sites run classic themes and will not see any of it, which is fine.
Patterns
A pattern is a pre-arranged group of blocks you can insert and edit: a pricing table, a testimonial row, a hero.
This is the feature most people would benefit from and most people have never opened. If you rebuild the same three-column layout on every page, saving it once as a pattern removes that work permanently.
Performance work you get for free
Several releases have improved image handling and loading behaviour without anyone needing to do anything. Lazy loading became default. Modern image format support improved.
This is the most valuable category of change and the least discussed, because “your site got slightly faster while you were asleep” makes a poor headline.
Auto-updates
You can set individual plugins and themes to update themselves, and you probably should for most of them.
The objection is that an update might break something. True. The counter-objection is that the alternative is running outdated code, which is how the overwhelming majority of WordPress sites get compromised. Outdated plugins are the single most common entry point.
A sensible middle: auto-update everything except the two or three plugins doing something structural, and take a backup before touching those manually.
What to actually do with a new release
- Back up first. Always. This is not optional and it is the step people skip.
- Update on staging if you have one. If you do not, update at a quiet hour rather than on Friday afternoon.
- Update plugins before or after core, not during. Halfway is where the strange errors live.
- Check the site afterwards. Homepage, a blog post, a page with a form, and submit that form. Two minutes.
- Do not chase a feature you will not use. A release that changes nothing for you is a release that changed nothing for you.
A note on staying current
The security argument for updating is strong and boring, which is why it gets ignored. Known vulnerabilities in old plugin versions are published, and automated tools scan for them at scale. The attack is not aimed at you; you are simply running a version that appears on a list.
Keeping current is unglamorous and it prevents most of what actually goes wrong with WordPress sites.
Frequently asked questions
Should I update WordPress as soon as a new version is released?
Security releases, yes, immediately. Major feature releases can reasonably wait a week or two while any significant issues surface, provided you are not skipping security patches in the meantime. Always back up first.
What is Full Site Editing in WordPress?
It lets you edit site-wide areas such as the header, footer and templates using the block editor, rather than editing theme files. It requires a block theme; sites on classic themes will not see it and do not need to switch.
Is the block editor better than the classic editor?
For most new sites, yes. It produces clean, portable markup and ongoing development is focused there. The classic editor remains a reasonable choice for existing sites and heavy shortcode workflows, but it receives progressively less attention with each release.
Will updating WordPress break my site?
Occasionally, and usually because of an outdated theme or plugin rather than core itself. Back up first, update at a quiet time, and check a few key pages afterwards. The risk of updating is consistently smaller than the risk of not updating.
Should I turn on automatic updates?
For most plugins and themes, yes. Outdated plugins are the most common way WordPress sites get compromised. Leave auto-updates off only for the few plugins doing something structural, and update those manually after a backup.
