Loading web-ubiquity..

Platforms are dictated to for most users by one of the following:

• platform / OS they use personally (iOS, Android, Microsoft, etc)
• vendor they use (website tonight software)
• OS and libraries that their server is running

These are largely irrelevant to someone wanting to communicate online and yet constrain all of their decisions associated with web publishing. Situations where this leads to innovative potential being stiffed and costs to spiral for the average consumer of web content production

• Drupal and Wordpress are PHP 20+ year old CMS solutions that are very popular for hosting
• However, the modern web is dominated by NodeJS based development environments.
• This leads to a needlessly complex web for consumers in this space which largely leads to outsourcing of hosting and production
• The platforms are free, but the knowledge tree required to engage in these platforms effectively makes them vendor locked in to extend and grow beyond their base.

HAX being shipped in a platform agnostic way, by piling much of the functionality onto the front-end of the browser, means that when there are back ends required they are minimalist. Writing a new back end in newer languages will cost far less in development and maintenance than past solutions.

Multiple platforms, one system, one format.

The HAX core team has been able to produce working backends in PHP and NodeJS. This has lead to:

• HAXcms and HAXSite deployed on nodejs hosts​
• HAXcms deployed on PHP hosts
• HAXSite deployed via 11ty
• HAX npx cli for developers locally
• HAXcms compiled for a Desktop App
• HAX editor on topof Drupal , WordPress and ClassicPress, GravCMS
• HAXcms on top of ELMS:LN (this is how we migrated many sites off our old platform 👀)

All of these come from code bases that are 98% identical thanks to the HAX front-end delivery of assets and our community commitment to ubiquity in web publishing.