From d7d5007597e879939cd4932b010f5347b37649a9 Mon Sep 17 00:00:00 2001 From: Daniel Alejandro Gallegos Date: Mon, 21 Aug 2023 21:12:36 -0400 Subject: [PATCH] Auto saved by Logseq --- pages/[[seed]] planting guide.md | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/pages/[[seed]] planting guide.md b/pages/[[seed]] planting guide.md index 23c210f..efc79c0 100644 --- a/pages/[[seed]] planting guide.md +++ b/pages/[[seed]] planting guide.md @@ -11,9 +11,12 @@ tags:: #seed #zettlekasten #[[digital garden]] **next:** ``` - technically the first line has two `::` but [[logseq]] parses it weird so there. - - `tags::` related concepts to this one - - `prev:` something related to the concept, possibly something overarching. + - `tags::` - related concepts to this one/categorization. + - `**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. - 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.