DOMX
is an approach to building modern web applications using the DOM, browser,
and patterns morso than relying on frameworks or libraries.
Building a web application today is like building a Rube Goldberg machine. If this feels like your development experience then perhaps it is time to re-think and simplify.
DOCS
- Platform Evolution
- When the Platform is not Enough
- State Management
- Data Elements (on GitHub)
- Client Side Routing
Platform Evolution
Historically the web has seen a common pattern.
We start with proprietary home grown solutions. Some of those solutions may end up in a library that is shared by the community. And finally, the browser platform provides its own solution.
Read moreWhen the Platform is not Enough
Of course, there will always be a need for libraries. No one wants to build the 483rd date component by hand and if there is need for complicated animations the Web Animation API or Canvas may not cut it.
At the same time there may be ways to stay close to the platform without investing heavily in proprietary solutions.
Read moreState Management
The DOMX approach to state management embraces the unidirectional data flow pattern popularized by `FLUX` and `Redux` but relies on API's that already exist in the DOM.
Read moreData Elements
The DataElement
base class provides for a Flux/Redux style unidirectional data flow state management pattern using DOM events and custom elements.
By utilizing the DOM and custom elements the footprint is small and performance is fast since communication happens through DOM events and not a JavaScript library.
Read moreClient Side Routing
Often times routing begins and ends with following the boilerplate examples used in your web framework of choice. Routing may even be a feature that is tacked on haphazardly at the end of a development cycle when you realize your application is behaving strangely and need to do some patch work to fix some primary use cases. Or sometimes, even more tragically, routing may not be implemented at all.
Read more