# Thank you for considering to contribute!
I love Super Productivity. It's my favorite side project and I use it every day to plan my tasks and to track my time. I need your help!

## Things that would help

### Feedback
* What do you like and what not?
* What should be improved?
* What essential features are missing?
* If you don't, why won't you use the app?
* Reporting bugs

### Design & UX
I am not a designer. So there is probably a lot not to like. It would be absolutely great if a professional could have a look or two.
* Are the general concepts working? What should be improved?
* Providing better icons

### Features/Coding
* Improving existing issue provider integrations (Jira, GitHub, GitLab, Gitea, OpenProject, Linear, ClickUp, Azure DevOps, etc.)
* Improved data syncing
* Bug fixes and performance improvements

### Translations
* See our [translation guide](../docs/TRANSLATING.md) for how to contribute translations

### Documentation/[Wiki](https://github.com/super-productivity/super-productivity/wiki)
* Flagging outdated or incorrect documentation (or correcting via Pull Requests) is greatly appreciated.
* Creating [guides and workflow examples](https://github.com/super-productivity/super-productivity/wiki/1.00-Quickstarts) with short videos or screenshots would be welcomed.

## Commit Message Format

We use the Angular commit message format: `type(scope): description`

**Types:** `feat`, `fix`, `docs`, `style`, `refactor`, `perf`, `test`, `build`, `ci`, `chore`

**Examples:**
* `feat(tasks): add recurring task support`
* `fix(sync): handle network timeout gracefully`
* `test(e2e): fix flaky sync tests`

**Note:** Use `test:` (not `fix(test):`) for test-related changes. The `fix` type is reserved for actual code/bug fixes.

Include the issue number in your commit message if fixing a particular issue (e.g.: `feat: add nice feature #31`).