Platform Agnostic means that HAX technologies will work anywhere. They can work stand alone in the case of HAXsites like this one, as part of a larger solution like HAXcms or HAXiam, on static web pages, codepen's, Drupal, Wordpress, custom CMS's, it doesn't matter. HAX should work there. The web component standard makes this technically possible, and the way in which we implement that standard helps us maximize integration and ease of adoption by existing and future solutions.
- No hosting specific tools that would lock the user into PHP, NodeJS, 11ty or any other style back-end compilation
- Support for the h-a-x editor working separately from HAXcms in order to operate like text area drop-in editors of the early 2000s
- Support for migration from existing sources such as existing CMSs, static site generators, markdown, docx and other structured data formats that can be converted to the JSON Outline Schema API
- Highly optimized Developer Experience to ensure one command to work on any system in our universe
- Desktop application support for OS's that we can maintain via Electron
- Integration with external Frameworks and Libraries as the community desires
- Support for All Evergreen browsers
- HAX has plugins for Wordpress, Drupal, BackdropCMS, GravCMS
- All web components made to work with HAX, work without HAX present, improving portability but also allowing for them to work in any system they are implemented
- HAXcms has plugins for Drupal as a theme layer so that Drupal headlessly feeds API data to HAXcms to render. HAXcms believes its still itself and Drupal saves output in the previous mentioned plugin as node content