Begin
Introduction
What Ajo is, how its four layers fit together, and how far along each one is.
Ajo began as a small library for building interfaces with JSX and JavaScript generators. Around it grew a platform that can take an application from its first component to a server you control. Each piece is a separate package: use Ajo alone in any page, or follow the whole path.
Four layers
| Layer | What it does | Packages |
|---|---|---|
| Ajo | Renders components. Stateful components are generators; this.next() renders them again. | ajo, ajo-cloves, ajo-ui, ajo-ui-playa |
| Ajo Kit | Turns components into an application: file routes, server loaders and actions, SQLite, live updates. | ajo-kit, ajo-kit-auth, ajo-kit-mail |
| Ajo Engine | Runs a Kit application as sealed, precompiled bytecode with declared capabilities. | ajo-engine, ajo-engine-compiler |
| Ajo Server | Hosts Apps in rootless containers on an Alpine Linux image, with an administration App. | ajo-kit-server |
The layers are designed to fit together, but each boundary is explicit. Node runs development, builds and tests; in production a Kit application runs only on Ajo Engine. Ajo Server deploys what the engine runs.
Where things stand
These are early releases. The documentation describes what exists today, including its limits.
| Package | Version | Status |
|---|---|---|
ajo | 0.2.0 | Published on npm. |
ajo-kit | 0.5.0 | Published on npm. Pre-1.0: its API is still being refined. |
ajo-engine | 0.2.0 | Pre-release. The native packages are verified on Linux x64 (Alpine musl and Freedesktop glibc). |
ajo-kit-server | 0.3.1 | Experimental. Hosts come from signed releases, on this machine or on DigitalOcean; there is no automated host replacement yet. |
How to read these docs
Start with the quick start to create a working App from the official starter. Each layer then has its own section, from first steps to a complete reference. The packages section covers authentication, mail and the component libraries. Every page after the quick start ends by naming the repository documents it is based on.