Loading haxcellence..

Developing for HAX itself or leveraging it's tools? There's a lot going on in our ecosystem so if we miss something let us know!

Contribute webcomponents repo

The HAX monorepo has all 500+ blocks in the HAX ecosystem, as well as the editor, site and CMS (front-end) aspects of the system. If contributing to ANYTHING front-end focused, it will be through this repository. General contribution workflow:

• Fork the haxtheweb/webcomponents monorepo
• yarn install
• to work on HAX as a while, run yarn run hax from the project root
• to work on an individual element, cd elements/element-name and then run yarn run start
• Make your changes, commit, push up and then open a PR against the main repo

Create my own web components

The HAX CLI is the best way to accomplish this. It leverages Lit + OpenWC recommendations for building new web components that can easily be published on npm. It also has boilerplate that makes it easier to build blocks that visually look like the HAX ecosystem (via DDD) and also ways of creating stand alone HAXsite's and workflows for building custom themes and elements for the ecosystem.

Contribute to a specific back-end / system integration

Each project whether HAX11ty, haxcms-nodejs, haxcms-php, HAXiam, unbundled-webcomponents, no matter what it is, it will have it's own repository for contribution.