Auto saved by Logseq

This commit is contained in:
Daniel Gallegos 2023-08-21 21:13:36 -04:00
parent d7d5007597
commit 89a1e1657d
3 changed files with 15 additions and 15 deletions

View file

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

View file

@ -1,6 +1,6 @@
tags:: #seed #zettlekasten #[[digital garden]] tags:: #seed #zettlekasten #[[digital garden]]
- prev: [[seed]] - **prev:** [[seed]]
- seeds are our word for [[zettles]], a part of [[zettlekasten]]. our methodology is to keep things simple but have enough metadata for [[logseq]] to pick up and generate the graph view from. - seeds are our word for [[zettles]], a part of [[zettlekasten]]. our methodology is to keep things simple but have enough metadata for [[logseq]] to pick up and generate the graph view from.
- # seed format - # seed format
- id:: 64e3fb8f-7148-427c-837d-4a38f70293a2 - id:: 64e3fb8f-7148-427c-837d-4a38f70293a2
@ -11,11 +11,13 @@ tags:: #seed #zettlekasten #[[digital garden]]
**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 - `tags::` - related concepts to this one/categorization.
- `prev:` something relayed - the reason why tags are at the top is to take advantage of [[logseq]]'s built in tagging system. :3
- 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 - `**prev:**` - something related to the concept, possibly something overarching.
- bolded to look pretty.
- `[content]` - you know, whatever the seed contains.
- `**next:**` - another concept to keep the flow going!
- also bolded to stand out and look pretty.
- 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.
- next: [[gardening habits]] - **next:** [[gardening habits]]
-
-

View file

@ -1,6 +1,6 @@
tags:: #seed #zettlekasten #[[digital garden]] tags:: #seed #zettlekasten #[[digital garden]]
- prev: [[seed]] - **prev:** [[seed]]
- seeds are our word for [[zettles]], a part of [[zettlekasten]]. our methodology is to keep things simple but have enough metadata for [[logseq]] to pick up and generate the graph view from. - seeds are our word for [[zettles]], a part of [[zettlekasten]]. our methodology is to keep things simple but have enough metadata for [[logseq]] to pick up and generate the graph view from.
- # seed format - # seed format
- id:: 64e3fb8f-7148-427c-837d-4a38f70293a2 - id:: 64e3fb8f-7148-427c-837d-4a38f70293a2
@ -12,14 +12,12 @@ tags:: #seed #zettlekasten #[[digital garden]]
``` ```
- 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/categorization. - `tags::` - related concepts to this one/categorization.
- the reason why tags are at the top is to take advantage of [[logseq]]'s built in tagging system. :3
- 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]]. 😎🤙
- `**prev:**` - something related to the concept, possibly something overarching. - `**prev:**` - something related to the concept, possibly something overarching.
- bolded to look pretty. - bolded to look pretty.
- `[content]` - you know, whatever the seed contains. - `[content]` - you know, whatever the seed contains.
- `**next:**` - another concept to keep the flow going! - `**next:**` - another concept to keep the flow going!
- also bolded to stand out and look pretty. - also bolded to stand out and look pretty.
- 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
- 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.
- next: [[gardening habits]] - **next:** [[gardening habits]]
-
-