docs: broaden README with event sourcing and CQRS positioning and ecosystem links - #580
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
README-only changes to make the samples repository easier to discover and to reflect the breadth of the Cratis stack accurately:
Why
The samples repo is a common entry point for people evaluating the stack, but the README did not mention "event sourcing" or "CQRS" in its tagline and had no outbound links to the rest of the ecosystem. This aligns it with the positioning used across the other Cratis repositories.
Suggestion (not in this PR)
samples.jsonis intentionally untouched. As a follow-up, consider adding sample tracks for the non-.NET Chronicle clients (TypeScript, Kotlin/Java, Elixir) so cratis.io/samples reflects the multi-language breadth — best planned through a dedicated issue.