Drupal’s entire existence is rooted in the fact that it is a collaboration of organizations and individuals, and that massive collaboration requires communication and relationships. Minimally, if an organization wants a secure website/application, it must connect with the Drupal community to be notified about security releases. Very few enterprise implementations of Drupal can be accomplished by a single, independent group. Websites and their digital experiences are too complex. Organizations frequently separate development from hosting. With decoupled implementations of Drupal, organizations are beginning to unravel the front-end from the backend.
The complexities and challenges of Drupal websites/applications are endless. Having good partners and hiring the right vendors can help strengthen an organization’s planning and process. For example, SaaS hosting providers specializing in Drupal can easily be responsible for most of an organization’s infrastructure-related tasks.
In my previous posts about good Drupal leadership, I discussed the challenges of planning, implementing, and resourcing. To help establish good Drupal leadership, organizations need to understand the type of relationships involved and what is required to strengthen these relationships.
Relationships types
Internal
Anyone not directly involved with Drupal will want to know, “What is Drupal?” An organization with an executive-level summary answering the “what” and…Read More
