thanks for the pointer, I'll try messing with it to see if it is something that would work for me

any idea why some hierarchies don't show up when I do a site preview?

overall it is not really reacting on me changing stuff

the site preview from the plugin is not live (we're working on it). if you want the life preview, you can use the cli: https://wiki.dendron.so/notes/1399b5d2-28fb-4077-aa5f-c8edbe52bc5d.html#local-preview

I don't need it live, I'm fine with stopping it and running it again. But things do not change even after that

but if i do a preview from cli it works, odd

its a known issue that we're addressing 😅

oh! Looks like I misunderstood. cli works well 🙂

Hello Dendron people (do I call you dendrites?) -- I have a quick question: If I have a pre-existing Obsidian vault what does the migration process look like? Is it possible to simply open the vault in Dendron and slowly hierarchicalize the notes over time by treating original notes as root-ish level notes?

dendrites works 🙂 we have a migration guide here: https://wiki.dendron.so/notes/f9b4fc21-7613-4c8a-9257-cec4c06b67f9.html#obsidian dendron looks into vaults one folder deep and creates hierarchies using dot delimited filenames so nested folders without the migration won't work right now

This will be a non-issue for me -- I was largely using a flat-file method anyway. 🙂 I am now hankering for some hierarchies. Hehe...

And thank you for the doc-link!

I have tried importing into Dendron and I have stumbled across some choke points (import crashes): -

(())

Double parens -- I can just script remove those, no worries. But perhaps useful for others to be aware of in case that is their transclusion mechanism or what have you. -

[[note#^block_id]]

Obsidian's block-level syntax creates a new note instead of linking to the block id in an existing note...Are there any intentions to support this, or is there a better means of working around this?

the double parens are because of our old note ref syntax. we'll be updating with a new default to disable that by default and deprecating it later in april when we have an automated migration script in place for users that are still using the old syntax

we plan on supporting block ids. just haven't gotten around to it 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=

Okey doke -- thank you again for the link.

Feature request added (which also mentions the fact that this feature is an import blocker): https://github.com/dendronhq/dendron/issues/560

Thanks. It seems to happen when I reload the index and navigate to the tree view. Doesn't happen every time and will take anywhere from 30 sec - 2 min to load the hierarchies. This is a new workspace I was testing on.

I might have missed this, are aliases currently not supported with note references? i.e.

![[Some note|scratch.2021.03.20.144219.test]]

or did I forget about a new config to enable this 😄

nope, they're not supported yet. your the first one to bring it up 😅 feel free to submit an issue. if your interested in taking it on, also happy to point out the places that need to change 😇

**Is there a way in dendron markdown import to specify a hierarchy under which the notes will be imported? ** I am currently in the process of importing notes in dendron and though it has imported a majority of my markdown files, some of them are still left. These are in folders that somehow the importer missed. I am now manually adding the location of these specific folders in the import yaml. The problem for me is that these notes get imported at the root level. I already have a hierarchy in mind in which I would want the notes to be added to. Is there a way to add the hierarchy in dendron's import config?

Also while writing this question it hit me that I could move all the files to another folder with the hierarchy name inside the folder to get the same result. But the option to prefix a hierarchy would be nicer.

the prefix option as been brought up before. 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 meanwhile, another alternative is using the CLI. there currently are some issues with the plugin version of importing markdown that the CLI doesn't have. you can run the following command where you

dendron.code-workspace

file is to import everything dendron importPod --wsRoot . --podId dendron.markdown --useLocalEngine see CLI installation docs here: https://wiki.dendron.so/notes/23a1b942-99af-45c8-8116-4f4bb7dccd21.html

Started using scratch notes more, and immediately found it to be useful to embed it to where I started the scratch note. I'm definitely interested in working on it and will open an issue for it. I need to survive the crunch time at work this weekend first though 😄

Created: https://github.com/dendronhq/dendron/issues/561

Is it possible to reference front-matter data through references?

Currently, does linking to a header within a note work?

Seems to work

[[#<header]]