Chris D. Macrae

Another thought -- should we rename *templates* to _**generators**_? For all intents and purposes, all templates should be a "generator". Even if it's a project using react, react-router and renderToString()...

@ncphillips Nope! Eslint and stylelint don't effect the gulp build at all

I totally agree with all of this. The only configuration I'd be interested in seeing is SSG commands; skinning things down to just a: - `start/server` command - `build` command...

To clarify, the `args` object should be powered via environment variables, which we could expose much [like CRA does](https://github.com/facebook/create-react-app/blob/master/packages/react-scripts/template/README.md#advanced-configuration). I could see a user being able to add additional package...

@ncphillips Let's MVP the shit out of this. Use the `docs/` folder on GitHub, and down the road that can just be used to generate a valid Jekyll site.

Not even HTML pages @ncphillips, just markdown files that can later be turned into a website. See `front-matter-manipulators` docs: https://github.com/chrisdmacrae/front-matter-manipulator/tree/master/docs

We likely wouldn't be using a custom domain -- at least not for a while, so I think this will suffice for the time being

I think this is a perfect example of a "fork" of `static-scripts`, i.e, `create-static-site-tailwindjs`

@ncphillips Here's an example of Tailwinds with CRA: https://medium.com/@mikeeeeeeey/create-react-app-tailwind-css-feat-postcss-631d9e33ba8c But in reality, you'll want it as part of your PostCSS plugins, so that's a separate instance of C-S-S.

@budparr Sort of. I've been doing this in some internal projects w/ some government projects, and I prefer it to using Webpack for PostCSS because you don't have to require...