Improve discoverability: why paragraph, ecosystem links, and package tags - #64
Merged
Conversation
Add a short Why paragraph for Marten and Wolverine users, summarize the exhaustive goals list in the README and move the full list to Documentation/goals.md, and append the Cratis ecosystem section with cross-links to the wider stack.
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
1 participant
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
Documentation/goals.md(linked from the README, the docs overview, and the docs ToC); the README now carries a concise summary instead.PackageTags(cratis;event-sourcing;cqrs;screenplay;marten;wolverine;critterstack;interop) so the package is findable on NuGet by category and framework terms.Why
Better discoverability across the Cratis organization: consistent ecosystem cross-links, accurate breadth wording, and search-relevant keywords (event sourcing, CQRS, Marten, Wolverine) on the surfaces people actually find first. All wording is factual; the pre-release status and JasperFx non-affiliation disclaimer are unchanged.
Labeled
no-release: documentation and package-metadata only, no consumer-observable behavior change.