Every new WordPress release is an opportunity to rethink priorities and (re)discover what could be missing in the WordPress core. While version 4.3 is being prepared, I came up with a list of five main Core features I would like WordPress to have, before it reaches version 5.0. Some might call this bloat, but I […]
Five WordPress Features Wanted Before Version 5.0 originates from Goce Mitevski
WordPress 5.0 graphic by Goce Mitevski (CC BY-NC 3.0)
Every new WordPress release is an opportunity to rethink priorities and (re)discover what could be missing in the WordPress core. While version 4.3 is being prepared, I came up with a list of five main Core features I would like WordPress to have, before it reaches version 5.0.
Some might call this bloat, but I think it’s a necessity as WordPress grows further as a platform.
Post Type, Taxonomy, Custom Field Management ExtravaganzaWhy do we need to code, to create custom post types and custom taxonomies without plugins in WordPress? This should be a no-brainer. You sign in, go to Posts, select “Add New Post Type” or “Add New Taxonomy“, fill out a nicely designed form and review available options.
Drupal has this for ages – of course not implemented in the same way. However, the benefits are huge! Developers code less. Clients have more control. There is a single code-base for everything, baked right into Core.
Same goes for custom fields. Maybe it’s a good idea to consider integrating Advanced Custom Fields (ACF) in Core?
I imagine a separate section in the WordPress back-end called “Custom Fields” where you could define and manage existing custom fields. I really like the ACF User Experience. Works great!
This can later be taken to the next level by enabling all kinds of conditional relationships between post types, taxonomies and custom fields.
On/Off Switch for Core FeaturesWordPress should have a separate page in the back-end with a list of all Core features. From this page each of the Core features could be turned on and off.
If I’m developing a website with no comments and search, I should be able to go to this new page, mark “Comments” and “Search” and select Disable. Turning these features off would mean that the relevant PHP code – from the WordPress API – in any theme will be ignored and will not get executed, which will directly result in less database queries and, possibly, improved website performance.
I imagine this page looking like wp-admin/plugins.php.
If I’m right, the last time search in WordPress was updated, was 16 months ago. We got relevance-based search-results-ordering and it made a huge difference. Suddenly, Relevanssi was no longer needed for simple sites.
I would expect the following additional changes in the near future:
Because I cannot count how many times clients have requested this in WordPress, while being very disappointed when an incoming not-well-tested update for WordPress SEO by Yoast broke something on their website.
Here is what I think any WordPress website should get out of the box in terms of Search Engine Optimization and what I expect to see integrated in Core in the near future:
<head>Lets add a separate page in Dashboard with performance options. Call it “Performance“.
This page should provide options for:
Nothing new here. Many persistent cache plugins offer these options in their code, but the point is to have all of this in Core, created with the WordPress Coding Standards in mind, thoroughly tested and extendable.
Also, I imagine the Performance page including information about how well the website performs on the current server, with smart suggestions on what can be improved. Not sure if something like this is currently possible with WordPress though, but it definitely would be useful to have.
Think About ItMost WordPress websites use custom post types, custom taxonomies and custom fields to organize content; don’t need every Core feature out there; require additional development for decent search experience; benefit from SEO and work faster when cached.
Imagine how much time can be saved if we have all this included in WordPress and manageable immediately after installation. No different code-bases to debug, less security issues, much more satisfied clients and a much more powerful Content Management System.
Here’s to WordPress 5.0 and making all of this happen. Cheers!
| # | Наименование новости | Тональность | Информативность | Дата публикации |
|---|---|---|---|---|
| 1 | Socync – Automatic social media posting and scheduling | 0 | 8.1 | 12-08-2026 |
| 2 | How to enable pretty permalinks in WordPress under wp-env | 0 | 11.6 | 23-02-2023 |
| 3 | Reboot | 0 | 12.07 | 03-05-2026 |
| 4 | Revisiting WordPress smilies in a pure CSS way | 0 | 10.42 | 20-12-2014 |
| 5 | WordCamp Paris slides: Unit Tests for WordPress plugins | 0 | 5.68 | 26-01-2015 |
| 6 | Reply To: Using Create theme with Site Origin page plugins | 0 | 17.17 | 01-10-2026 |
| 7 | Introducing the Advanced Professional WordPress Developer Certification | 0 | 7.65 | 19-02-2026 |
| 8 | X-post: Introducing Ipsum, the new default theme | 0 | 10.2 | 16-09-2026 |
| 9 | Reply To: Change spacer height for mobile? | 0 | 18.14 | 01-10-2026 |