• NPM version (npm -v): 6.13.4
• Node version (node -v): v13.6.0
• Node Process (node -p process.versions):

{
  node: '13.6.0',
  v8: '7.9.317.25-node.26',
  uv: '1.34.0',
  zlib: '1.2.11',
  brotli: '1.0.7',
  ares: '1.15.0',
  modules: '79',
  nghttp2: '1.40.0',
  napi: '5',
  llhttp: '2.0.1',
  openssl: '1.1.1d',
  cldr: '35.1',
  icu: '64.2',
  tz: '2019a',
  u

Start thinking about what content we're trying to capture and how best to express it to users.

Proposal:

Homepage (landing / upsell)
├─┬ Getting Started
│ ├── Getting started / installing Eyeglass
│ ├── Why Eyeglass
│ ├── Options
│ └── How Eyeglass works
├─┬ Eyeglass Modules
│ ├── What is an Eyeglass module
│ ├─┬ Authoring an Eyeglass module
│ │ ├── Exporting Sass (mixins, variables, partial

Hello,

Here is the project structure:

-- app.scss
-- components
-- _partial_one.scss
--- module
---- _partial_two.scss 

Now in my app.scss:
@import components/*.scss - works properly : imports _partial_one.scss and watches for changes in the file
@import components/**/*.scss - imports _partial_two.scss but on changes in the file it compiles _partial_two.scss and doesn't r

It would be nice to script/automate the creation of the README.

There are two main parts of the current README:

• The example section, that shows example usage of the plugin. This example code is now part of examples/ in the source, and the script could just lift that code and write it to the README file since it's already going to be maintained as an example usage to quickly test the plugin.