# 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](#new-to-event-sourcing)
  [Build a full-stack app](#build-a-full-stack-app)
  [Operate Chronicle](#operate-chronicle)
## New to event sourcing

1. Read [Why event sourcing](/chronicle/why-event-sourcing/).
2. Read [Event modeling](/event-modeling/).
3. Build the [Chronicle tutorial](/chronicle/tutorial/).
4. Read [Consistency](/chronicle/concepts/consistency/) and [When to use event sourcing](/chronicle/concepts/when-to-use-event-sourcing/).
5. Use [Community and help](/community/) when your domain model raises questions.

## Build a full-stack app

1. Start with [Get started](/chronicle/get-started/).
2. Follow [Build a full-stack feature](/build-a-full-app/).
3. Learn [Arc vertical slices](/arc/vertical-slices/).
4. Add screens with [Components getting started](/components/getting-started/).
5. Run the [Samples](/samples/) beside the docs.

## Evaluate Cratis

1. Read [Why developers choose Cratis](/why-cratis/).
2. Read [Adopting Cratis](/adopting-cratis/).
3. Check [FAQ](/faq/) and [Version compatibility](/compatibility/).
4. Review [Production readiness](/production-readiness/).
5. Ask adoption questions in [Community and help](/community/) or use [Professional help](/professional-help/) for dedicated review.

## Operate Chronicle

1. Read [Chronicle hosting](/chronicle/hosting/).
2. Review [Chronicle configuration](/chronicle/hosting/configuration/).
3. Learn the [CLI](/cli/) and its operational scenarios.
4. Use [Production readiness](/production-readiness/) as the cross-stack checklist.
5. Keep [Security](/security/) and [What's new](/whats-new/) in your release process.

## Frontend developer

1. Read [Arc frontend](/arc/frontend/).
2. Learn [generated proxies](/arc/understanding-the-proxy-boundary/).
3. Use [Components](/components/) for command forms, dialogs, data tables, and styling.
4. Browse [Storybook](/components/storybook/).
5. Use [Samples](/samples/) to see the screen and backend together.

## Contributor

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