What Eigenn documentation covers
Eigenn is the operating workspace around the books. The docs explain how cash, customers, invoices, transactions, runway scenarios, and weekly review work stay attached to the same finance record.
- Use Docs for product concepts and setup decisions.
- Use Guides for complete workflows your team can repeat.
- Use API Reference for integration details generated from the OpenAPI contract.
- Use Changelog and Support when you need release context or help from the team.
How the docs are organized
The documentation follows the same navigation shape as the product: start with the operating record, then move into the core workspace, then connect APIs and automations.
| Section | Use it for |
|---|---|
| Docs | Concepts, feature surfaces, and setup paths |
| API Reference | Auth, endpoints, events, and schemas |
| Guides | Step-by-step finance and integration work |
| Changelog | Product and API updates |
| Support | Help paths and the context to send |
Adding new pages
Add a new .mdx file under apps/web/content/docs, then add the page path to docs.json. The docs shell reads the manifest and the MDX frontmatter, so navigation and page metadata stay content-driven.