Skip to content

Improve discoverability: README positioning and npm keywords - #24

Merged
woksin merged 2 commits into
mainfrom
docs/sibling-pattern-and-npm-keywords
Aug 28, 2026
Merged

Improve discoverability: README positioning and npm keywords#24
woksin merged 2 commits into
mainfrom
docs/sibling-pattern-and-npm-keywords

Conversation

@woksin

@woksin woksin commented Aug 27, 2026

Copy link
Copy Markdown
Contributor

Summary

Improves how Scene is found and understood from search engines, npm, and the rest of the Cratis ecosystem. No shipped behavior changes — README wording and package metadata only.

Added

  • README one-liner describing Scene as the UI model of the experimental Cratis model-first layer, with a sentence placing it in the Screenplay → Stage → Scene pipeline
  • Shared "Cratis ecosystem" section in the README cross-linking Chronicle (and its language clients), Arc, Components, CLI + Workbench, the model-first layer, supporting tools, and Samples
  • npm keywords for all eight @cratis/scene.* JavaScript packages (ui, react, event-modeling, cqrs, event-sourcing, low-code, and package-specific terms)

Changed

  • README now hyperlinks Screenplay, Stage, and Studio where they are mentioned, and closes with a "Part of the Cratis platform · MIT" footer

woksin added 2 commits August 28, 2026 00:50
Lead with what Scene is (the UI model of the experimental Cratis
model-first layer), link Screenplay, Stage, and Studio where they are
mentioned, and add the shared Cratis ecosystem section so the
repository is discoverable from the rest of the stack.
All eight @cratis/scene.* packages published no keywords, making them
hard to find on npm. Add per-package keyword sets covering the Cratis
ecosystem and category terms (ui, react, event-modeling, cqrs,
event-sourcing, low-code).
@woksin
woksin merged commit edc4cda into main Aug 28, 2026
3 of 4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant