✅ SEP 4: Add taxonomical types alongside tags
Status: Finished
Date: 2023-04-16
Commit: 12af74e3bc8f3ff029344ddca7681dc27be55ef0
Code complete
Currently the site has the concept of tags, a document can have any number of tags, and can define new tags at will. These serve as the primary taxonomical tool. By convention I make the first tag the major one, corresponding to one of the major streams of this site: meta, nonsense, notes, journal, journeys, pearls. Later tags are of lesser significance.
Formalising this distinction could allow for more robust/predictable taxonomical behaviour.
This more explicit meta hierarchy could partially assist with breadcrumb
navigation by introducing the option to ‘breadcrumb’ in the form
type / tag[0] / title.
Possible names for this new metadata element: type,category, group, set, stream.
Possible issues
Some future document may not neatly fit into a ‘type’. This seems unlikely as the types are sufficiently distinct and broad.
Although, what about the pearls newsletter. Is that type: pearls or type: newsletter? Probably the latter, tagged ‘pearls’.
There are other cases that need settling too. Are ‘changelogs’ and ‘proposals’ their own type or are they notes tagged with ‘changelogs’ or ‘proposals’? Again, I lean toward the latter.
These ‘types’ will need to be clearly and strictly defined, with concise descriptions for future reference so there is never any doubt as to whether a new type is to instantiated or simply a tagged node beneath a type.
Types Classes (not required)
misc
index
note
general
meta (might need to make this a tag not a class, as both proposal and changelog would be considered meta I think)
proposal
changelog
belief
question
recipe
essay
manual (may get rid of)
list (may not create, as I prefer creatign lists through taxonomies)
glossary (want to get rid of this)
journal
regular
now
nonsense
journey
drawing (will drawing be a tag AND a class??!)
reflection (possible new class (or should it be a tag?) for when I'm looking back on a time)
letter
newsletter?
pearls
reference
quote (raw quotes, without my own notes, my notes should be made in a note that links to or transcludes the quote)
link
book
poem
film
letter
art
definition (for defining terms/words, to replace glossary)
So we have hierarchy that goes as follows: type: class: tags… sort of.
All documents must have a type and a class, classes can be thought of as
sub-types. Classes belong to types. Conversely, tags are completely optional,
and unlike type and class, tags can be multiple/plural where type and
class may have only one value each.
The ‘note’ and ‘journal’ types will not be required to ?what about what is now the journal tag? Should those documents simply have no tag? That could work. In the same way, notes need not be required to have a tag.
For pages where ‘class = index’, could switch ‘type’ to the most appropriate of note/journal/reference/ etc
Index pages don’t get tags?
change ‘collection: type: …’ to ‘collection: style: …’, then a collection can be comprised of types, and/or classes, and/or tags
