Explore

Open the parts of the language that are easiest to learn by trying.

This page groups together the hands-on surfaces for AEON: guided learning, lightweight editing, and example-driven features that are easier to understand through direct interaction.

Use it as the practical companion to the overview and the walkthrough pages.

Entry Points

Choose a way in.

Walkthrough

Learn the language step by step

Start with the structured walkthrough, then continue into the more advanced features once the basic document model feels clear.

Open walkthrough

Playground

Use a simplified editor

Try bindings, containers, anonymous child metadata, modes, and multiline text in a stripped-back editing surface with AEON highlighting.

Open playground

Processing

Trace source into runtime meaning

See a document move through canonical form, assignment events, schema checks, meaning validation, and Tonic materialization.

Open processing

Validation

Pair AEON with an AEOS schema

Edit source and schema side by side, seed rules from an AEON document, and watch validation diagnostics update.

Open AEOS playground

Templating

Render AEON nodes as HTML

See the AEON Matter template demo model: data files, node templates, semantic directive comments, and generated HTML.

Open templating

Wiki

Read the public guide

Use the wiki when you want the fuller language guide, AEOS reference, examples, and links to the authority specs.

Open wiki

Implementers

Build against the Aeonite specification surface.

If you are writing an AEON parser, validator, runtime, or CTS adapter, use Aeonite as the formal publication surface for the specifications this implementation follows.

AltoPelago maintains the implementation and learning surfaces; aeonite.org publishes the versioned specifications, conformance boundaries, licensing context, and source repositories.

Recommended Flow

A simple path through the interactive surfaces.

Start with the walkthrough if you want the language introduced in order.

Open the simplified playground once you want to type the syntax yourself.

Use the processing walkthrough when you want to see how the same document becomes validated, canonical, and materialized.

Use the templating example when you want to see AEON data and node-structured templates combine into rendered HTML.

View as Markdown