Teams eventually reach a point where their bespoke site approach becomes overwhelming. Website governance can allow your team to manage requests and portfolios more efficiently.
Drupal was a hobbyist framework for a long time. As popularity grew, agencies and small teams built practices using Drupal extensively to roll out increasing numbers of sites for customers. However, as a portfolio grows beyond 20 to 50 sites, issues and pain from a lack of governance framework can begin to set in. Developers start to feel underwater, code maintenance becomes unmanageable and customers can get frustrated by timelines and cost to add features. Artisanal handcrafted sites can no longer be sustained at this scale.
As Drupal continues to grow in the enterprise space, agencies and small teams will find themselves more and more immersed in this cacophony of demands. This session will help attendees develop a governance model to maintain their site portfolio with less effort.
Learning objectives for attendees
1. Define governance frameworks and their usefulness
2. Develop a governance model for their organization
3. Maintain their site portfolio with less effort
This is a joint talk with Raymond Wang -- https://www.drupal.org/u/flailingmaster