Contributing to SpryEditor

Everything new contributors need to understand the product, work safely inside the codebase, and keep the design system coherent.

Getting Started
How to ramp up quickly on the project.
  • Read the repository documentation and current product routes first.
  • Run the app locally and verify the main editor, auth flow, and settings area.
  • Review the design principles before changing shared UI or messaging.
Where To Help
High-value areas for contribution.
  • Editor workflows, export reliability, and asset management.
  • Design system consistency across settings, public pages, and app surfaces.
  • Accessibility, responsive behaviour, and regression coverage.
Contribution Standards
Expectations for production-ready changes.
  • Keep changes cohesive, testable, and aligned with brand and accessibility requirements.
  • Prefer shared tokens and reusable components over page-specific overrides.
  • Document assumptions and verify affected routes before opening a PR.
Feedback Loop
How to keep the project improving.
  • Report regressions with exact routes, repro steps, and screenshots when possible.
  • Flag any design-principle mismatch before it spreads into more modules.
  • Treat contributor notes as living documentation for the next person.