Integrating a new paradigm that fundamentally impacts several aspects of the TYPO3 Core is always a meticulous process. The Core developers must ensure that the additional code becomes part of the system without compromising stability. Existing options to maintain and upgrade TYPO3 must also remain intact.
Kudos to the TYPO3 team for this impressive release. Content Blocks into the core is a game-changer, making content creation so much more flexible and future-proof.
Can you please make the image at " Backend User Permissions" zoomable?
The TYPO3 v13.3 release makes TYPO3 even more versatile and efficient. It’s awe-inspiring how the community continues to innovate and deliver updates that cater to the evolving needs of users.
Just refilled the cats’ food-bowls, I don’t find no dog though. Preparing for some TYPO3 upgrades to do.
#T3Kudos to the contributors for their dedication and efforts on TYPO3 v13!
IMHO, the cherry-pick strategy for EXT:content_blocks is a solid approach. However, it might be beneficial to include it in the TYPO3 core, similar to how other products and communities have made bold decisions (e.g., Gutenberg in WordPress). This would encourage people to take TYPO3 more seriously and build pages and content directly within the core. Hopefully, TYPO3 people will understand and start the project with content blocks for their next project.