Component-Based Design is often discussed in Drupal community in the context of large, complex multisite projects. It always makes sense to divide the bigger complex structure into tiny manageable pieces so that the components are easy to re-use and minimize technical debt.

Not sure, why did not we think of this before? 

Since Interfaces are made up of smaller components. This means we can break the entire interface down into fundamental building blocks and work up from there. That’s the basic gist of atomic design.

We have been working on the same approach and made independent components in Drupal. It not only reduced the operational cost but also reduced the amount of repetitive work we had been doing. And then, it was all about plug and play from there on.

In our talk, We're going to cover the following topics:

• What are components?
• Identifying components
• Problem with Legacy code
• How did components help?
• Rolling out components to multiple sites
• Overriding Core components in Multisite

Takeaways from this talk:

• Understanding of Component Architecture
• Keeping it simple and try not to complicate.
• Deliver a swift hassle free MVP.