Fix a bug, translate the interface, document a workflow, or send a reproducible report. Every contribution moves the project forward, and none of them require being a maintainer.
KOMA Studio is built in the open by people who use it to ship chapters. Code is only one of the ways to help — and it is rarely the most urgent one.
Start from an issue: report a bug, claim a good first issue, translate the UI, or improve the docs. Code contributions follow the usual fork, branch, commit, pull request flow.
Search the issue tracker first — someone may already be working on it. For anything larger than a bug fix, open an issue or a discussion and describe the approach before writing code. Small, focused pull requests get reviewed fastest.
Fork the repository, create a branch, make the change, and open a pull request against the default branch. Include what changed, why, and how you tested it — screenshots or sample pages help a lot for visual work.
A project like this lives or dies on real-world feedback. Translations, documentation, and reproducible bug reports from actual chapters are often more valuable than another feature branch.
Reviews are public and focused on the code, not the person. Expect questions about edge cases, performance on large chapters, and whether the change fits the workflow. Maintainers may ask for changes before merging — that is normal for any open-source project.
