Contribution guide
Rastry is early-stage open source software. Contributions are most useful when they preserve the shared domain rules and make behavior easier to verify.
Before changing code
Section titled “Before changing code”Read the repository contribution guide, the product definition, and the relevant change records.
The dependency direction runs from apps through core/image-engine to contracts. The web package is intentionally independent: do not import Desktop code, Electrobun, Bun.Image, or user filesystem APIs into it.
Checks
Section titled “Checks”Use the repository toolchain:
bun installbun run checkbun --filter @rastry/web typecheckbun --filter @rastry/web buildKeep tests in the package’s test/ tree and cover safety invariants, failure isolation, or observable behavior. Do not commit generated dist, build, .hutch, or optimized output.
Web content changes
Section titled “Web content changes”Public content is English for this first release. Catalog pages must have a real example, a stable slug, a source link, and useful related links. Update CHANGELOG.md or a release entry when the public release story changes. Do not add empty SEO pages or advertise unsupported features.
Open a focused pull request with the behavior, verification performed, and any platform-specific limitation.