@amilcar Hi! Sorry it’s taken so long to reply to this. I’ve been refining my process and now I think I’m at a point where I’m comfortable with the workflow.
I love the idea of publishing a knowledge base. Obsidian is a great tool for linking positive law, case law, principles etc. I hoped to at some point be able to do that, but I realised I can link many different interests that probably wouldn’t be as interesting to other people, so that project’s on hold for now
maybe someday.
If you DO publish, or wish to talk more about this, feel free to reach out! I’m fascinated by all the possibilities.
In regards to how to deal with legislation:
I’m keeping one file per law/rule/regulation. Link to blocks is a very valuable resource to linking back between articles, paragraphs, etc. Another tool is Internal link to Link to Headings, for example, a legislation might be separated into titles and chapters that you format as a heading, making it easy to link in other files.
In order to keep direct quotes separate from my own annotations, I use the Admonition Plugin. However, community plugins don’t work on Publish, so you’d have to accomplish something similar with CSS. People have shared different CSS Snippets with pseudo-admonitions on the Discord server, so you might want to check that out!
One thing that’s useful for me to keep in handy, usually within an “info” admonition or otherwise at the top of the note, is how to cite that resource. Easier than to keep referring back to Zotero!
I use (nested) tags for classification, which is a controversial topic but works for me
For example, I have “t/entity/LLC” which is “t” for Type, “entity” for genre (as opposed to, say, “authority” or “law” or “principle”) and “LLC” relating to a specific sort of entity. The “t” part isn’t really needed but it helps clean up the tag pane. For example, a law regulating LLCs would have both the tags “t/law” and “t/entity/LLC”.
I hope this helps a bit! I hope to eventually do a more detailed write-up if there’s interest.