It's not a framework or a library, but rather a set of rules and practices of how to do things. It will sounds somewhat weird, but I'll list them anyway. Maybe someone will find it useful:
- Overall mental model: libraries don't implement components, but rather change the behavior of certain elements on the page.
- No library keeps state in JavaScript variables. DOM is your model.
- All configuration is also done through DOM with liberal use of CSS selectors to reference things.
- No library has any direct dependencies on any other.
- Things that need to react to changes should (if at all possible) use timers. If that's not possible, they should register global event handlers, rather than attach them to individual components.
While this might horrify some people, it actually forced me to come up with rather nice, abstract behaviors that capture many common features I had to commonly implement. Also, this plays well with the notion of progressive enhancement. I recommend everyone to try it on some new web-based project of low to moderate complexity. Ir really does simplify a lot things.