they start off as less but are compiled to css when bundled with our template

you can use this package to generate css for ant -> https://www.npmjs.com/package/@emeks/antd-custom-theme-generator

Thanks! Tried that just now, generated a theme where everything is red, put that in assets/ and it loads find through the custom header, but then it's just overriden by light.css (which I expected). How can I have it for example load after your css? I can think of one way but it's a bit hacky, not sure if there's a better way

Have you done this before and it worked?

(yeah just checked, custom header is included well before all the default css ... sorry this should probably be a thread)

I guess since this is temporary, for now I'll just modify .next/pages/_app.tsx directly (there's still some custom light stuff outside of that for the DendronTreeMenu under .next/styles/scss/main.scss, but I guess I'll fix that case by case with some !importants, forgive me lord)

heh, sounds good. will ping you when we have the custom header fix

I too use Netlify process, so I am not timing the build (Cause it is happening on netlify server, plus it is beyond my control) Before that I used to run the CLI build locally, and I think it is slower than 11ty based build. (Still 40 mins seems too long.) Has anyone else noticed this ?

@User Can you share how to theme Published Dendron pages, when you are successful ? TBH, I also do not like the current theme. I liked 11ty based on better 😄

FWIW, it looks like "older" style get rendered briefly, and then newer one is superimposed second later. There is enough lag that I can notice two "rendering" Is it possible then to keep the older style ? @User

Certainly! I've already figured it out, will write a note to document how and publish it on my newly themed pages and send 😁

I found out why this happens too, and how to fix it (it was bothering me because the light theme would show up before my theme shows a second later)

Is it possible to enable showing backlinks in the preview? (In the content preview - I am aware of the Backlinks panel)

not yet. feel free to submit a feature request for that

Is there any documentation for front matter besides here? https://wiki.dendron.so/notes/ffec2853-c0e0-4165-a368-339db12c8e4b/ I'm looking for info on things like

stub

and

isDir

Also trying to understand the meaning of the book icon in the nav panel? Does it mean "this is part of a schema"?

that’s the main doc. ‘stub’ is an implementation detail of notes that will go away soon (it means that this note originally was a placeholder). same with ‘isDir’

yes

Here's that write-up https://amar.io/memo/notes/lr2RxTLuy85mXFFN24lQ8/ though I'm still in the process of figuring things out!

What does it mean to the reader looking at a published garden? Since it's part of the nav panel in nextjs-template too

Sorry to flood with questions today, but one more thing: how can I go about troubleshooting that the links in the generated "Children" section are missing the path prefix? Could be related to https://discord.com/channels/717965437182410783/923994998188421201/923995656899690557

this is a great writeup. thanks for putting it out there. we're working on making this less terrible in the future 😅

currently not much. we're planning on adding tooltips to show schema descriptions when you hover over the book icon. suggestions are welcome (including just toggling it off for this time when publishing)

New user of Dendron. I like the use of MD to do documentation. One big plus is it is viewable through github as a simple link to the MD file in the repo. So to read things I don't require a clone of the repo. Its about understanding what I have before I do the clone. So here is my problem: Dendron links are not linkable in Github. I could replace them with the Github repo links but than means I have to push to see my changes. unless I'm working page by page as I do now. Example: For VSCODE: The telescope is a large dobsonian reflector [[telescope-control.telescope]]. For GitHub: The telescope is a large [dobsonian reflector](./docs/vault/telescope-control.telescope.md). Thoughts?

a few thoughts - we're compatible with github wiki which uses the

[[ wikilink ]]

syntax

otherwise, you can use the

markdown export

pod to export to regular markdown (automate in github action) so that you have a github renderable version of your notes available as well

Thanks

The basic problem I have with the wiki approach is the wiki doesn't follow the branching of the code. I like the idea that wiki would actually branch as the code branches. Not really your problem.

Unless of course the branch documentation is a sub note. hmmm

ah, currently we keep the docs in a separate repo that is initialized with the code