This is a refactoring of basically the whole shebang: the template directories for various configurations, and the generator code that tells Yeoman which files to copy under certain circumstances. Here's the gist:
The entire app/templates/jekylltemplate directory is now a git submodule pointing at the "template" repo. This means that the boilerplate (config and data files) lives in one place.
The generator now asks you whether you'd like to use Jekyll and Sass independently.
The Jekyll setup involves copying all of the files from the template repo, minus the .git submodule metadata directory.
If you pass --sass or answer Y to the Sass question, we copy over the contents of app/templates/jekyll-sass.
The non-Jekyll ("static") setup involves:
Copying over the entire dist directory from the npm installation to assets/uswds
If you pass --sass or answer Y to the Sass question, we copy the contents of app/templates/static-sass and extendpackage.json with the contents of package.ext.json.
There are now unit tests for most of these decisions that use the yeoman-test and yeoman-assert libs recommended in Yeoman's testing guide. You can run them with npm test, assuming you've also run npm install --dev beforehand.
This is a refactoring of basically the whole shebang: the template directories for various configurations, and the generator code that tells Yeoman which files to copy under certain circumstances. Here's the gist:
app/templates/jekyll
template directory is now a git submodule pointing at the "template" repo. This means that the boilerplate (config and data files) lives in one place..git
submodule metadata directory.--sass
or answer Y to the Sass question, we copy over the contents ofapp/templates/jekyll-sass
.dist
directory from the npm installation toassets/uswds
app/templates/static
directory--sass
or answer Y to the Sass question, we copy the contents ofapp/templates/static-sass
and extendpackage.json
with the contents ofpackage.ext.json
.There are now unit tests for most of these decisions that use the
yeoman-test
andyeoman-assert
libs recommended in Yeoman's testing guide. You can run them withnpm test
, assuming you've also runnpm install --dev
beforehand.