Learning paths

The docs are broad because Cratis is a stack. Use a path when you want sequence: what to read first, what to build, and where to go next.

New to event sourcing Understand why facts, projections, consistency, and event modeling matter.

Build a full-stack app Follow the command to event to read model to React loop.

Operate Chronicle Run, inspect, diagnose, replay, and harden a Chronicle deployment.

New to event sourcing

1. Read Why event sourcing.
2. Read Event modeling.
3. Build the Chronicle tutorial.
4. Read Consistency and When to use event sourcing.
5. Use Community and help when your domain model raises questions.

Build a full-stack app

1. Start with Get started.
2. Follow Build a full-stack feature.
3. Learn Arc vertical slices.
4. Add screens with Components getting started.
5. Run the Samples beside the docs.

Evaluate Cratis

1. Read Why developers choose Cratis.
2. Read Adopting Cratis.
3. Check FAQ and Version compatibility.
4. Review Production readiness.
5. Ask adoption questions in Community and help or use Professional help for dedicated review.

Operate Chronicle

1. Read Chronicle hosting.
2. Review Chronicle configuration.
3. Learn the CLI and its operational scenarios.
4. Use Production readiness as the cross-stack checklist.
5. Keep Security and What’s new in your release process.

Frontend developer

1. Read Arc frontend.
2. Learn generated proxies.
3. Use Components for command forms, dialogs, data tables, and styling.
4. Browse Storybook.
5. Use Samples to see the screen and backend together.

Contributor

1. Read Contributing.
2. Read Governance.
3. Find product docs and issues in the repository that owns the behavior.
4. Use Feedback and suggestions for early ideas.
5. Run the relevant build and docs checks before a pull request.