Where am I coming from?
After a year of exploring whether to Drupal or not to Drupal, my organization is adopting Drupal as part of their Digital Experience Platform (DXP). My career is intertwined with Drupal, both as a piece of software and as a member of its community. I can easily see myself continuing to focus on Drupal for the rest of my career.
Everyone at my organization knows that for over ten years, I have been invested in the growth and development of Drupal as well as the growth and success of my organization’s website – the two go hand in hand. As of the writing of this blog post, the organization has been, and is, committing additional projects and resources to Drupal, which means that more people now frequently ask me Drupal-related questions. Just the other day, I rattled off a quick list of what it takes to implement a Drupal website on a recent planning call.
What is required to implement a Drupal website/application?
Below is my list of the tasks required to build an enterprise Drupal website/application.
General
- Business requirements
- Quality assurance
- Accessibility review
- Migration strategy
Infrastructure
- Hosting
- Local development
- Source control
- Deployment (CI/CD)
- Monitoring and logging
- Automated testing
Architecture
- Information architecture
- Content architecture
- Content authoring
General Implementation
- Asset and media management
- Roles and permissions
- Workflows and moderation
- Search Engine Optimization (SEO)
- Configuration management
Decoupled…Read More