I haven't gone too deep on this myself, but could you consider these as separate fields in frontmatter (synonym: [[link.to.page]])?

It's valid yaml and would give you some nice backlinks. There's not too much tooling based on the frontmatter yet but could be a good way to do this.

I've already got a few

author.{name}

pages since I'm working on a dissertation. For whatever it's worth, Dendron's backlinks panel doesn't currently seem to recognize wikilinks in the YAML header, but it does when the same link is in the body of a note. To be more clear, I tried

author: [[author.hooks-bell]]

in the YAML header and it didn't show up in the backlinks panel even after reloading the window. But in the body of the same note, [[author.hooks-bell]] did show up in the backlinks panel. Is that the current expected behavior? If so, are you saying that might change in the future?

ah, I see - probably because we parse the frontmatter differently than the rest of the notes. Might be tricky to change but I do think it's expected behavior to have the frontmatter be able to reference other notes. @User

Hmm...Will ponder on this and come back later.

If it's useful for your "workflow" question, in practice I've been putting "metadata" header either at the top or bottom of a note, to at least keep this sort of thing tidy. I'm mostly familiar with YAML just from using Jekyll, so I don't know how Obsidian or Roam use it in comparison to Dendron. But I can definitely see how it'd be useful to make connections that aren't in the body of a note.

Been thinking, experimenting and writing some notes of this. The summary is: - There is no right or wrong way of doing this, however there are some principles that seem to emerge - Keeping track of the "Who, When, Where, What, Why" seems to make sense for most notes. (i.e. information source, and information sinks. Where you found the information and where you intend to use it. eg. source: discord.dendron.questions, sink: article.classification.bestpractices. Identifying patterns can also be constructive, such as [author].[book].[chapter].[page]) - Depending on the context of a note some "W"s will be more relevant than others. (i.e. For a daily journaling, "When" and "Where" (geographic location) will be more relevant.) (Realising all "W"s are important, but that some are more relevant depending on context is refreshing because it brings some clarity and consistency to how we tag notes.) - I use a combination of hierarchies, tags and keywords. (Which end up all being pretty much the same in Dendron, yet are conceptually (or purposefully) different. i.e. they serve different purposes in my mind.) - Building a "Lexicon" upfront provides a lot of clarity on what really matters to you and what hierarchies would make sense. (i.e. Categorize words by "Aspiration", "Role", "Interest", "Topic", "Project", "Goal", "Book", "Author" etc...) (Most of the hierarchies emerge inside the "Topic" category, but are not limited to that category.) - The great thing is that we are entirely free to design what works best for ourselves. There are no rules. We are only limited by our imagination. Experiment and make the most of it 🙂

Hey all, I'm very confused when attempting to setup basic links. I started using Dendron on mac and I'm hitting CMD+L, typing in the name of the file I want (lets say disney) and it will only ever generate the schema file. It won't let me generate markdown files under any circumstances except for CMD+I (for a new note). So I am quite confused on how to do things like the video tutorials

Are you trying to make a new regular note, something like

disney.movie.moana

? I think CMD+SHIFT+S is the default for that. CMD+SHIFT+L specifically looks up schemas (or lets you make new ones). Does the bar say

Lookup (schema)

or

Lookup (note)

?

Lookup Schema. CMD+SHIFT+S is definitely lookup note. Ok, yeesh I thought I was going crazy - thanks!

Could someone point me to documentation describing how to publish a part of my notes hierarchy as a page? for example if I have

pro.example.docs

,

pro.example.docs.page1

and

pro.example.docs.page2

and I want a static page with

pro.example.docs

as root

so if you want to only publish your

pro

hierarchy, you should do

yml
site:
    siteHierarchies: [pro]
    siteRootDir: docs

thanks, but how can I create multiple pages on different domains? for example

pro.myproject

and

pro.example

but I don't think you can make

pro.examples.docs

as root

oh ok

So maybe just create a new workspace instead?

new workspace?

yes, so that I can have multiple web sites

yeah

hmm

i could make a little script which copies all files from a specific hierarchy to another workspace, then refactors their hierarchy and builds a simple page

yeah I think so since in this case you seem to already have a site containing the hierarchy you want to make a new site

yeah, the mental model is that every vault is a git repo so you can mix and match vaults per workspace and use a different dendron.yml to publish

here's a guide that can help you do that: https://wiki.dendron.so/notes/401c5889-20ae-4b3a-8468-269def4b4865.html#converting-a-local-vault-to-a-remote-vault

how can I specify a different dendron.yml with another sitefor every vault? Aren't they all built to the same

WORKSPACE_ROOT/build

folder?

this would be a diff dendron.yml for diff workspaces

you would be using the same vaults with diff workspaces and diff configurations within each workspace

hmm, in my mind, I want to do something like this:

yaml
version: 1
vaults:
  - fsPath: vault
  - fsPath: example.com
  - fsPath: docs.hello.world
useFMTitle: true
noLegacyNoteRef: true
sites:
  - siteUrl: "https://example.com"
    copyAssets: true
    siteHierarchies:
      - root
    siteRootDir: docs
    usePrettyRefs: true
    title: example.com Docs
    vault: example.com
    buildOutputDirectory: build/example.com
  - siteUrl: "https://docs.hello.world"
    copyAssets: true
    siteHierarchies:
      - root
    siteRootDir: docs
    usePrettyRefs: true
    title: docs.hello.world Docs
    vault: docs.hello.world
    buildOutputDirectory: build/docs.hello.world
initializeRemoteVaults: true

got it. yeah, that's something I want to add support (it just hasn't come up much until just now) there are a few ux quirks to work out (eg. currently if you run

copy note url

, its easy for us to generate the url based on the

siteUrl

. if you have multiple sites, this might require a dropdown) can you submit a feature request so we can track it in our roadmap? https://github.com/dendronhq/dendron/issues/new?assignees=&labels=&template=feature_request.md&title= in the meantime, i would use the workaround of multiple workspaces but same vaults until we get this implemented.