^

I'd love it lol

or would the showcase be appropriate for that?

just created the #749357067843666032 channel 🙂

cool 🙂

This part of scheme of my wasn't working for me tbh I spammed namespace when it wasn't working idk how the logic works on it 😅

yaml
- id: t
  parent: root
  namespace: true
  children:
    - yoga
    - phys

- id: yoga
  namespace: true
  parent: t
  desc: Yoga General
  children:
    - r
- id: r
  namespace: true
  parent: yoga
  desc: Yoga Routines
  template:
    id: t.yoga.template.r
    type: note

- id: phys
  parent: t
  namespace: true
  desc: Exercise and work out General
  children:
    - r
- id: r
  namespace: true
  parent: phys
  desc: Exercise and work out routines.
  template:
   id: t.phys.template.r
   type: note

@User you'll get the syntax highlighting if you add "yaml" after the first three `-marks 🙂

Thanks I was wondering how the cool kids where doing it!

Dendron Newbie struggling with a question: How do you handle a thought/atomic note that is related to several different chunks in how you name based on creating heirarchies? For Example: med.prev.nutrition vs med.prev.vitamins vs med.prev.diets? What if a note relates to all three {in ones mind} at this point in time {which of course will change} In the past I have used tags. What is the best practice here? In my mind, its easier to categorize when you have some semblance of understanding. What if you are trying to understanding a topic in which you don't understand? Here is where concepts emerge and my multiple bucket problem becomes a problem for me. Thanks in advance

@User could you give an example?

@User I hope hope this helps clarify. For Example: med.prev.nutrition vs med.prev.vitamins vs med.prev.diets? What if a note relates to all three {in ones mind} at this point in time {which of course will change} In the past I have used tags. What is the best practice here? In my mind, its easier to categorize when you have some semblance of understanding. What if you are trying to understanding a topic in which you don't understand? Here is where concepts emerge and my multiple bucket problem becomes a problem for me. Many thanks

Personally in that case I'd keep the notes in med.prev, and add headings (e.g. ## Nutrition) as needed. If med.prev grows too large, it probably starts to give more hints what would be the best way to split it

speaking of which; @User what would it take to have "extract as a subnote" command for selected text? (Select some text in a note, invoke the command, give the new note a name, note is created with the selected text and the text is erased from the source)

@User interesting. So just to understand, you would keep a single note named med.prev then create subheaddings {##} My initial thought was to create multiple notes like this med.prev TitleOfNote1; med.prev TitleOfNote2; med.prev TitleOfNote3 until emergence becomes clearer.

yep, IMO keeping the text in a single place would allow easier reshuffling and spotting the patterns for further splitting

@User many thanks for the help in my Dendron journey!

np 🙂

@User Dendron Newbie struggling with a question: How do you name a thought/atomic note based hierarchal note taking in which a note/thought is related to several different other notes.What is the best practice for naming? For Example: med.prev.nutrition vs med.prev.vitamins vs med.prev.diets? What if a note relates to all three {in ones mind} at this point in time {which of course will change} In the past I have used tags. What is the best practice here? In my mind, its easier to categorize when you have some semblance of understanding. What if you are trying to understand a topic in which you don't understand? Here is where concepts emerge and my multiple bucket problem becomes a problem for me. Just wanted to get your thoughts...Do you 1. Keep a single note with ## subheadings or 2 create multiple notes like this med.prev TitleOfNote1; med.prev TitleOfNote2; med.prev TitleOfNote3 until emergence becomes clearer? I realize there is no one way to do it, but in your 10 year experience, I am sure you have worked through it in your own way. BTW...I think this would be a great blog post or newbie topic....Thanks in advance for all your work. Tom

> speaking of which; @User what would it take to have "extract as a subnote" command for selected text? (Select some text in a note, invoke the command, give the new note a name, note is created with the selected text and the text is erased from the source) @User currently, you can create a subnote out of a current line using

scratch notes

you can see a video of it here: https://www.dendron.so/notes/593206ea-5658-4874-bafd-18a138870f91.html a proper

extract as a subnote

feature is coming in september!

> @User interesting. So just to understand, you would keep a single note named med.prev then create subheaddings {##} My initial thought was to create multiple notes like this med.prev TitleOfNote1; med.prev TitleOfNote2; med.prev TitleOfNote3 until emergence becomes clearer. @User this is what I would do as well. I generally use what I call the amoeba pattern: keep everything in one note until it gets too big (this is relative to the topic, for me this is usually around 800 words) before I split it out into children notes

once i do split it out, I use backlinks and note references (https://www.dendron.so/notes/f1af56bb-db27-47ae-8406-61a98de6c78c.html) to aggregate notes into a single view

> 2 create multiple notes like this med.prev TitleOfNote1; med.prev TitleOfNote2; med.prev TitleOfNote3 until emergence becomes clearer? > @User this has generally been my approach. that's why dendron is built around the concept of iteratively updating your hierarchies via

schemas

and the

refactor command

(https://www.dendron.so/notes/eea2b078-1acc-4071-a14e-18299fc28f47.html#refactor-hierarchy).

and great idea on the blog post - i have a backlog of workflow posts that I'm planning publishing. stay tuned!

this thread inspired me to create the #749641193322971238 channel in the meanwhile 🙂

@User I am trying to figure out in what context to use which workflow. Simply speaking especially with emerging topics in which I do not yet fully understand. My bad in the past is I fall into the collector's fallacy and keep making new notes. Would be great if you could set a limit/alarm on reminding you to reflect and elaborate on your notes and stop just collecting. I think one of the points from this thread is knowing when to STOP your heirarchy and let your notes begin collecting so you can emerge your thoughts and find the clusters again. I think this is where schema's come in. I need to better understand this dendron.gettingstarted and emerge my thoughts here dendron.gettingstarted emergent thinking dendron.gettingstarted clusters This is what I am thinking

would be great to have a report that states "these notes probably have too much stuff in them, maybe split?" 🙂

@User I call these random thought notes...weeds {not my original}. {someone I remember reading } had a whole series of progressive patterns w: weeds (level 0 notes) all the way to e: evergreen notes now d: dendron/trees {maybe clusters/themes} ...need to explore

> would be great to have a report that states "these notes probably have too much stuff in them, maybe split?" 🙂 @User that's a great idea. could be an icon we could also set in the treeview/lookup with a configurable threshold set at some sane default 🙂

> @User I call these random thought notes...weeds {not my original}. {someone I remember reading } had a whole series of progressive patterns w: weeds (level 0 notes) all the way to e: evergreen notes now d: dendron/trees {maybe clusters/themes} ...need to explore @User these sound a lot like

scratch notes

(https://www.dendron.so/notes/5c213aa6-e4ba-49e8-85c5-1bdcb33ce202.html#scratch-note). i use these all over the place for thoughts that I don't have an hierarchy for or don't want to think about organizing

?? I assume, most people have 1 schema and update a single one?