Thanks for the details @User and for filing the issue. @User - with that kind of error msg, I'm guessing it's an issue with the markdown parsing logic not being able to handle such a large file. Maybe the first mitigation we can do is to handle that error gracefully and point out to the user which files are causing issues.

Not sure if we're tracking an issue for that - i just tested it locally and am able to see images in preview. I wonder if the underlying issue is related to the other issue you filed https://github.com/dendronhq/dendron/issues/2702

Hm.... maybe. On mouse hover, the editor preview only shows icons for images for me... Or sometimes local paths

Image Rendering Issues

has anyone experimented with converting bibtex citekeys to HTML when publishing a vault? my experience with development is limited, but could rehype-citation (https://github.com/timlrx/rehype-citation) be added to the process handling markdown to html? would probably conflict with how remark-rehype handles footnotes. something I will experiment with, but wondering if others had tried the same.

Markdown import error

So i journal useing dendron. Not everything I do is worth keeping up on and idea board. But some things should be raised to that level, otherwise they get lost in my journal. I'm interested in how other people do it and link to their dendron journals?

i use a tag (#star) to highlight important lines. then use backlinks to go over them

block references can be nice for this

I have a hierarchy tree as follows

yaml
- root
    - blog
    - notes
        - public
        - private1
        - private2

What is the most easy to organize config, to publish all except the two

private1

and

private2

nested hierarchy nodes? If I config like below, will it work?

yaml
publishing:
    siteHierarchies:
        - root
        - blog
        - notes
        - private1
        - private2
    hierarchy:
        private1:
            publishByDefault:
                vault-name: false

i think the eaisest way to seaparate private and public stuff is with separate vaults.

woah i have a color???

WHEN DID THIS HAPPEN????

It's because you caught a bug! 🪲

i did smash a mosquito with my bare hands earlier 👉 🎯

today has been a very brain-numb day for some reason

i've had a few superficial ideas, but nothing of substance

woahhhhh

this just autocompleted two levels deep

this is majik

Well i read over some hiccup in cross vault references. So i hesitated to use multi vault setup. And the deprecation of workspace is also under investigation. Seems many things that I don’t understand clearly.

sure i can do that - i will have to find my old github account or make a new one so there will be some delay probably until the weekend but ill file a ticket

Hello, I've questioned this on the chat channel, hope it gets more attention here properly. Do you know how can I enlarge the font on the Preview?

Hi @User - other than scaling the resolution of your entire VS Code, I don't think there's a way to adjust the resolution of just one window like the preview

I have a hierarchy tree in a vault named as

vault-name

as follows

yaml
- root
    - blog
    - notes
        - public
        - private1
        - private2

I would like to publish all, except the two

private1

and

private2

nested hierarchy nodes. Here is my first attempt with

dendron.yml

, but it does not work, since everything is published

yaml
publishing:
    siteHierarchies:
        - root
        - blog
        - notes
        - private1
        - private2
    hierarchy:
        private1:
            publishByDefault:
                vault-name: false

What is the current config to achieve my publishing target?

when custom preview theming is implemented, I imagine you'd be able to use it for this

is all of the frontmatter required in dendron? if not, is there a way to only generate frontmatter for what is required i.e. the ID? do self contained vaults change the necessity for unique id, and is it possible to use the filepath as unique id in that case? if title and description are optional frontmatter, is it possible to use the kebab-cased-filename as a title in dendron published sites?

All the front matter you get when you create a new note is required I think. You can generate the front matter with "fixFrontmatter" doctor action: https://wiki.dendron.so/notes/ZeC74FYVECsf9bpyngVMU/#fixfrontmatter

we do want to support filepath for published sites - the reason we currently don't is because the links would break on refactoring

has anyone experimented with working with dendron in alfred? I am going to look into the dendron cli but curious if anyone has any existing experience or projects going on