Current draft: https://docs.google.com/document/d/1v2PlXt8aGRm5dvhLDvRrcYySCadC3_e0Vc5OLQtzX3Y/edit?usp=sharing There are a lot of differences between Emulsify and Compony. | Compony | Emulsify | | ------ | ------ | | Everything is a component | Structure is altered to allow pattern-lab to work | | Component-based doesn't promote spriting | Spriting is supported | | No auto accessiblity testing | Automatic accessiblity testing | | No testing on speed | google pagespeed integrated testing | | No pattern-lab yet | Automatic public github page showcasing your pattern lab result | | A growing set of component-ecosystem to download from | Limited set of emulsify components | | The end page only loads the CSS that is needed on any given page | every page downloads all css on every page, as everything is compiled in to a single style.css | | The end page only loads the JS that is needed on any given page | The end page only loads the JS that is needed on any given page | | Fluid spectrum of atoms > organisms | Strict structure of atomic design | | Developer experience: Only defining more libraries and attaching more libraries | Defining pattern-lab variables, including + embedding .twig files, a bit hacky built on top of everything... | | Theme stands completely on it's own | You need to download a drupal module in order for this to work | | Heavily modified Gulp-setup for Drupal-theming | not-custom to drupal-theming | Maybe conceptually the idea of Pattern Lab inside Drupal theming is wrong? We are working inside a CMS, which means that our entire site works as a styleguide if you create one page where you list every component on?