Now that we are all used to using Composer to require and update any site, and automation to build sites on various platforms, where shall we put our custom work on the site? There are some who feel there should be a custom repository, with code which can be pulled in by composer, while others feel the custom work is part of the site. And what about components that can be shared between projects? In this discussion, we will look at development use cases for all of the above and discuss ways projects can share, reuse and work together. We will also discuss what Composer Installers are and how they work to ensure your code is added in the proper place.
About the Speaker
Mark Casias
Drupal Tech Lead at Kanopi
Albuquerque
AmyJune writes:
Hailing from Albuquerque New Mexico, Mark has been developing and maintaining Drupal sites for over 12 years, and is an active part of the community, adding core commits and a few of his own modules. works at Kanopi Studios as a Drupal Tech Lead, working to solve client problems and create the sites of their (Drupal) dreams.
Mark is an Acquia Certified Developer, and is highly skilled in Drupal, Gatsby / React, JavaScript, Sass / CSS. Outside of Drupal, he’s an active tennis and golf player, and rocks out on the bass in his band.
