# Axo
Axo
Slides in .mdx, components in .axo, output that is just HTML.
Installnpm i -D @ambystech/axoLicenceMIT
A deck should still open in five years.
The tools that make slides beautiful make them fragile: a runtime to boot, a CDN to reach, a framework to keep upgrading.
The usual deal
Hydration, client islands, a bundle to ship. It renders — until the wifi drops, or the CDN moves, or the framework majors.
What Axo ships
HTML, CSS and vendored assets. No client framework, no hydration, no CDN
link. client:* is a compile error, not a warning.
A compiler with a CLI around it.
Write slides as .mdx. Write components as .axo. Everything is decided at
compile time, and what lands in dist/ is a static site.
0network requests over file://39components included<3MBvendor payload
MDXReveal.jsPreact at build timeZero runtime
Five stages, then it is HTML.
RegistryYour components and layouts, shadowing the built-ins.
→ registry
→ registry
SlideMDX to a Reveal section, rendered to a string.
ShellThe page around it — fonts, theme, footer.
VendorReveal, fonts and Mermaid copied in locally.
Build
→ dist/
dist/, and nothing pointing outside it.→ dist/
If the build cannot render it correctly, it fails and names the file and line.
The filename is the component name.
Drop Tier.axo in components/ and you have <Tier>. No registration, no
import, no list to update.
components/Tier.axo
---
const { name, price } = Axo.props;
---
<div class:list={['tier', price && 'paid']}>
<span class="n">{name}</span>
<h4>{price}</h4>
<p><slot /></p>
</div>
One command.
~
npx @ambystech/axo new my-deck
Docsgithub.com/ambystechcom/AxoEditorAxo for VS Code
