79 private links
Extensive description of concepts and uses of org-mode.
I don't use org-mode personally (the syntax falls just into the uncanny valley of markdown-like) but this covers concepts as well as uses, so might be useful outside a strict org-context as well.
Proper project management with Taskwarrior in vim. - tbabej
Todo vim integration discussion; different systems from paper to file-system oriented to org-mode to plain markdown discussed
python taskwarrior api. Contribute to ralphbean
Apparently the most mature Todoist CLI (and most well known , going by stars)
other options:
The fastest wiki and knowledge base for growing teams. Beautiful, feature rich, markdown compatible and open source. - outline
Clockify is the only completely free time tracking software for teams.
Free toggl alternative - possible to self-host
So many todoist guides / templates / ideas / integrations
Using taskwarrior allows easy editing, viewing, exploring workflow through vim
similar to todoist in some ways
Time-tracker with server/agent components. Open source and coming along somewhat nicely.
Plugins for e.g. editor (vim) and terminal already exist but I have not tried them extensively.
Could integrate nicely into personal data scraping pipeline.
Useful Apps
In a structured tagging system, children should automatically receive the tag from parents as well.
Example:
Programming > JavaScript
Programming > Css
Anything tagged either js or css should automatically receive the appropriate parent tag.
Tags and folders
Tags are essentially virtual folders already
So, tags should have the option to be turned into 'primary tags' or folders via a checkmark
Any item can only contain one primary tag
All child/parent tags will be converted to primary tags (essentially making that trunk of the tree a folder trunk)
A parallel folder structure will be created for all the tags under which the files tagged with the tag will now live
If a file results in multiple primary tags after turning a tag into a primary tag either
- conflict has to be decided manually, and only selected primary tag is kept
- both tags will stay on item, it will exist in one directory as actual file, in one as symlink to actual file
Tags can be 'related' to one another not just through child/parent but sibling (or 'cousin') relationships, though i dont know how this wouldbe visualized / affect the structual tree