Guides
tagwerk is one Markdown file per day and a short line syntax. What that is worth depends on what you do with it — so these pages take one kind of work each and walk it through, with the price of every part named where it comes up.
The guides
-
You already have a folder of daily notes
Coming from Obsidian, Logseq or Markor: what tagwerk reads, what it adds, what it ignores and what it writes back. -
Your own sync
Nextcloud, ownCloud, Synology, any WebDAV server — what moves, what is never deleted, and what a conflict looks like. -
Hours, clients and follow-ups
Freelance days: hours as readings that add up, clients as tags, follow-ups that move themselves to the right day. -
What you measure every day
Weight, sleep, training, mood: a tag with a number after it, and what has to be true for it to count as one. -
One-on-ones, commitments, decisions
Leading a team from a personal notebook: the one-on-one you prepare by searching, what you are waiting for, what a company phone changes, and what does not belong in a note about a person. -
tagwerk at university
A semester as day files, and syncing through a university’s own Nextcloud or ownCloud. -
Your school year in text files
The homework diary, the timetable as a template, revision before a test, marks as readings.
When you want it exact
Every guide says what a thing does; the format specification says what it is — every rule of the file format, written from the parser, including the regular expressions themselves. It is the document to read if you are writing a tool of your own, or if a guide and the app ever disagree.
For anything about a purchase, a licence file or a licence that went missing, the licence page is the place.