ive been looking at quite a few documentation solutions lately. oh yes indeed lol. so i thought i would provide some learnings and internal values that i've developed in terms of what i expect out of a documentation frontend. firstly, i have learned to prioritize performance and bundle size. i think there are a lot of players who are okay at this, but I really believe svelte and astro to be above the ones that ship with a runtime like vueJS or react. astro strips away all the javascript, and svelte has no virtual dom its just a compiler. a snappy load time and experience is really important for users that I am targeting which may not have the best internet connection. next, i'm wondering if astro might be a good fit for dendron. if i get around to it with the time and figure out this HMR for the slug.filenames in the astro frontend, i'll be sure to publish a fork so others can use it. but i think astro might fit into dendron's "extend on any vertical" design tenet.

Dendron and Astro

I don't know about Astro specifically, but I've done experiments in the past using Hugo. I used an intermediate processing stage, where I treated the

.dendron.cache.json

file as a data source — pulling in notes, saving them as

uuid.md

and building the breadcrumb trail based on relations in the cache file. You could probably do something similar using a fake fetch function and Astro's dynamic route system (been a bit so I forget their exact terminology). Basically, if you're willing to do the work getting stuff out of your vault, Astro could be a great fit.