Thanks! That did the trick!

😢 No it still doesn't unfortunately. With a single test vault I still get the error around GET / and multi vault complains about multiple root notes

I stumbled upon dendron just now. I am interested in knowing the structure. Does the notes if viewed in explorer be thousands of notes (after a period of time, of course) crammed into a single folder? Is the idea to never look at the explorer side of things?

So I tried playing with it again on my Windows machine and it said dependencies needed to be updated when I tried the site preview. After it updated, the preview site worked. So looks like may have been some kind of dependency issue.

I typically add a lot of images (screenshots, diagrams) to my docs. Saving all these images to the same folder just turns into a huge mess overtime. The only sane approach I have found so far is to save images belonging to a doc in their own folder. Makes it lot easier to manage.

Dendron uses dotted filenames (hierarchies) instead of folders so all the notes will be in one folder.

So the documents wont have their own folders to separate the assets

Or did I misunderstand and you wanted asset folders made for each hierarchy? 😅

@User Searched around the forum to see if there was any interest in supporting asciidocs and noticed your replies. Add me in as a big fan as well. Any ideas how complicated it would be to have minimal support for asciidoc? (I am hoping you may of keep this in mind from the start and architected things to make it doable, instead of completely impossible. If so I will take a look at it.)

I don't have a problem with all text documents being in the same folder. Just need the images and other assets belonging to a document to be in their own folder. i.e one folder per document (I create diagrams using Draw.io or TpX and then export the diagrams to png. I would like to keep all the assets that go into creating a document in one folder.)

I guess you could do that and just have the resources in the asset folder be symlinks or juctions back to the assets in the document folder, (maybe)

I was wondering about the same type of thing. Have the assets for a document in a specific folder. For example if the document is projects.my.doc.md, then the images would go in a folder called projects.my.doc.assets.

ah, you can set this in your workspace settings

add

"pasteImage.path": "${currentFileDir}/assets/images/${currentFileNameWithoutExt}",

(or name the path to your liking) to dendron.code-workspace under

settings

this will save assets to

[your vault]/assets/images/foo.bar/

if you paste the image into

foo.bar.md

${currentFileName}

is also available if you need the extension of the note to be there

yeah. so dendron has the tree view which will show you a logical view of all your notes https://dendron.so/notes/f7ebd4aa-8ba7-4bc5-bd00-a1efc5315f07.html#dendron-tree-view

got it. we'll be adding support for vault specific asset folders. dendron will just put everything into

assets

. that being said, there's nothing stopping you from creating custom assets folders today and manually creating links

we use unified to render markup (https://www.kevinslin.com/notes/601aa2f7-72f5-4663-bacc-8465bf29f3bb.html) a few ways to support asciidoc: 1) support them in code fences or custom delimeters (eg. see https://dendron.so/notes/ba97866b-889f-4ac6-86e7-bb2d97f6e376.html) 2) have markup on a workspace/note that parses ascii doc instead of markdown 2) is harder to do just because anything we implement also needs to render to html (for preview and publishing).

Thanks. @User solution will work well for me.

> is harder to do just because anything we implement also needs to render to html (for preview and publishing).

@User Just edited my previous reply and looks like Discord lost it... I mentioned I will look into the code base to see if we can add basic support to asciidocs. One of the reasons I prefer asciidoc is that it can generate clean semantic HTML pages. It also has an elegant solution to augment sections of a document with CSS classes, which can only be achieve in markdown by inserting HTML snippets inside the document (and defeats the whole purpose of a markup language, if you ask me.)

Thank you! I think that will work for me.

I'm glad 👍

Yeah, I saw that. But if I'm not on VSCode? Say, I sync it and on the other machine don't have VSCode handy or sync it on mobile. Will it be like all the notes in one folder? Is the idea here to always use lookup or search?

Good news for you: publishing works now for me. Most probably the issues were caused by an outdated config in

dendron.yml

. I created a new workspace and added my remote repos and some other required settings. The main change I noticed is that the remote repo vaults are now directly in the root on the same level as a local vault and no longer subfolders of a folder repo

yep. the nice thing with hierarchies in the filename is that you can use other editors like vim and it'll work just as well (minus fuzzy search and that you can bring back with plugins)

sweet! i was going to ask if you wanted to have a custom debug session. moving forward, we're going to be systematic about

dendron.yml

changes. we've had a bunch of migration issues from folks going from version 0 -> 1 but things should be more stable from this point

Going forward I will initialize a new workspace if something doesn't seem to work as expected to get the latest version of

dendron.yml

. I only noticed now that images aren't properly shown in the preview. Initially I thought it's a syntax issue. I use

![image](./Assets/images/foo.png)

since pandoc requires this so I changed that. Much to my surprise even afterwards the published site shows the old img src. Any idea what I'm doing wrong here. Apologies in advance: I only skimmed through the docs for publishing and didn't check discord 😬