Since 2020, the implementation of an API to help with cookie consent and other privacy-related elements has been up in the air. Now, this open and pending issue is being revisited.
Remember that you can listen to this program from Pocket Casts, Spotify, and Apple Podcasts or subscribe to the feed directly.
Program transcript
Hello, Iâm Alicia Ireland, and youâre listening to WPpodcast, bringing the weekly news from the WordPress Community.
In this episode, youâll find the information from December 2nd to 8th, 2024.
The WP Consent API was announced as a tool to help websites manage user consents more efficiently, especially in the context of data protection law and the famous GDPR. But is it really the solution the community needs?
Although it was initially considered as a response to the privacy challenges faced by website owners, there are doubts about whether the WP Consent API actually offers anything new or if, on the contrary, it could create more complications, as in practice, the solution may not be as flexible as expected. Some argue that the specific needs of each website do not always fit into a one-size-fits-all approach to consent management, leading to a lack of customization in the user experience.
On the other hand, we cannot forget that privacy and consent are increasingly relevant issues on the web today. Users demand more transparency, and regulators are pushing for better practices. In this sense, if WordPress is going to integrate a consent API, it must be something that helps, simplifies, and, above all, does not hinder the flexibility that has always characterized WordPress.
After the release of WordPress 6.7, the retrospective moment has arrived, and the feedback form related to this release will be available until January 13.
The Developer Blog has released a post about Hybrid Themes, which combine the best features of classic themes and block themes.
These themes allow the inclusion of modern block theme features, such as visual template editing and global style control, without completely abandoning the use of PHP and traditional files of a classic theme.
The Playground team has proposed a Blueprint Block Editor, with the development of a visual block editor that simplifies the creation of configuration templates in WordPress Playground.
Blueprints require advanced knowledge of JSON, but now, with a new user interface, the aim is to simplify the process and make it more accessible.
The Design team continues to work on small changes such as making the primary option in the appearance menu less prominent, allowing the navigation menus (for example, the header menu) to be unsynchronized from other areas, and introducing a dark mode for Openverse.
The Training team has presented a proposal to improve user engagement in Learning Pathways courses by breaking them into shorter segments. Currently, the courses are long, and many users drop out before completing them.
By splitting the content into smaller units, the goal is to reduce learning fatigue and allow participants to progress at a more manageable pace, achieving more frequent feelings of accomplishment. This change could make courses more accessible and increase completion rates, as users would feel less overwhelmed and more motivated to finish the courses.
And finally, this podcast is distributed under a Creative Commons license as a derivative version of the podcast in Spanish; you can find all the links for more information, and the podcast in other languages, at WPpodcast .org.
Thanks for listening, and until the next episode!
Leave a Reply