Maintenance: Easier upgrade paths and maintenance procedures
Key Focus Areas for Drupal 11
Making site builder tools easier to use
Improving content editor tools
Making Drupal easier to upgrade and maintain
Current Status
Drupal 11 is under active development, with several features being tested and refined through Drupal 10's minor releases. Many of the planned features are being introduced incrementally through Drupal 10.x updates to ensure a smooth transition when Drupal 11 is released.
There was only screenshots provided however I could get a brief understanding.
Here is Gemini helping me make sense of my notes: Key Features & Improvements:
Streamlined Content Editing (Workspace): Empower content editors to easily create and publish new site sections. This includes a versioning system (A/B testing) allowing editors to create multiple versions of a section and choose the one to go live based on desired outcomes (e.g., different content based on event results). A more intuitive and descriptive user interface (UI) will further simplify the process.
Organized and Reusable Components (Single Directory Components): Improve code organization and reusability by grouping all related files and assets (Twig templates, YAML configuration, JavaScript, CSS, images, etc.) within a single directory for each component. This makes it easier to manage, understand, and reuse components across different pages and applications.
Granular Security and Compliance: Implement more flexible permission management beyond simple user roles. This includes the ability to assign and revoke permissions based on specific criteria, such as time of day (e.g., automatically revoke access on weekends).
Simplified Setup with Recipes (Coming Soon): Introduce a "Recipe" system, similar to an app store, to streamline the installation of related components. A recipe can bundle modules, themes, and configurations, enabling users to quickly set up new features or environments. This system will also support custom configuration actions.
Integrated Features (Blog, Privacy, SEO, AI, Analytics, Multilingual): These features will be seamlessly integrated into the new CMS, providing out-of-the-box functionality for content management, privacy compliance, search engine optimization, artificial intelligence integration, analytics tracking, and multilingual support.
Two CMS Options:
No-Code CMS: A new, user-friendly CMS that requires no developer intervention for content management and site updates.
Drupal Core (For Developers): For more complex projects or those requiring custom development, Drupal Core will continue to be supported. This offers developers the flexibility and power of Drupal.
Overall Benefit: These improvements will make the CMS easier to use, more secure, and more efficient, empowering both content editors and developers.
David
if you had to take a stab at how much work this is for GEMs in hours, what would that be - all the feature updates, etc what does that look like, more or less. I'd suggest we think about the time you think it might take per item including possible issues.
Things like streamlined content editing - do you think we'd need to replace any of the modules we have for GEMS now to replace it with the new?
We don't have a crystal ball but I can go back and say we think from X hours to Y hours taking the above upgrade factors into consideration and applying what is needed?
Rough guestimate from me knowing nothing - you checking all this stuff 10 hours, you applying what may be needed another 20 and then me doing a spot check on the visuals and you or X doing a good check another 10-20 so ball park 50 - 60 hours ( but this is not coming from a place of knowledge so what do you think )
Release Timeline
Additionally watched this video:
https://www.youtube.com/watch?v=JmhHzFU44dY
There was only screenshots provided however I could get a brief understanding.
Here is Gemini helping me make sense of my notes:
Key Features & Improvements:
Streamlined Content Editing (Workspace): Empower content editors to easily create and publish new site sections. This includes a versioning system (A/B testing) allowing editors to create multiple versions of a section and choose the one to go live based on desired outcomes (e.g., different content based on event results). A more intuitive and descriptive user interface (UI) will further simplify the process.
Organized and Reusable Components (Single Directory Components): Improve code organization and reusability by grouping all related files and assets (Twig templates, YAML configuration, JavaScript, CSS, images, etc.) within a single directory for each component. This makes it easier to manage, understand, and reuse components across different pages and applications.
Granular Security and Compliance: Implement more flexible permission management beyond simple user roles. This includes the ability to assign and revoke permissions based on specific criteria, such as time of day (e.g., automatically revoke access on weekends).
Simplified Setup with Recipes (Coming Soon): Introduce a "Recipe" system, similar to an app store, to streamline the installation of related components. A recipe can bundle modules, themes, and configurations, enabling users to quickly set up new features or environments. This system will also support custom configuration actions.
Integrated Features (Blog, Privacy, SEO, AI, Analytics, Multilingual): These features will be seamlessly integrated into the new CMS, providing out-of-the-box functionality for content management, privacy compliance, search engine optimization, artificial intelligence integration, analytics tracking, and multilingual support.
Two CMS Options:
Overall Benefit: These improvements will make the CMS easier to use, more secure, and more efficient, empowering both content editors and developers.
Screenshots from the video
Things like streamlined content editing - do you think we'd need to replace any of the modules we have for GEMS now to replace it with the new?
We don't have a crystal ball but I can go back and say we think from X hours to Y hours taking the above upgrade factors into consideration and applying what is needed?
Rough guestimate from me knowing nothing - you checking all this stuff 10 hours, you applying what may be needed another 20 and then me doing a spot check on the visuals and you or X doing a good check another 10-20 so ball park 50 - 60 hours ( but this is not coming from a place of knowledge so what do you think )
https://drupalize.me/tutorial/upgrade-drupal-11#:~:text=Use%20the%204.,via%20the%20Extend%20administrative%20page
Improved field management could be an issue
PHP - if it coincides, it might cause an issue
Dave to install 11 and see what happens