Omaha Nebraska has a long history of quality — quality of beef, quality of life, etc...

This project hopes to extend that connection with quality, and start a trend of associating Omaha with quality of code.

..."omaha" is also a short namespace that was available from js.org

This project strives to help developers leverage core patterns common to multiple technologies in an effort to maximize flexibility and minimize churn.

Toward this end, we embrace incremental enhancement by maintaining control over build tools and leveraging sustainable technologies. This philosophy plays well with many options and will help any project stay ready to #usetheplatform

- If you choose to use AMD, modules will be scaffolded using CommonJS sugar syntax, and whether you choose to use Browserify or Webpack, modules will be imported using their Browserify-compliant names. Following these simple conventions enables flexibility and helps identify how technologies differ.

A scaffolded web app will have the same architecture with AMD or CommonJS, Jest or Mocha, Webpack or Browserify!

- Marionette can be read/understood in under 30 minutes and allows for customization (like swapping out renderers...we like to use morphdom)

We like to understand our production dependencies and practice patterns before plugins.

Yes. More specifically, this site was built with the awesome static site generator, GatsbyJS.

Beyond the fact that GatsbyJS is amazing, we wanted to highlight that developing solutions with front-end technoligies is not a zero-sum game with only one winner.

Component-based technologies like React have a time and place, but depending on your experience, requirements, and constraints, React might not be for you. Omaha is here to provide a viable and sustainable alternative, with an always-available path for incremental enhancement.