Choosing the architecture
We shared our experience, proposing solutions which would be effective in the long term. It was important for the Bossa team to rely as much as possible on Drupal core features and create as little custom code as possible. On the other hand, however, they looked for solutions which would enable them to maintain well organized and easy to understand code.
One of the solutions we proposed is Layout Builder, which at the beginning of the project was still an experimental feature in Drupal, but now it's a fully supported official functionality. Thanks to this decision, the Bossa team did not have to develop any custom editorial mechanism but could rely on the features given by Drupal, saving a lot on development.
Pattern Lab and Multisite in Drupal
Another example of an architectural choice was making a decision on how to implement the Drupal theme in such a way that it would be maintainable over longer term. Additionally, one of the requirements was the ability to reuse the built elements in other websites which would be created by the team in the future.
We suggested and helped build a design system implementation based on a base theme and an end theme, built on Pattern Lab. Using Pattern Lab, we can successfully control the whole design system. Thanks to creating a base theme and child themes, we can easily add additional websites which will reuse a lot of the components, but will be able to maintain separate designs. Droptica implemented Pattern Lab and trained Bossa team in using it.
We also helped to create the correct mechanics of working in a multisite environment. Additional websites built on the system will take much less time to create. There will also be a single codebase to maintain instead of many separate ones.