{"type":"rich","version":"1.0","provider_name":"Transistor","provider_url":"https://transistor.fm","author_name":"The WP Minute+","title":"WordPress says NO","html":"<iframe width=\"100%\" height=\"180\" frameborder=\"no\" scrolling=\"no\" seamless src=\"https://share.transistor.fm/e/cfd1fa41\"></iframe>","width":"100%","height":180,"duration":2596,"description":"In this episode of WP Minute+, I sat down with Mark Szymanski to discuss the recent buzz surrounding WordPress.com's \"content models\" experiment. \n\nThis feature, which briefly excited the WordPress community, promised to bring custom post types and fields to the core WordPress experience. However, the excitement was short-lived as Automattic announced that the feature wouldn't be coming to core WordPress after all.\n\nOne of the most intriguing parts of our discussion was the broader implications for WordPress.com and WordPress.org. We touched on the potential future of WordPress development, including the possibility of WordPress.com offering enhanced features as a way to differentiate itself and generate revenue. \n\nThis led to an interesting debate about the balance between open-source development and commercial interests in the WordPress ecosystem.\n\nThroughout the conversation, it became clear that this incident highlighted some of the ongoing challenges in WordPress development and communication. While we both expressed hope that the feature might still find its way into WordPress in some form, we agreed that clearer communication and expectation management are crucial for the platform's future.\n\nKey takeaways for WordPress professionals:\nPrototypes and experiments can generate significant community interest and should be communicated carefully.\nThe relationship between WordPress.com and WordPress.org continues to evolve and may lead to differentiated features.\nClear communication is crucial when showcasing potential new features to avoid confusion and disappointment.\nThe WordPress community is eager for improvements in custom post types and fields within the core experience.\nThe balance between open-source development and commercial interests remains a complex issue in the WordPress ecosystem.\nUser experience and ease of implementation are critical factors in the adoption of new WordPress features.\nThe future of WordPress development may involve more native...","thumbnail_url":"https://img.transistorcdn.com/Sc_eJunw7xigqxjwbAQZm4WVha2xRuUoFYgmWEEXnaU/rs:fill:0:0:1/w:400/h:400/q:60/mb:500000/aHR0cHM6Ly9pbWct/dXBsb2FkLXByb2R1/Y3Rpb24udHJhbnNp/c3Rvci5mbS9hODUy/NDIxOTQzZmFmNDk3/ZDk4ZGUzZTQ3NzA3/NTk5MC5wbmc.webp","thumbnail_width":300,"thumbnail_height":300}