docs(readme): unify hub-and-spoke ecosystem header - #39
Merged
Conversation
Apply the shared "Part of Statewave" header to the top of the README: core runtime, both SDKs, connectors, docs, examples, admin, and statewave.ai, with a centralized issue-tracker line and the current repo marked as the active entry where it appears in the nav. Gives every public repo a consistent path back to the rest of the family.
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
Adds the unified "Part of Statewave" ecosystem header to the top of this repo's README — linking the core runtime, Python & TypeScript SDKs, connectors, docs, examples, admin, and statewave.ai, plus a centralized issue-tracker line. Where the repo appears in the nav, its own entry is marked as the active "you are here" item.
Why
Consistent hub-and-spoke navigation across the public repos: whichever repo a visitor lands on, they get a clear path back to the core project and its siblings.
Scope
README-only — no code or behavior changes.