want to help build okommerce?

ways to contribute

code contributions — bug fixes, new modules, performance improvements. open a PR against the main branch on github.

documentation — fix typos, clarify confusing parts, add missing sections. docs live in /docs in the repo.

translations — help us improve our 5 default languages or add new ones. translation files live in /locales.

bug reports — file an issue on github. include reproduction steps, expected vs actual behavior, environment details.

community help — answer questions on the forum or github discussions.

code style

follow the existing patterns. we use .editorconfig and an automated linter. the CI will catch most issues.

• vertical-slice architecture — keep new features self-contained
• EF Core for writes, Dapper for reads
• async everywhere, no blocking calls
• tests for non-trivial logic — xUnit + Moq

PR process

1. fork the repo
2. create a feature branch
3. commit with a clear, conventional commit message
4. open a PR against main with a description of what changed and why
5. wait for CI to pass and a maintainer to review
6. address feedback, merge

contributor license agreement

contributions are licensed under MIT to match the rest of the codebase. by submitting a PR, you confirm you have the right to do so.

questions?

email contributors@okommerce.com or open a github discussion.