Dries Q&A
summary
A wide-ranging Q&A covers concrete moves: Adobe buys Magento and that drives vendor interest in Drupal commerce integrations; Acquia secures deeper-pocket investors and keeps independence while expanding capital; the project is building a telemetry initiative to measure which core features and admin flows are actually used so decisions can be data-driven; the credits program expands beyond code to reward docs, UX, events; Layout/Layer Builder moves toward whole-page editing and the team compares specific tradeoffs with Gutenberg.
AI-written summary · about
chapters (11)
- 0:00Intro
- 4:49How would you sell Drupal in comparison do Adobe Experience manager. Key selling points etc.
- 11:21A big portion of the current and proposed initiatives are focused on UX. How could we increase the size of our UX community to build more momentum there?
- 13:58What is the biggest roadblock right now? If you can't figure out any currently, how about historically?
- 17:39What kind of metrics do you think we should gather and how should we weigh contributions in the new Community Recognition Program?
- 21:41D&I is important to the growth of Drupal. Should it be an official initiative? Would that get more people in the room, more people invested?
- 26:08Drupal has been in the top for being the most dreaded web framework' according to the Stack Overflow surveys. What can we do about that?
- 28:33What are your thoughts on Gutenberg as an editor in terms of improving the experience for beginners to Drupal. How would it fit in with Layout Builder?
- 30:29Drupal in schools: is there a school or teacher using Drupal to teach Web creation to kids?
- 35:26How do you see your role, and Acquias role, changing in the community, with the new acquisition?
- 43:41Your keynote mentioned beginners. Will you formally challenge Drupal hosting companies and agencies to hire junior devs so that beginners have an entry point?
related talks
01h 09m"Driesnote"
53mA Survey of Emerging Technologies That Complement Drupal
52m"Decoupled Drupal: Implications, risks and changes from a business perspective"
43m"Drupal distributions panel"
46mAmbitious Editorial Experiences with Headless Drupal
16mOpening Session
23mAI-native CMS vs vibe coding
01h 01mThink Locally, Build Globally - How Drupal is powering headless omni-channel web platforms
