Lumos Ecosystem: The Stuff Nobody Sees

A language is more than a compiler. Its the docs that teach it. The CI that validates it. The examples that prove it works. The invisible infrastructure that makes adoption possible.

After shipping Lumos core and the editor toolchain, I built everything else a production language needs.

The Documentation

docs-lumos runs on Docusaurus at lumos-lang.org. Not just API reference — actual learning paths. Getting started guides. Concept explanations. Copy-paste examples that actually work.

The key insight: documentation is onboarding. Every page should answer "what do I type next?" If someone lands on the docs and leaves confused, thats a failure.

MDX lets me embed interactive examples. Code blocks with syntax highlighting. Tabs showing Rust output vs TypeScript output side by side. The same visual language as the README, consistent everywhere.

The GitHub Action

lumos-action makes CI integration one YAML block. Add it to your workflow, point it at your schema files, get generated code on every push.

- uses: getlumos/lumos-action@v1
  with:
    schema: schemas/
    output: generated/

No local Lumos installation required. The Action handles everything. Validation, generation, even PR comments showing what changed.

The Examples

awesome-lumos collects production-ready examples. Not toy demos — actual patterns people need. Token accounts. Game state. NFT metadata. Governance structures.

Each example includes the Lumos schema, generated Rust, generated TypeScript, and a README explaining the pattern. Fork it, modify it, ship it.

Why Bother?

Compilers are easy to ignore. Nobody adopts a tool because the parser is elegant. They adopt it because they found clear docs, working examples, and easy CI integration.

The ecosystem is the product. Everything else is implementation detail.

Components: Documentation (Docusaurus), GitHub Action, Example Collection

Links: Docs • GitHub Action • Examples