Feedback and suggestions

Cratis gets better when people tell us where the model is confusing, where the tools feel rough, and where the docs leave a gap. You do not need a fully shaped proposal before you speak up. A rough observation from a real project is often the most useful feedback.

Use this page when you want to suggest an improvement, report that something was hard to understand, or tell us what would make Cratis easier to adopt.

Discuss an idea in Discord Use Discord for early suggestions, adoption feedback, design questions, and exploratory product ideas.

Open a documentation issue Report unclear guides, missing examples, broken explanations, or topics you expected to find.

Read the roadmap See what is stable, what is being hardened, what is being explored, and where feedback helps.

Understand governance See how ideas become issues, design notes, pull requests, releases, and documentation.

Browse product issues Turn actionable product feedback into an issue in the repository that owns the behavior.

What to send where

Feedback	Best place
”This concept confused me”	Cratis Discord, then a Documentation issue if the docs need a change
”This API or workflow feels awkward”	Cratis Discord for discussion, then the matching product issue tracker
”The docs are missing an example”	Documentation issues
”This bug is reproducible”	The matching product issue tracker
”I have an idea for a feature”	Cratis Discord for early shaping, then a GitHub issue when the proposal is concrete
”I want to understand what is planned”	Roadmap
”I want to propose a larger design change”	Governance
”I want to contribute the change”	Contributing

If you are not sure where the feedback belongs, start in Community and help. We can help route it.

Product issue trackers

Area	Issue tracker
Chronicle event store, clients, Workbench, and hosting	Chronicle issues
Arc commands, queries, proxy generation, validation, and backend/frontend integration	Arc issues
React components, forms, dialogs, tables, styling, and Storybook	Components issues
CLI commands, diagnostics, and AI command catalogs	CLI issues
Fundamentals libraries and shared .NET/TypeScript helpers	Fundamentals issues
Documentation site, guides, examples, and broken links	Documentation issues

Useful feedback

The most useful feedback tells us what happened in context:

• What you were trying to do.
• Which product or page you were using.
• What you expected to happen.
• What happened instead, or where you got stuck.
• What would have made the next step obvious.

For documentation feedback, a short note like “I reached this page looking for X, but found Y” is enough. For product feedback, include the package version, runtime, command, API, or component involved when you know it.

Real examples beat polished proposals

If you can share the event, command, projection, screen, CLI command, or paragraph that caused the friction, start there. We can help turn the observation into a concrete issue or improvement.

What happens next

Open feedback may stay as a conversation until the right shape is clear. Once it becomes actionable, we prefer to capture it as a GitHub issue so it has a durable record, can be linked from pull requests, and does not disappear in chat history.

For questions that need an answer more than a change, use Community and help.