Skip to main content

Contributing

Contribute to Certo responsibly

Contributions are easiest to review when they stay scoped, are grounded in project docs, and clearly describe the operational impact of the change.

Repo structure

  • Frontend logic lives under src/frontend
  • Backend logic and Strapi configuration live under src/backend
  • Project docs, architecture notes, and config guides live under docs

Before opening a PR

  • Read the project docs and current roadmap to confirm scope
  • Keep changes targeted to a single problem or feature area
  • Document any config or operational changes introduced by the patch

Validation

  • Run the relevant frontend unit tests
  • Use the existing backend TypeScript checks where relevant
  • Confirm that security-sensitive changes are documented and not silently reduced in scope

Contribution checklist

  1. Read the root documentation and any relevant architecture or security notes before proposing a change.
  2. Keep the patch focused on one user journey, bug fix, or feature area.
  3. Document any configuration or deployment changes that affect operators.
  4. Validate the relevant frontend or backend checks before requesting review.
  5. Reference the project issue or roadmap context when the work touches product or security concerns.