I suggest to re-use drupal core's themes at this point, and have the following:
for drupal's js files we can have themename/js folder.
1.1. In this folder we have only drupal's scripts, which are out of "storybook" scope.
1.2. Filenames are themename/js/some-script.es6.js
1.3. Compiled version lives here themename/js/some-script.js
for drupal's css files we can have themename/css folder.
2.1. Works same way as (1)
for source images (and svg sprite) we can use themename/images folder.
3.1. We can try to inline affected images from css -> to base64 format.
for source fonts we can use themename/fonts folder.
4.1. Probably we can try to use source fonts in compiled css somehow. Not copy fonts to dist folder and then use them, but instead use source fonts directly in compiled css.
So our src folder can be removed at all
Probably dist folder can be removed at all
Pattern's shit lives in templates/patterns as always.
Compiled assets of components - lives inside of components
I suggest to re-use drupal core's themes at this point, and have the following:
for drupal's js files we can have
themename/jsfolder. 1.1. In this folder we have only drupal's scripts, which are out of "storybook" scope. 1.2. Filenames arethemename/js/some-script.es6.js1.3. Compiled version lives herethemename/js/some-script.jsfor drupal's css files we can have
themename/cssfolder. 2.1. Works same way as (1)for source images (and svg sprite) we can use
themename/imagesfolder. 3.1. We can try to inline affected images from css -> to base64 format.for source fonts we can use
themename/fontsfolder. 4.1. Probably we can try to use source fonts in compiled css somehow. Not copy fonts to dist folder and then use them, but instead use source fonts directly in compiled css.So our
srcfolder can be removed at allProbably
distfolder can be removed at allPattern's shit lives in
templates/patternsas always.Compiled assets of components - lives inside of components