When we say Sustainability in HAX we mean a few different forms for sustinability. There's environmental, technological, and project sustainability.
- send less data, use less battery
- thin offline, low resource, low internet; how do we best serve these communities?
- high cache times via zero configuration CDNs
- repurposed solutions​ as much as possible
- unbundle to ship assets that are use less data over the course of multiple transactions instead of incentivizing the singular one-off web transaction
- Code should work stand alone, without HAX
- HAX is helping write code, it is not a requirement
- No vendor / hosting environment specific capabilities that lock you to hosting with functionality
- accountability; able to read files, find problems, report them, and rapidly fix them
- html as API; code in html structure will be supported by js asset
- CDNs that mirror and fallback in order to try and serve assets locally, then cascading to global CDNs if not available
- No database; easy migrations. Things that move easily can sustain projects more readily
Watch project lead btopro explain the difference in how the "magic script" delivers assets in order to improve sustainability.
- 100% open source; from the individual web components all the way up to CDNs, SaaS, PaaS, and CMS solutions
- Community driven, backed by Penn State, an R1 research university, to deliver online course experiences and websites
- HAX is part of Apereo and contributed to by others outside of Penn State
- Pipeline of student developers contributing to and constantly improving the HAX platform in their studies via Project EdtechJoker