Sitemap / IA

Nobody has claimed this yet.

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, partials, etc)
│ │ ├── Exporting custom Javascript functions
│ │ ├── Creating a new module with Yeoman generator
│ │ └── Converting an existing project to an Eyeglass module
│ └── Installing an Eyeglass module
├── Working with assets in Eyeglass
├─┬ Integration
│ ├── Pure node-sass
│ ├── With gulp.js
│ ├── With Grunt
│ ├── With Broccoli.js
│ └── With Ember CLI
├─┬ Troubleshooting
│ ├── Errors / warnings
│ ├── Debugging
│ └── Common issues
└── CHANGELOG
```

/cc @chriseppstein @xiwcx @una

Start with the proposed sitemap in the issue and compare its sections with the project's current documentation. Confirm which user journeys and content belong in the structure, then seek agreement on the information architecture. Done means the sitemap and resulting documentation sections have been approved.

Written by the indexing model from the issue text.