mirror of
https://github.com/johannesjo/super-productivity.git
synced 2026-07-17 16:37:43 +00:00
* docs(wiki): refactor download page Rework and improve download page in preparation for README updates. * chore(ci): simplify the initial release text Centralizing all links to one place will make maintenance of docs easier. * chore(docs): Update meta docs and templates Aligning issue templates and other docs to support the use of the wiki and to encourage additions from others. * chore(docs): align README with new download page
1.8 KiB
1.8 KiB
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 for how to contribute translations
Documentation/Wiki
- Flagging outdated or incorrect documentation (or correcting via Pull Requests) is greatly appreciated.
- Creating guides and workflow examples 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 supportfix(sync): handle network timeout gracefullytest(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).