We Can't Have This New Feature in WordPress?!  [[3. Resources/Readwise/Full Document Contents/Articles/We Can't Have This New Feature in WordPress!|Full Document Contents]] ## Document Notes # Title: We Can't Have This New Feature in WordPress?! ## Table of Contents: - [[#📝 Summary:]] - [[#📖 Main Content:]] - [[#🗒️ Notes:]] - [[#📖 References:]] - [[#🗣️ Paraphrase:]] - [[#📰 Newsletter:]] - [[#✅ Action Items:]] - [[#🧪 Hypotheses:]] - [[#❓ Questions:]] - [[#🔮 Future Research:]] - [[#🧠 Learning Styles Assessment:]] - [[#📊 Accessibility Assessment:]] - [[#🌍 DEIB (Diversity, Equity, Inclusion, and Belonging) Assessment:]] - [[#✅ Logical Validity:]] - [[#🔍 SEO Evaluation]] - [[#🎯 Conclusion]] ## 📝 Summary: This video discusses a new feature introduced by the WordPress.com team, referred to as "Create Content Model." It allows users to build custom post types and dynamic fields using the block editor. Despite positive reception and high user engagement, confusion arose as to whether this feature would be implemented in WordPress.org core. The video critiques the disconnect between the announcement and the lack of plans for its inclusion in core WordPress. ## 📖 Main Content: The feature demonstrated by WordPress.com was an experimental tool that brought together custom fields and post types directly into the block editor. The feature aimed to make WordPress more accessible to users who may not have development expertise but still need dynamic data integration. This could be revolutionary for non-technical users, but the excitement was marred by the realization that the feature might not be introduced to WordPress.org. The video also addresses the implications of separating commercial and open-source development efforts in WordPress and questions the clarity of communication between these two branches. ### 🗒️ Notes: - **Feature Overview**: WordPress.com showcased a new "Create Content Model" feature that integrates custom fields and post types into the block editor. - The feature was met with high engagement and excitement across the community. - The feature was developed quickly, but the WordPress.org team clarified that it was only an experiment. - **Community Reaction**: - Positive feedback from developers and non-technical users alike. - Frustration emerged when it was announced that the feature might not make its way into WordPress.org core. - **Communication Issues**: - Lack of clear messaging about whether the feature was a permanent addition. - The discrepancy between WordPress.com and WordPress.org features causes confusion. ## 📖 References: - Merlin’s YouTube Channel: [We can't have this new feature in WordPress?!](https://www.youtube.com/watch?v=YZ9t5VvkhmM) ## 🗣️ Paraphrase: 1. Merlin explains that the "Create Content Model" feature had high potential due to its simplicity in integrating dynamic data through custom fields and post types without the need for complex development. 2. Despite the buzz and excitement, the announcement that the feature may not be available in WordPress.org left many feeling disappointed, leading to questions about the future of WordPress development and its different approaches for .com and .org. ## 📰 Newsletter: In a recent video, WordPress.com introduced a new feature called "Create Content Model" that simplifies custom post types and dynamic fields within the block editor. While the community responded enthusiastically, questions arose regarding the feature's availability in WordPress.org. This leads to a broader discussion about the divergence between WordPress.com and WordPress.org and what it means for users of both platforms. Tune in to the full discussion [here](https://www.youtube.com/watch?v=YZ9t5VvkhmM). ## ✅ Action Items: - Investigate whether this feature will eventually be available in WordPress.org core. - Consider how WordPress.com can better communicate with the WordPress.org community to avoid confusion over feature releases. - Keep an eye on future announcements and potential developments from WordPress.com regarding this and similar features. ## 🧪 Hypotheses: - If WordPress.org users were given access to "Create Content Model," the adoption rate of dynamic custom fields and post types would increase among non-developers. - Miscommunication between WordPress.com and WordPress.org regarding feature availability reduces overall user trust and engagement. ### 📊 Methodology: - **Survey**: Conduct surveys across WordPress.com and WordPress.org users to measure interest in the feature and perceived clarity of communication. - **User Testing**: Run A/B testing on different communication approaches for new feature rollouts between WordPress.com and WordPress.org. ### ❓ Questions: - How can WordPress better synchronize feature announcements across its platforms to minimize confusion? - Will there be a growing divide between WordPress.com and WordPress.org in terms of features and user experience? ### 🔮 Future Research: - Explore the possibility of a more unified communication approach for WordPress.com and WordPress.org features. - Investigate how separating WordPress.com’s commercial offerings from WordPress.org’s open-source platform impacts the developer and user communities. ### 💡 Implications: Unified communication could streamline the development process, increase transparency, and strengthen community trust across both platforms. Future research may lead to new models for how open-source and commercial branches of WordPress interact and evolve. ### 🧠 Learning Styles Assessment: 1. **Visual Learners (Spatial)**: - **Present**: The video format offers visual demonstrations of the feature in action. - **Improve**: Provide step-by-step visual guides, screenshots, or infographics for more clarity. 2. **Aural Learners (Auditory-Musical)**: - **Present**: The video content is ideal for auditory learners, offering detailed explanations. - **Improve**: Add an audio version of the transcript for those who prefer to listen rather than watch. 3. **Verbal Learners (Linguistic)**: - **Present**: The language is direct and descriptive, explaining technical concepts clearly. - **Improve**: Add accompanying articles or blog posts to expand on the video content. 4. **Physical Learners (Kinesthetic)**: - **Improve**: Suggest hands-on experiments with WordPress Playground to engage kinesthetic learners. 5. **Logical Learners (Mathematical)**: - **Present**: The video presents a clear logical progression of ideas, from feature introduction to community reaction. - **Improve**: Include data-driven comparisons between WordPress.com and WordPress.org user experiences. 6. **Social Learners (Interpersonal)**: - **Improve**: Encourage group discussions through live community chats or social forums to foster deeper learning. 7. **Solitary Learners (Intrapersonal)**: - **Improve**: Provide personal reflection prompts or individual exercises related to WordPress customization. 8. **Naturalistic Learners**: - **Improve**: Make real-world analogies to how dynamic content in WordPress could reflect natural processes or environmental data. ### 📊 Accessibility Assessment: - **Screen Reader Compatibility**: Ensure all videos come with closed captions and a fully accessible transcript. - **Improve**: Add alt-text to accompanying images in the video descriptions. - **Keyboard Navigation**: Ensure all interactive elements in the accompanying article are keyboard navigable. - **Contrast and Readability**: Test video overlays and ensure color contrast meets accessibility standards. ### 🌍 DEIB (Diversity, Equity, Inclusion, and Belonging) Assessment: - **Cultural Relevance**: Ensure the discussion includes use cases from non-Western perspectives and a diverse range of industries. - **Inclusive Language**: Use gender-neutral terms and avoid exclusionary language. Ensure technical jargon is explained for non-native speakers. - **Neurodiversity Support**: Break down complex explanations with bullet points, headers, and visual aids to support neurodiverse audiences. ### ✅ Logical Validity: - **Sound Deductive Reasoning**: The argum > [!note]+ Document Notes > > # Title: We Can't Have This New Feature in WordPress?! > <!-- deep-read:sections start --> ## Table of Contents: 1. [📝 Summary](#📝-summary) 2. [📖 Main Content](#📖-main-content) 3. [🗒️ Notes](#🗒️-notes) 4. [📖 References](#📖-references) 5. [🗣️ Paraphrase](#🗣️-paraphrase) 6. [📰 Newsletter](#📰-newsletter) 7. [✅ Action Items](#✅-action-items) 8. [🧪 Hypotheses](#🧪-hypotheses) 9. [❓ Questions](#❓-questions) 10. [🔮 Future Research](#🔮-future-research) 11. [🧠 Learning Styles Assessment](#🧠-learning-styles-assessment) 12. [📊 Accessibility Assessment](#📊-accessibility-assessment) 13. [🌍 DEIB Assessment](#🌍-deib-assessment) 14. [✅ Logical Validity](#✅-logical-validity) 15. [🔍 SEO Evaluation](#🔍-seo-evaluation) 16. [🎯 Conclusion](#🎯-conclusion) ## 📝 Summary: This video discusses a new feature introduced by the WordPress.com team, referred to as "Create Content Model." It allows users to build custom post types and dynamic fields using the block editor. Despite positive reception and high user engagement, confusion arose as to whether this feature would be implemented in WordPress.org core. The video critiques the disconnect between the announcement and the lack of plans for its inclusion in core WordPress. ## 📖 Main Content: The feature demonstrated by WordPress.com was an experimental tool that brought together custom fields and post types directly into the block editor. The feature aimed to make WordPress more accessible to users who may not have development expertise but still need dynamic data integration. This could be revolutionary for non-technical users, but the excitement was marred by the realization that the feature might not be introduced to WordPress.org. The video also addresses the implications of separating commercial and open-source development efforts in WordPress and questions the clarity of communication between these two branches. ### 🗒️ Notes: - **Feature Overview**: WordPress.com showcased a new "Create Content Model" feature that integrates custom fields and post types into the block editor. - The feature was met with high engagement and excitement across the community. - The feature was developed quickly, but the WordPress.org team clarified that it was only an experiment. - **Community Reaction**: - Positive feedback from developers and non-technical users alike. - Frustration emerged when it was announced that the feature might not make its way into WordPress.org core. - **Communication Issues**: - Lack of clear messaging about whether the feature was a permanent addition. - The discrepancy between WordPress.com and WordPress.org features causes confusion. ## 📖 References: - Merlin’s YouTube Channel: [We can't have this new feature in WordPress?!](https://www.youtube.com/watch?v=YZ9t5VvkhmM) ## 🗣️ Paraphrase: 1. Merlin explains that the "Create Content Model" feature had high potential due to its simplicity in integrating dynamic data through custom fields and post types without the need for complex development. 2. Despite the buzz and excitement, the announcement that the feature may not be available in WordPress.org left many feeling disappointed, leading to questions about the future of WordPress development and its different approaches for .com and .org. ## 📰 Newsletter: In a recent video, WordPress.com introduced a new feature called "Create Content Model" that simplifies custom post types and dynamic fields within the block editor. While the community responded enthusiastically, questions arose regarding the feature's availability in WordPress.org. This leads to a broader discussion about the divergence between WordPress.com and WordPress.org and what it means for users of both platforms. Tune in to the full discussion [here](https://www.youtube.com/watch?v=YZ9t5VvkhmM). ## ✅ Action Items: - Investigate whether this feature will eventually be available in WordPress.org core. - Consider how WordPress.com can better communicate with the WordPress.org community to avoid confusion over feature releases. - Keep an eye on future announcements and potential developments from WordPress.com regarding this and similar features. ## 🧪 Hypotheses: - If WordPress.org users were given access to "Create Content Model," the adoption rate of dynamic custom fields and post types would increase among non-developers. - Miscommunication between WordPress.com and WordPress.org regarding feature availability reduces overall user trust and engagement. ### 📊 Methodology: - **Survey**: Conduct surveys across WordPress.com and WordPress.org users to measure interest in the feature and perceived clarity of communication. - **User Testing**: Run A/B testing on different communication approaches for new feature rollouts between WordPress.com and WordPress.org. ### ❓ Questions: - How can WordPress better synchronize feature announcements across its platforms to minimize confusion? - Will there be a growing divide between WordPress.com and WordPress.org in terms of features and user experience? ### 🔮 Future Research: - Explore the possibility of a more unified communication approach for WordPress.com and WordPress.org features. - Investigate how separating WordPress.com’s commercial offerings from WordPress.org’s open-source platform impacts the developer and user communities. ### 💡 Implications: Unified communication could streamline the development process, increase transparency, and strengthen community trust across both platforms. Future research may lead to new models for how open-source and commercial branches of WordPress interact and evolve. ### 🧠 Learning Styles Assessment: 1. **Visual Learners (Spatial)**: - **Present**: The video format offers visual demonstrations of the feature in action. - **Improve**: Provide step-by-step visual guides, screenshots, or infographics for more clarity. 2. **Aural Learners (Auditory-Musical)**: - **Present**: The video content is ideal for auditory learners, offering detailed explanations. - **Improve**: Add an audio version of the transcript for those who prefer to listen rather than watch. 3. **Verbal Learners (Linguistic)**: - **Present**: The language is direct and descriptive, explaining technical concepts clearly. - **Improve**: Add accompanying articles or blog posts to expand on the video content. 4. **Physical Learners (Kinesthetic)**: - **Improve**: Suggest hands-on experiments with WordPress Playground to engage kinesthetic learners. 5. **Logical Learners (Mathematical)**: - **Present**: The video presents a clear logical progression of ideas, from feature introduction to community reaction. - **Improve**: Include data-driven comparisons between WordPress.com and WordPress.org user experiences. 6. **Social Learners (Interpersonal)**: - **Improve**: Encourage group discussions through live community chats or social forums to foster deeper learning. 7. **Solitary Learners (Intrapersonal)**: - **Improve**: Provide personal reflection prompts or individual exercises related to WordPress customization. 8. **Naturalistic Learners**: - **Improve**: Make real-world analogies to how dynamic content in WordPress could reflect natural processes or environmental data. ### 📊 Accessibility Assessment: - **Screen Reader Compatibility**: Ensure all videos come with closed captions and a fully accessible transcript. - **Improve**: Add alt-text to accompanying images in the video descriptions. - **Keyboard Navigation**: Ensure all interactive elements in the accompanying article are keyboard navigable. - **Contrast and Readability**: Test video overlays and ensure color contrast meets accessibility standards. ### 🌍 DEIB (Diversity, Equity, Inclusion, and Belonging) Assessment: - **Cultural Relevance**: Ensure the discussion includes use cases from non-Western perspectives and a diverse range of industries. - **Inclusive Language**: Use gender-neutral terms and avoid exclusionary language. Ensure technical jargon is explained for non-native speakers. - **Neurodiversity Support**: Break down complex explanations with bullet points, headers, and visual aids to support neurodiverse audiences. ### ✅ Logical Validity: - **Sound Deductive Reasoning**: The argument that the new WordPress.com feature could improve user accessibility is logically sound and based on clear evidence of its impact. - **Causal Reasoning**: Merlin uses cause-and-effect reasoning to explain how the feature's introduction led to community excitement and subsequent confusion over its availability. ### 🔍 SEO Evaluation: 1. **Keywords**: - The article effectively uses target keywords like “WordPress,” “custom post types,” and “block editor.” 2. **Meta Description**: - A clear meta description summarizing the article would improve SEO. 3. **Title Tag**: - Ensure the title tag is optimized with primary keywords and is concise. ## 🎯 Conclusion: This WordPress.com feature has opened up exciting possibilities for users but has also highlighted the need for clearer communication between WordPress.com and WordPress.org. The "Create Content Model" feature could drastically improve accessibility for non-developers, but without proper implementation into WordPress.org core, it risks being a missed opportunity. Short Summary for [We can't have this new feature in WordPress?!](https://www.youtube.com/watch?v=YZ9t5VvkhmM) by [Merlin](https://merlin.foyer.work/) WordPress New Feature Controversy Explained [00:06](https://www.youtube.com/watch?v=YZ9t5VvkhmM&t=6) The future of WordPress and the controversy around the custom content model. [02:08](https://www.youtube.com/watch?v=YZ9t5VvkhmM&t=128) Positive feedback on evolving feature in WordPress [06:21](https://www.youtube.com/watch?v=YZ9t5VvkhmM&t=381) Addressing the lack of clarity in understanding features in WordPress. [08:13](https://www.youtube.com/watch?v=YZ9t5VvkhmM&t=493) WordPress.com feature integration into open-source WordPress platform [11:40](https://www.youtube.com/watch?v=YZ9t5VvkhmM&t=700) Concerns about the decision-making process in WordPress [13:35](https://www.youtube.com/watch?v=YZ9t5VvkhmM&t=815) WordPress Studio for local development was viewed positively with 230 likes, but recent developments have caused disappointment. [17:25](https://www.youtube.com/watch?v=YZ9t5VvkhmM&t=1045) Confusion caused by unclarity in communication strategy [18:56](https://www.youtube.com/watch?v=YZ9t5VvkhmM&t=1136) Confusion around new WordPress feature [22:48](https://www.youtube.com/watch?v=YZ9t5VvkhmM&t=1368) Wordpress.com is introducing a new create content model prototype for defining custom post types and fields. [24:36](https://www.youtube.com/watch?v=YZ9t5VvkhmM&t=1476) The need for clear communication on prototype features [27:54](https://www.youtube.com/watch?v=YZ9t5VvkhmM&t=1674) WordPress should focus on becoming profitable and emphasizing its superiority in the market [29:48](https://www.youtube.com/watch?v=YZ9t5VvkhmM&t=1788) Comparison between Expression Engine and WordPress [33:42](https://www.youtube.com/watch?v=YZ9t5VvkhmM&t=2022) Ease of access is vital to encourage user engagement. [35:32](https://www.youtube.com/watch?v=YZ9t5VvkhmM&t=2132) Future of developing WordPress natively and integration with different hosting options. [39:22](https://www.youtube.com/watch?v=YZ9t5VvkhmM&t=2362) Discussion on leveraging APIs and framework in WordPress development [41:03](https://www.youtube.com/watch?v=YZ9t5VvkhmM&t=2463) Lack of clarity and confusion in communication. --------------------------------- Detailed Summary for [We can't have this new feature in WordPress?!](https://www.youtube.com/watch?v=YZ9t5VvkhmM) by [Merlin](https://merlin.foyer.work/) WordPress New Feature Controversy Explained [00:06](https://www.youtube.com/watch?v=YZ9t5VvkhmM&t=6) The future of WordPress and the controversy around the custom content model. - The custom content model called create content model showcased by the wordpress.com team involves custom fields, custom post types, and the block editor. - There is excitement around the new feature but also controversy regarding whether it aligns with the overall direction of WordPress. [02:08](https://www.youtube.com/watch?v=YZ9t5VvkhmM&t=128) Positive feedback on evolving feature in WordPress - Appreciates the direction and concept of the new feature - Suggests potential improvements in UX/UI for future iterations [06:21](https://www.youtube.com/watch?v=YZ9t5VvkhmM&t=381) Addressing the lack of clarity in understanding features in WordPress. - Discusses the confusion surrounding UX and how different user groups perceive and use the features in WordPress. - The prototype of the new feature was not polished and needs further development. [08:13](https://www.youtube.com/watch?v=YZ9t5VvkhmM&t=493) WordPress.com feature integration into open-source WordPress platform - Discussion on the transition of features from commercialized WordPress.com to open-source WordPress platform. - Positive engagement and reception towards the new feature despite differing user audiences. [11:40](https://www.youtube.com/watch?v=YZ9t5VvkhmM&t=700) Concerns about the decision-making process in WordPress - Discussion about Daniel Bach Huber's expertise and contributions to WordPress - Reflection on the success of the YouTube project related to WordPress [13:35](https://www.youtube.com/watch?v=YZ9t5VvkhmM&t=815) WordPress Studio for local development was viewed positively with 230 likes, but recent developments have caused disappointment. - The WordPress community had a positive sentiment towards the new feature and was excited to see it implemented. - The recent change in direction with the feature is seen as a fumble and has caused disappointment among the community. [17:25](https://www.youtube.com/watch?v=YZ9t5VvkhmM&t=1045) Confusion caused by unclarity in communication strategy - Emphasizing on releasing without clear explanation or communication plan - Suggesting potential confusion between different user bases in making communication decisions [18:56](https://www.youtube.com/watch?v=YZ9t5VvkhmM&t=1136) Confusion around new WordPress feature - Discussion about challenges between wordpress.com and wordpress.org - Concerns about code contribution and bypassing [22:48](https://www.youtube.com/watch?v=YZ9t5VvkhmM&t=1368) Wordpress.com is introducing a new create content model prototype for defining custom post types and fields. - WordPress.com is hoping the prototype will spark productive conversations within the core community. - The new content model is part of Wordpress.com's strategy to offer a different experience, potentially one you have to pay for, in order to survive. [24:36](https://www.youtube.com/watch?v=YZ9t5VvkhmM&t=1476) The need for clear communication on prototype features - Emphasizing the importance of clearly stating if a feature is just a prototype and not planned for release - Consideration of the impact of commercialized product versus .org and the need to support open source platforms [27:54](https://www.youtube.com/watch?v=YZ9t5VvkhmM&t=1674) WordPress should focus on becoming profitable and emphasizing its superiority in the market - WordPress can leverage its massive market share on the modern web to attract users by offering a 20% better experience - Implementing a slow rollout of features could help enhance user experience and maintain user engagement [29:48](https://www.youtube.com/watch?v=YZ9t5VvkhmM&t=1788) Comparison between Expression Engine and WordPress - Expression Engine is a smaller open source project with paid versions offering cool features - Ann McCarthy sharing insights on data views and customizations in WordPress with challenges [33:42](https://www.youtube.com/watch?v=YZ9t5VvkhmM&t=2022) Ease of access is vital to encourage user engagement. - Providing clear and accessible buttons in the GitHub repo facilitates experimentation and feedback. - The competition between Playground and Studio raises questions about native app experiences and user preference. [35:32](https://www.youtube.com/watch?v=YZ9t5VvkhmM&t=2132) Future of developing WordPress natively and integration with different hosting options. - Exploring the possibility of integrating with any hosting account through Studio or playground. - Considering revenue models and potential advertisements in the Studio app. [39:22](https://www.youtube.com/watch?v=YZ9t5VvkhmM&t=2362) Discussion on leveraging APIs and framework in WordPress development - Exploring the use of fields API and REST API for development - Concerns regarding slow progress on UX side and decision-making process for new features [41:03](https://www.youtube.com/watch?v=YZ9t5VvkhmM&t=2463) Lack of clarity and confusion in communication. - Language and follow-up news around the new feature were confusing. - Hopes that WordPress will address and clarify the situation for users. <!-- deep-read:sections end --> ## Highlights - Hit the Twitter sphere I did a video on it uh let me pull up the old screen I said is this the future of Wordpress and it's custom let me pull up Daniel's tweet that's what I meant to do pull up Daniel's tweet is this the future of Wordpress this is um something that the wordpress.com showed off the wordpress.com team showed off it's called create content model I demoed it I showed it on the channel and I was like I can get behind this custom Fields custom post types in the block editor debatable if that's the canvas we need to use and I was like this is great for a person like me doesn't want to do like heavy development stuff doesn't want a big page builder around it I was like I can get behind this Simplicity of custom fields and dynamic data um before we start dissecting like the controversy around this what was your original reaction when you saw the way it worked as somebody who's heavily you know invested in let's say bricks and also a former Elementor user yeah um I mean I think I think it was Kevin there was a lot of engagement on on this and we'll get into all that sort of thing but like on the surface when I saw it I think it was yesterday right or it was very very recently um I want WordPress to succeed I want it to continue to progress and we talk about this stuff all the time I don't use Gutenberg as much as other people like I'm I'm in the bricks world still page builder world and everything so I'm like not super tied to the block editor and don't use it again as much as other people do with the block systems and everything but I saw this and I was like this is amazing ([View Highlight](https://read.readwise.io/read/01j7m7zqqytmmgazq2b678ttq2))