Documentation map

Hedron has a large repository because it contains user guides, API contracts, package documentation, RFCs, acceptance evidence, and historical release material. These are not interchangeable.

If you are building an application

1. Build your first app
2. Build a notes app — one continuous learning path
3. Core concepts
4. Minimal form POST
5. What is HTMX?
6. Learning path
7. Current release and support — when pinning for production
8. Deployment and Troubleshooting

If you are evaluating adoption

Read What's ready today, Evaluate Hedron, Enterprise diligence, Public 1.0 readiness, Security, and the production adoption checklist.

If you are looking up an API

Start with API by task if you know the outcome. Use the full API reference for exact contracts, then check Stability and Symbol tiers to check whether a symbol is stable, beta, or experimental, and use Error codes for diagnostic remediation.

If you are contributing

Start with Contributor day one, then read Contributing. Maintainer-only design material lives in the repository under docs/rfcs/, docs/implementation/, and docs/acceptance/; those directories contain proposals, contracts, and evidence rather than end-user guidance.

Status labels

• Current: part of the active public product path.
• Experimental: public but changeable; use with the documented fallback.
• Historical: describes an earlier release or phase.
• Maintainer: repository process or engineering evidence, not an adoption guide.