Prototype subset of components

[kwm14]

No description provided.

[lyubomir-popov]

My original idea was to keep a config file that asigns each component a default theme, and build using that theme, per component. The core challenge with this is that unlike less, scss lacks dynamic imports. The scss maintainers are planning to address that with a new modules system, but that seems to be going nowhere fast. According to them:

• if we don't plan to go beyond two themes for the foreseeable future, then wrapping imports in conditionals might work (not tested) almost like a dynamic import, e.g.:

@if($hr-default-theme == 'dark') { 
  @import 'hr-theme-dark'
}

• or, we can just do it manually, by importing theme files and including them, as with patterns. But would this mean that out of the box we import everything? That would increase file size.
  If we opt to provide the files, but not include them by default, then you might be used to using hr.is-dark on say ubuntu.com, but in snapcraft where they import things individually, it would fail until you discover you need to import separately.