We're working through a lot in a workshop next week but it's for documentation we want to be able to scrape so probably quite specific i.e. certain sections must only be populated with bullet points are all links to notes (maybe in a certain hierarchy), maybe certain keywords might flag up for ambiguity etc. I can share some of the stuff once we get more into it if it would be of interest

yes - please. something we want to focus on is making hierarchies more prescriptive so that you can control to a fine detail, what gets populated in a hierarchy. some examples: - a note requires certain sections - a note requires certain frontmatter - the body of a section needs to conform to a regex - the value of frontmatter needs to conform to a regex the enforcement of these constraints can be required on a per hierarchy level, with the following options: - loose: no enforcement, but autocomplete will pre-populate with these sectiosn - warn: show red warnings around any parts that don't match a schema - strict: disallow creation/commit of notes that don't conform to the constraints

Yeah that sounds perfect for what we're going for! I think we'll be using templates (with pre-populated examples) to start with. I'll share what we're planning once we have it but those sound like they cover most things.

circling back to check if anything new came out of the workshop?

Pretty much just the metadata on backlinks thing - everything else pretty much just worked when we thought about it in a dendronic way.

fyi, we'll be starting work on the custom theming this week 😇 @foureyedsoul ☝️