search

netzstrategen / bacon

netzstrategen baseline CSS library.
2 stars 0 forks source link

Make Bacon more library-like #7

Closed colourgarden closed 7 years ago

colourgarden commented 7 years ago

Ultimately, Bacon should be used as a library via npm. For this reason, we should move the docs into a separate folder (or possibly a separate repo) and also remove the gulp build process entirely. bacon.scss should sit in the root so the main value in package.json references just the file name (no sub-folders).

Edit: Move the docs into a sub-folder, separate into markdown files and build with Jekyll.

fabianmarz commented 7 years ago

If the gulp build process is removed entirely, how is the library build then? By the parent project?

colourgarden commented 7 years ago

Correct. Each project should have it's own gulp build process anyway (to handle whatever that project needs). We can keep a gulpfile in Bacon to build the base library and generate the docs or something but Bacon should be included as a library and then built upon.

So in NEPO we would have:

// nepo-theme.scss

@import '../../node_modules/netzstrategen/bacon/bacon';

@import 'assets/scss/components/atoms/xxx';
colourgarden commented 7 years ago

Completed with #10.