What I’m trying to do
- simplify my notes (pages) structure and automation
- use url/web/http type querysting parameter & value passing
- have a layer of abstraction between navigation, indexed lists, and content
Things I have tried
I’ll try to simplify; for example:
if I there is an index page which lists Animals,
when I click on the list item link for Dogs, it goes to a second page which shows a picture of dogs, and has embedded search results showing all notes with the tag:#Dogs
so the first page, lets call it “Animals”, would have a bullet list of items, kinda like:
* [Cats](obsidian://file=Details?value=Cats)
* [Dogs](obsidian://file=Details?value=Dogs)
* [Giraffe](obsidian://file=Details?value=Giraffe)
and the second page, lets call it “Details” has:
* a heading with code like ###<%=value%>
* an image with the code like ![](attachments/<%=value%>.png)
* an embedded search query with code like ```query tag:#<%=value%>```
I can go back to the index “Animals” page, click another list item option, eg. “Cats”, and then it goes to the same second page “Details”, which will shows content for cats
this way, in this simplistic example, there is only 2 pages: index and details… and then all the notes
is this kinda thing do-able? is there another way? or am I barking up the wrong round-about
(I know the coding is wrong for Obsidian, but I formatted to try explain my question)