With the WordPress 5.5 development cycle finished, it’s time to start mapping out which features are expected to be rolled out in WordPress 5.6 later this year. Today, Chloe Bringmann asked the community to get in touch with her wish list on the Make Core blog.
As usual, I have some thoughts. I tend to turn to some of the long-lasting developer tickets because these features allow plugin authors to create better products for end users in the long run.
A complete custom post status API at the top of my usual list of most wanted features. I have already discussed this for my WordPress 5.5 wish list. It could be the time for more realistic dreams. Maybe we’ll see him another year or two down the road. However, if any main clue wants to give the feature green light, I will be happy to be the evangelist and to excite others.
Selection of the type of post on the home page
For this version, I want to recall one of my other years’ wishes. WordPress should allow end users to select any type of personalized post for display on the homepage.
Imagine a WordPress where users can access the Reading Settings screen in the administrator and select something different from their normal list of posts or a page to display on the home page. Have you installed a forum plug-in? Maybe users want to list their latest topics or the forum list. Are you running an e-commerce plug-in? Users should be able to view their products. Set up a web design portfolio? View the most recent projects by simply selecting this choice in the administrator.
This is an area where the software has always turned to bloggers and avoided giving some love to other types of sites.
Currently, plugin authors have to run some crazy hacks for it to work. WooCommerce’s custom query class is enough to make any developer give up. Not all of the code in that file is for the first page, but it has a frustrating amount to make something work that should be much simpler for plugin authors.
The reason why this must be in the WordPress core is that every single plug-in doesn’t need to create a custom solution. Plugins should be able to mark their post types during registration as “allowed on the homepage” – not all post types are meant for this type of display. So WordPress should handle all the dirty work behind the scenes if the end user selects a particular type of post. Adding to the API for plug-in authors would be simple, and plug-ins that are already hacking this feature together can eliminate a lot of unnecessary code.
There is an existing 8-year ticket for the function. It has some old and probably obsolete patches and hasn’t seen any real activity in the past four years. However, it would be nice to see this function in the WordPress core and finally close the ticket.
Block system wish list
Like most versions, the block system will get maximum attention. The things that will arrive in WordPress 5.6 are mostly already set in stone, assuming that a particular feature is not lagging behind in development as the widgets and navigation menus did for version 5.5.
Overall, I like the general direction the block system was headed. If anything, I was impatient for some things, such as waiting for the lock management screen integrated in the administrator. For other features, like editing the whole site, I still wonder if they are realistic goals for the WordPress 5.6 version.
I would like to release and focus on strengthening and polishing the existing system. Take stock of the weaknesses – and there are many – that users are citing. Spend some time working to make the editing experience more fluid before trying new features.
Not gonna happen. New features are what gets developers up in the morning and excited about the project. Therefore, my fallback request is to display the block management screen.
What’s on your wish list?