Aria Templates in a nutshell:
The MVC's terminology in AT:
Templates can either be evaluated client-side or precompiled at build time.
To get started with Aria Templates, you have several options:
bootstrap.jsfile in your HTML page, to run the original, development source code,
npm install ariatemplatesin the command line, then call
require('ariatemplates')from your code to load the framework.
You can use jsFiddle-like InstantAT, where you can play with Aria Templates in your browser (requires a reasonably modern browser).
The framework itself doesn't have any external dependencies.
We use Grunt, JSHint, UglifyJS, attester and a couple of other tools for building and testing.
Web apps & services:
Feel invited to contribute highlighters for editor of your choice, or other useful tools!
We release a new minor version (1.3.5, 1.3.6, ...) every 3 weeks, containing new features and bugfixes. Each version is thoroughly tested before the release. These releases are backward compatible. Occasionally we also backport important fixes to some of the older releases (1.3.1A, 1.3.1B etc.) - see tags.
Twice or three times a year, we issue a non-backward-compatible release, bump the the second digit (e.g. 1.3.x -> 1.4.1) and provide migration guide.
Before removal, items are marked as deprecated for at least 9 weeks (usually much more). We inform about deprecation in the docs, release notes and by flooding your console -- you won't overlook it.
Visit our forum to ask questions.
If you spotted some code problems in the framework, please open an AT issue or ideally, a pull request with the fix and a test.
If you spotted some issue with missing / incorrect documentation on ariatemplates.com, please open a usermanual issue.