I use the nearly the same.
- Zim-Wiki for items or procedures that I refer to or repeat often. Zim-Wiki is mostly plain text and transportable, but handles embedding small screenshots. I keep another Zim-Wiki notebook for small projects or investigations.
- A simple text file list for in progress items or projects that I am working that have more or less an end date or specific goal
- A simple text file list for to-do items, vague plans, and links to check. This file changes almost daily.
- A simple text file list for wish list items and purchase ideas
> syncthing on all my devices to keep all them all current
In my paid work I have a few additional things, but not much more. The most important is a separate subdirectory for each project's files. Structure it so that it is ready to use in a retrospective repository when finished. Refer back to it often when planning similar projects.
I used to "hoard" knowledge, had a large library, sets of sorted bookmarks files, etc., but I'm finding that I need less and less of that. I think the biggest change took place when I made a short project once with the goal of making my home computing portable and self-hosting. That really simplified a lot.
A big help is being consistent in a format and structure that makes sense to you regardless of the tools you migrate through.
- Zim-Wiki for items or procedures that I refer to or repeat often. Zim-Wiki is mostly plain text and transportable, but handles embedding small screenshots. I keep another Zim-Wiki notebook for small projects or investigations. - A simple text file list for in progress items or projects that I am working that have more or less an end date or specific goal - A simple text file list for to-do items, vague plans, and links to check. This file changes almost daily. - A simple text file list for wish list items and purchase ideas > syncthing on all my devices to keep all them all current
In my paid work I have a few additional things, but not much more. The most important is a separate subdirectory for each project's files. Structure it so that it is ready to use in a retrospective repository when finished. Refer back to it often when planning similar projects.
I used to "hoard" knowledge, had a large library, sets of sorted bookmarks files, etc., but I'm finding that I need less and less of that. I think the biggest change took place when I made a short project once with the goal of making my home computing portable and self-hosting. That really simplified a lot.
A big help is being consistent in a format and structure that makes sense to you regardless of the tools you migrate through.