lookup isn't 100% glob pattern matching. we use fusejs under the hood. you can see matching details here -> https://wiki.dendron.so/notes/84a0366a-eab5-4862-9bef-360f92a196dc.html#extended-search-syntax

ah, that's the deprecated legacy publishing. new publishing docs here -> https://wiki.dendron.so/notes/e5st4LFLtIwwbQmC6JBaF.html

Thanks a lot! 🙂

Oh cool, I didn't know that! I don't really have a use case that I absolutely need, but for the ones I have in mind, yes, that might actually be enough.

Is dark mode w/ NextJS (possibly with a toggle) something that's in Dendron's milestones? 😅

Cool! While I do have possible use-cases, they aren't really super high priority (current workflow is e.g. running python plotting in a colab and then copying the results over, which isn't really that much work). But I was just curious, as it seems there's a lot of Momentum (and ambition) on Dendron and it's one of the features that I really liked about Org-mode. Plus, it would fit nicely with Ivo's view that the next "wave" of PKG will have not just the data (which is what Dendron currently manages), but an application layer on top of it which makes the data "alive" (my words/interpretation)

what is "title" in schema definitions actually used for? I don't see it defined on the wiki

I was trying to mimick the setup at , but my Action's jobs keep failing over an error I don't understand 😢 I don't see what could be different in both these repos that could break the CI

I guess I didn't add the .vscode folder, but I thought that was optional

Okay, maybe I'm asking something that's a bit off but I'll try nonetheless 🙂 Since I saw that with Dendron: publish export a folder with non-ignorable dimensions is created (650+ MB for just a dozen of notes) I was asking myself if there was a lightweight way to "publish". For my usecase publishing to the default github repo is enough, I'd just need the note links to be working. Is there a way to achieve this?

I'm also interested in this. Even something toward ["bear blog"](https://bearblog.dev/) style minimalism. I think I could hack something together with the markdown pods and an SSG

if I end up doing this I'll share my setup in #743194856788328497 or something

I mean, I was thinking more of something like https://github.com/dendronhq/dendron readme.md where the links link directly to the notes, using github defacto as a markdown viewer

but if bearblog does the job, please share the setup 😄

markdown pod should be fine by itself then, I'd think, since it converts all the hierarchies into folders and the links into paths

Uhm, I'm not sure I undestand, woul you please be so kind to elaborate? Shoud I go with Dendron: Publish Pod?

what I have in mind is exporting a markdown pod and pushing it to the github repo. I can't test to see if it works the way I think it does or what the steps are just at the moment

Oh, thanks 🙂 I'll try to wrap my head around on how to export a markdown pod 🙂

I confirm it works somehow, probably pushed too much and links are broken, but I guess I'll just tinker with them a bit 😄

dendron notes (which is basically markdown) will work in hugo I think

and with hugo more configuration and tweaks are available

Another stupid question: is it possible to change root.md name to something else during Dendron: Export Pod? Should be README.md for github to get it

should be easy enough to use sed or something for that

if you have a lot of references to root

Would that not entail depending on an existing node/npm install, or bundling node/npm with the flatpak? I'd like to see it in some PPA I can apt-get too but I'm not sure it's worth the trouble...

not yet in the works but yeah we have plans of doing it. 🙂

Is it possible to rename root.md to something else, e.g. home.md?

not at the moment. it will be regenerated if you try to rename it.

So it just has to be renamed after the Dendron: Export Pod (markup)? That way it shouldn't be under dendron "root-rule" anymore

after export, you are free to do any changes