Field manual · 09
Contributing
Choose a Scout UI contribution path and follow the repository's canonical code, accessibility, docs, and artwork policies.
Search terms: contributing, code, accessibility, documentation, artwork, provenance
Scout UI welcomes focused work that strengthens sticker-native behavior, accessibility, performance, interoperability, documentation, or cleared artwork. This page summarizes the route in; repository policy files remain canonical.
Choose a contribution area
Code changes need rationale, tests, public-contract awareness, and visual evidence when behavior is visible. Accessibility contributions should document keyboard, motion, touch, reflow, and assistive-technology context. Documentation should use real exports and ordinary application content.
Treat artwork separately
Artwork needs creator affirmation, source provenance, license, attribution status, editable source, and safety validation. Scout product material, third-party logos, copyrighted characters, and unclear redistribution rights cannot enter the pack.
Follow canonical policy
Read CONTRIBUTING.md, CODE_OF_CONDUCT.md, SECURITY.md, SUPPORT.md, and
the sticker asset contribution guide in the public repository. Do not report a
security concern through a public issue.
Keep scope disciplined
A proposed component must add distinct behavior, not merely a name prefixed by “Sticker.” v0.1 remains eight components, three packages, and one docs app.