It is currently in beta.
The era of page redirects, mandatory admin dashboards, and content "previews" is over. Today's content demands that we be able to edit content where it exists on a page, as it looks when it's live, without barriers. It demands that we shouldn't sacrifice SEO concerns for rich, asyncronous web interactions. It demands that the framework shouldn't require a learning curve.
An efficient framework doesn't need to sacrifice good architecture for extensibility or user experience, and vice-versa. Our time is too important to be mucking around with a framework's specific details. We should be creating new things instead. This is what nooline aims to achieve.
There is a core set of principles which guide how Nooline is built:
Nooline is built Isomorphically – that is to say, much of its code can execute both on in the browser and on the server. It follows patterns found in many MV* frameworks, and relies upon a core set of components with wide-spread community use. Under the hood, Nooline uses a simple, extensible stack: Express, Backbone, and RequireJS.
All hands are welcome! Head on over to the milestones and pick something that interests you. Or submit a pull request for an idea you have!
Getting nooline running on your system is super easy. You'll need the following things already installed on your system:
Once you have those things up and running, head on over to the wiki for the rest of the details!