ComponentType and Status are required in the component schema but it's not clear how these are used. I have a couple questions...
I've found component type categorization, like atomic design, adds unnecessary cognitive overhead when defining components. I often get asked whether or not something should be an Atom, Molecule or Organism. I've found it simpler to just accept that components are infinitely nestable and come in different sizes and levels of complexity. This is one of the things that makes component based JS frameworks fun to work with.
In any case, thanks so much for your work on this! I've personally had a lot of false starts trying to integrate a living style guide or pattern library with Drupal. This module and the Storybook integration address all those past issues. I'm very excited about these concepts potentially getting into core.
Fixed
1.0
Documentation
@pixelwhip you are right. I regret being opinionated on this prop. This prop has gone away in SDC (which is like CL Components v2), and will not be present if this makes its way into core.
Automatically closed - issue fixed for 2 weeks with no activity.