Simple components for content sites.
Amkit builds the parts a documentation site actually needs — accessible elements, page-level blocks, and the content pipeline behind them.
- Render markup, not opinions.
- Every element ships behaviour and semantics. The stylesheet stays yours.
- Keep the data separate.
- Navigation, validation, and routes are computed by a package that renders nothing.
- Work without JavaScript first.
- The open state belongs to the browser. A runtime binds on top when there is one.
A note
Why the split is the whole idea.
A component library that ships a stylesheet decides how your site looks. A content helper that renders markup decides how your site is built. Both are borrowed decisions, and both are expensive to undo later.
So the packages are split along that line. @teasim/astra renders markup and carries behaviour with it, @teasim/aster arranges those elements into a site's chrome, and @teasim/astro computes navigation, validates content, and serves the machine-readable routes. None of them knows what the others look like.
Amkit
@teasim/astra · @teasim/aster · @teasim/astro