Auto saved by Logseq

This commit is contained in:
Daniel Gallegos 2023-08-21 21:11:36 -04:00
parent c5049106d8
commit 996263b7f7
3 changed files with 12 additions and 8 deletions

View file

@ -1 +1 @@
["6819d5ac-7c6b-4965-ba7b-e56686e61416" "e11b5282-195e-40cb-af42-af79882dc719" 545] ["6819d5ac-7c6b-4965-ba7b-e56686e61416" "e11b5282-195e-40cb-af42-af79882dc719" 547]

View file

@ -5,12 +5,14 @@ tags:: #seed #zettlekasten #[[digital garden]]
- # seed format - # seed format
- id:: 64e3fb8f-7148-427c-837d-4a38f70293a2 - id:: 64e3fb8f-7148-427c-837d-4a38f70293a2
``` ```
tags: tags: #whatev
prev: **prev:**
[content] [content]
next: **next:**
``` ```
- technically the first line has two `::` but [[logseq]] parses it weird so there. - technically the first line has two `::` but [[logseq]] parses it weird so there.
- `tags::` related concepts to this one
- `prev:` something relayed
- this allows us to [[hyperlink]] to another related concept, keep engagement with another, related idea, and give it metadata to sort through. nothing more, nothing less! [[keep it simple]], part of [[lazy engineering]]. 😎🤙 - this allows us to [[hyperlink]] to another related concept, keep engagement with another, related idea, and give it metadata to sort through. nothing more, nothing less! [[keep it simple]], part of [[lazy engineering]]. 😎🤙
- the reason why tags are at the top is to take advantage of [[logseq]]'s built in tagging system. :3 - the reason why tags are at the top is to take advantage of [[logseq]]'s built in tagging system. :3
- we use a logseq [template](logseq://graph/garden?block-id=64db7d5e-9da5-432a-aa11-f97ae5d113ec) for this, too, for ease of use. - we use a logseq [template](logseq://graph/garden?block-id=64db7d5e-9da5-432a-aa11-f97ae5d113ec) for this, too, for ease of use.

View file

@ -5,13 +5,15 @@ tags:: #seed #zettlekasten #[[digital garden]]
- # seed format - # seed format
- id:: 64e3fb8f-7148-427c-837d-4a38f70293a2 - id:: 64e3fb8f-7148-427c-837d-4a38f70293a2
``` ```
tags: tags: #whatev
prev: **prev:**
[content] [content]
next: **next:**
``` ```
- technically the first line has two `::` but [[logseq]] parses it weird so there. - technically the first line has two `::` but [[logseq]] parses it weird so there.
- `tags::` - `tags::` related concepts to this one
- `prev:` something related to the concept, possibly something overarching.
- `[content]` - you know, whatever the seed contains.
- this allows us to [[hyperlink]] to another related concept, keep engagement with another, related idea, and give it metadata to sort through. nothing more, nothing less! [[keep it simple]], part of [[lazy engineering]]. 😎🤙 - this allows us to [[hyperlink]] to another related concept, keep engagement with another, related idea, and give it metadata to sort through. nothing more, nothing less! [[keep it simple]], part of [[lazy engineering]]. 😎🤙
- the reason why tags are at the top is to take advantage of [[logseq]]'s built in tagging system. :3 - the reason why tags are at the top is to take advantage of [[logseq]]'s built in tagging system. :3
- we use a logseq [template](logseq://graph/garden?block-id=64db7d5e-9da5-432a-aa11-f97ae5d113ec) for this, too, for ease of use. - we use a logseq [template](logseq://graph/garden?block-id=64db7d5e-9da5-432a-aa11-f97ae5d113ec) for this, too, for ease of use.