A to-do list, time tracker and daily planner for focused personal work. Private, offline-first and open source.
:globe_with_meridians: Open Web App or :computer: Download
For all current downloads, package links, and platform-specific notes:
check the wiki
And much more!
[!NOTE] The web version has some limitations: See the Web App vs Desktop comparison for more details.
Starting Point in Wiki:
First steps •
Reference •
How-To
Productivity Tips:
Keyboard Shortcuts •
Short Syntax
Need Help?
Visit the discussions page
See the bottom of the README for more information on the documentation.
Here are some other topics covered in the official wiki:
Development:
Run dev server •
Package the app •
Build for Android •
Run with Docker
Data Management:
User Data •
Issue Providers •
Sync Providers
Customization:
Plugins •
Themes
APIs:
Sync Server •
Plugins •
REST
The development of Super Productivity is driven by a wonderful community of users and contributors. Thank you all so much for your support!
:eyes: Check out our awesome curated list of community-created resources about Super Productivity
You don't have to be a programmer to help: spread the word, answer questions, report bugs, contribute translations, build plugins or themes, or sponsor the project.
Before opening a pull request, read CONTRIBUTING.md and follow the commit message format.
A big thank you to all our sponsors!
(If you are, intend to or have been a sponsor and want to be shown here, please let me know!)
There are two wikis: the official one hosted by GitHub and the autonomously generated variant using DeepWiki.com. The manually curated version is a more stable and approachable resource designed to help you understand the app from a more human-focused perspective whereas DeepWiki is optimized for explaining the code itself with little regard for context beyond that.
It is preferable to maintain local documentation rather than rely on an external service. It is also preferable that the documentation is updated in tandem with the code changes as demonstrated in this commit.
Changes to files within ./docs/wiki are linted in CI before being automatically
sync'd to the repository's official Wiki hosted by GitHub.
Migrating to Docusaurus is a long-term goal once the content and structure of the wiki has matured and the remaining "legacy docs" have either been reworked or removed. There are some automations in development to help reduce the difference between the published docs and the state of the code while retaining a human-in-the-loop.
If you have very specific questions about how the code works or why a bug might be producing
a particular message it might be useful to
. It can help "cite your sources" when discussing functionality and code that you don't fully
understand as part of feature requests or bug reports.
This automated reference does come with some significant drawbacks:
| 日期 | 榜单 | 排名 | 周期新增 | 总 STAR |
|---|