Drupal 8 has been around for a while now and we've moved off the island. For most dev's they are well into the learning curve and more reusable project structure ideas are showing up. As a medium sized business how do we keep this momentum going and maximise it's ROI.
After 2 years of active D8 development, I will discuss what we have noticed, built and thrown away along the way.
A talk about architectural ideas (and pitfalls) about the horizontal (between different projects) and vertical (within the life time of a single project).
Provides in depth info about certain steps we took, the underlying concept and idea, encountered issues, key take aways etc.
Includes (but not restricted to)
Conceptual side
- What to document and how
- Hierarchy in automation, how to pick your battles
- Structuring (project) architecture cycles to be both ad hoc and structural
- Macro project single source of truth
- Business values vs dev values
- Useful abstraction vs One of solutions
- Momentum management
Practical side
- Automating documentation,
- Automating project setups,
- Keeping everyone out of date,
- Setting up an abstraction layer / layered logic
- Running deploys in various settings
- Regressions ROI