Why Use Ollie
Many of the patterns, practices, and libraries are useful in all of these contexts. That said, Ollie is a traditional web-oriented development environment.
Node is relied on for our build tooling and API, along with GitHub for source control.
Who isn't Ollie for
Maybe you're already working in a highly opinionated and comprehensive framework that provides a rich development environment baked-in.
Ember is an example of this. When you choose Ember, you're expected to use the Ember CLI, Ember's built-in tooling takes care of most of what Ollie does for you. See, Ember is comprehensive and notoriously opinionated. It already has opinions on file structure, testing, CLI, and much more.
Ember's like a religion, you accept it all or you won't fit in.
Of course, depending on the library or framework you're working with, there may already be a variety of starter kits or boilerplates available for you to use already.
What Ollie provides as a starter kit
Here's just a few items that should belong in all JS starter kits - and as such are already taken care of in Ollie,
- package management,
- dynamic HTML generation,
- centralized HTTP requests,
- a mock API framework,
- your component libraries,
- development webserver,
- automated testing,
- continuous integration,
- automated build and automated deployment.
- Solid documentation including a working example app to help convey how all these parts come together, including directory structure and file-naming practices.