Lots of work in the community is happening around how to best design, define, theme, and author components in Drupal, and seemingly everyone has their open source/contrib solution to make at least one aspect of building a component system easier. The question is why? What problems are all of these solutions looking to overcome? Why is the community not consolidating on a common approach?
In this session, we'll establish the parts of an individual component and what a component system needs to be successful. From there we'll look at various component system architectures and try to identify common pain points to see if there are bigger problems we should be addressing as a community.
Kyle Einecker of Perficient
Kyle has been working with Drupal since 2014, doing everything from theming, module development, to full on project architecture. He is active in the Drupal community and submits modules, patches, speaks at conferences/camps, and is an "Acquia Triple Certified" developer. In his current role, he is a Senior Technical Architect for Perficient, a global digital consultancy.
When he's not working he can be found hiking one of the many trails around Asheville or trying out a new brewery.