Add tags similar to +project and @context tags that use the #hashtag format.
These aren't strictly part of the todo.txt style, but are a fairly ubiquitous form of tag across the web.
Do be aware: # isn't URL safe. It is a reserved character that targets title elements on a given page. The tag will be translated to URL safe string:%23.
If you want, take a look at how Twitter handles this: paths for hashtags appear in form /hashtag/Cloud
It may be time to move away from the symbol-only URLs to word representations of what those symbols represent, especially given that hashtag is also reserved by Vue Router for hash-based history. Consider paths like:
/project/someProject
/context/someContext
/hashtag/someHashtag
What this means for paths like /x (done) and /!x (not done) I'm not sure. Maybe... /closed and /open.
These are generally clearer (at least for English-speaking users) and far more extensible (plain English words can be conceived of for any context).
Then it's just a question of whether we also maintain the legacy patterns.
Add tags similar to
+project
and@context
tags that use the#hashtag
format.These aren't strictly part of the todo.txt style, but are a fairly ubiquitous form of tag across the web.
Do be aware:
#
isn't URL safe. It is a reserved character that targets title elements on a given page. The tag will be translated to URL safe string:%23
.If you want, take a look at how Twitter handles this: paths for hashtags appear in form
/hashtag/Cloud
It may be time to move away from the symbol-only URLs to word representations of what those symbols represent, especially given that hashtag is also reserved by Vue Router for hash-based history. Consider paths like:
/project/someProject
/context/someContext
/hashtag/someHashtag
What this means for paths like
/x
(done) and/!x
(not done) I'm not sure. Maybe.../closed
and/open
.These are generally clearer (at least for English-speaking users) and far more extensible (plain English words can be conceived of for any context).
Then it's just a question of whether we also maintain the legacy patterns.