Haven't been around for a while, just wanted to say that progress is really coming along and I appreciate everyone's hard work.

yeah, its been a minute. happy to see you back @User 🙂

Wow, auto-complete in the lookup! 🎉

it took some doing but we found a workaround. credit to @User for the implementation 🙂

Just wanted to shoutout to all dendron's team for their kindness in answering promptly and clearly in the #735365126227493004 channel!

@User! It's CROP time 🙂 Please vote for your favored crop 👨‍🌾👩‍🌾 1. [Prompt user with more information and possible actions when using

Dendron: Delete Node

· Issue #963 · dendronhq/dendron](https://github.com/dendronhq/dendron/issues/963) 2. [Vault rename command · Issue #840 · dendronhq/dendron](https://github.com/dendronhq/dendron/issues/840) 3. [Interactive checkboxes in Dendron Preview · Issue #1828 · dendronhq/dendron](https://github.com/dendronhq/dendron/issues/1828) 4. None of these (if there's an issue you'd like to add to rotation, please reply with a github issue) To vote, respond with a 1️⃣ 2️⃣ 3️⃣ or 4️⃣ to this message. voting closes Monday at noon Pacific Time

this was a close one with votes across all issues. we'll be picking up 1️⃣ for the next CROP. thanks everyone for voting 🙏

Hi, I'm playing with site publishing and had a number of UI issues in the resulting site. Have detailed them out with screenshots here: https://github.com/dendronhq/dendron/issues/1871

I also think that the documentation at https://wiki.dendron.so/ could be improved to resolve the following issues 1. If you go to https://wiki.dendron.so/ and only look at the content in the left sidebar, there seems to be no entry for Publishing at all (unless I'm being blind. That's possible). I only found the publishing page at https://wiki.dendron.so/notes/4ushYTDoX0TYQ1FDtGQSg/ by dumb luck, because I already knew that Dendron supported publishing. There seems to be no way to get to https://wiki.dendron.so/notes/4ushYTDoX0TYQ1FDtGQSg/ from the left sidebar at https://wiki.dendron.so 2. I then noticed that a lot of useful stuff is at https://wiki.dendron.so/notes/7a7af2fa-b9d0-4adc-81e6-f03186123539/ . However, there seems to be no way to get to that page from the left sidebar at https://wiki.dendron.so 3. The left side bar at https://wiki.dendron.so has 'User Guide', 'Guide', 'Concepts' as top level menu entries. It is not immediately clear what the differences are. E.g. What is the difference between 'User Guide' and 'Guide' ? These could be all merged under 'User Guide' or could have more descriptive titles. Also, I'd have expected that at least one of these have 'Publishing' as a sub-link in the left bar, but they do not.

Wiki site reorg

I posted this feature request for word counting and beyond. It is a very common need to have to write to a target: 50-word bio, 100-word abstract, 250-word synopsis, etc, etc. Text statistics and analysis is a potentially interesting topic beyond the very basics so it would be interesting to hear opinions. Please upvote if you also would find this useful... 🙂 If there are tools for this I do not know about, please let me know... https://github.com/dendronhq/dendron/issues/1887

@User the issue with table of content links wrapping should be fixed now

Thank you very much!! I can confirm this is working 🙂 In future, would you like me to create separate issues i.e. 1 issue in github per actual issue? In the issue I reported earlier, there were 4 distinct issues (all related to publishing enhancements) and I don't know if that is good practice.

separate issue will make it easier to manage 🙂

Should I edit the existing issue, break it out into 4 separate issues, and then mark the one you fixed as done?

we can manage with the existing one. just for future reference

👍

Hey @User , I don't mean to bug you too much, but if you can, could you please expedite the fix/enhancement that in the ToC of the published pages, there is visually no distinction between e.g. an H2 header and a H3 header? This is part of Issue 1 in https://github.com/dendronhq/dendron/issues/1871 and the 'Expected solution' section gives an example solution. I'm only bugging you because maybe this is something you could fix in a few minutes i.e. it might not be a huge lift compared to other features you are building? As a way to thank you in advance, I present you with a pretty obscure (and low intensity) bug as follows: When you do

dendron publish dev

in rapid succession, sometimes the pages show up at localhost:3001 instead of localhost:3000 (maybe because port 3000 is still "busy" from the previous attempt?) That's not a problem. The problem is that

localhost:3000

seems to be hard-coded as the URL for the site title in the top left corner, even when the site is being served at localhost:3001. See the annotated screenshot below for a better understanding of this.

yep, have a fix for this. should be ready to ship if not this week then the following

as for the localhost, for development, its currently 3000. we have a backlog item to make it configurable

Hey, great app. Would be great to create a note within a hierarchy without typing the whole path. Any shortcut / command I am missing?

I think I asked this a while ago and if you have a note open when you press Ctrl-L you get that address in the lookup to edit. But if you fuzzy search for a note you can’t pull any of the search results in to edit, a VS code limitation. A Workaround is to search for a note in the desired place in the hierarchy and open it, then Ctrl-L will bring that note path up to edit for the new note

There's also tab autocomplete - so if you type a little bit of the hierarchy, you get a lookup result - you can then hit 'tab' to bring up the top result into your lookup bar. You can also select a particular item in the quick pick with arrow keys, hit 'tab' and it will autocomplete

Well, encountering the issue

page build failure

with GitHub Pages, leads me to publishing methods via Netlify. TIL that with this Netlify workflow, I just need to push updated contents to GitHub repo by

Dendron: Workspace: Sync

, and all of the built process will be executed automatically by Netlify. Much better, both in execution time, number of keystroke, size of local folder on disk and manual effort, vs the workflow of publishing via GitHub Pages. Thank you who took time and wrote the tutorial in details with gif screen cap. Imho, this is a tutorial written under a newbie's point of view. Awesome! 😄 https://blog.dendron.so/notes/7h7zZkjF4Yqz8XSrHS1je/

I think the Graph view can be very useful in multiple settings but it needs a bit more power. So, I created this issue with the relevant suggestions). It would benefit from discussion and further ideas. Please upvote on GitHub if this seems useful and add. For reference, this blog post is interesting: https://medium.com/geekculture/2-big-issues-that-roam-should-have-fixed-long-time-ago-4a9a1ff47c0f https://github.com/dendronhq/dendron/issues/1945

Hi folks! Thanks to all the team for this amazing tool. I've noticed that the autocomplete lookup ceased working after switching to my MacBook for holiday (pressing TAB wouldn't trigger completion). At first, I thought MacOs was the issue, but I then tried reverting VSCode extension from 0.73.1 to 0.73.0 and it worked again! Am I the only one to experience this issue?

Thanks for a wonderful app, it's great, but it needs more tutorials for beginners, it's really hard for first timers. I have used oneNotes, Notion, Obsidian and currently I'm using logseq. Logseq is an open-source standalone application have similar file system & md files as yours. If possible, Please add support to use my previous logseq notes. Thanks.

i think this has to do with missing settings in dendron.yml. i pasted a blank one below. can you make sure all the keys are present?

yml
version: 4
useFMTitle: true
useNoteTitleForLink: true
mermaid: true
useKatex: true
dev:
    enablePreviewV2: true
site:
    copyAssets: true
    siteHierarchies:
        - root
    siteRootDir: docs
    usePrettyRefs: true
    title: Dendron
    description: Personal knowledge space
    siteLastModified: true
    gh_edit_branch: main
    duplicateNoteBehavior:
        action: useVault
        payload:
            - vault
commands:
    lookup:
        note:
            selectionMode: extract
            confirmVaultOnCreate: false
            leaveTrace: false
            bubbleUpCreateNew: true
            fuzzThreshold: 0.2
    randomNote: {}
    insertNote:
        initialValue: templates
    insertNoteLink:
        aliasMode: none
        enableMultiSelect: false
    insertNoteIndex:
        enableMarker: false
workspace:
    vaults:
        -
            fsPath: vault
    journal:
        dailyDomain: daily
        name: journal
        dateFormat: y.MM.dd
        addBehavior: childOfDomain
    scratch:
        name: scratch
        dateFormat: y.MM.dd.HHmmss
        addBehavior: asOwnDomain
    task:
        name: ''
        dateFormat: ''
        addBehavior: childOfCurrent
        statusSymbols:
            '': ' '
            wip: w
            done: x
            assigned: a
            moved: m
            blocked: b
            delegated: l
            dropped: d
            pending: 'y'
        prioritySymbols:
            H: high
            M: medium
            L: low
        todoIntegration: false
        createTaskSelectionType: selection2link
    graph:
        zoomSpeed: 1
    enableAutoCreateOnDefinition: false
    enableXVaultWikiLink: false
    enableRemoteVaultInit: true
    enableUserTags: true
    enableHashTags: true
    workspaceVaultSyncMode: noCommit
    enableAutoFoldFrontmatter: false
    enableEditorDecorations: true
    maxPreviewsCached: 10
    maxNoteLength: 204800
preview:
    enableFMTitle: true
    enableNoteTitleForLink: true
    enableMermaid: true
    enablePrettyRefs: true
    enableKatex: true
    automaticallyShowPreview: false

We recently rehauled out web tutorial. Have you had a chance to try it out? https://wiki.dendron.so/notes/678c77d9-ef2c-4537-97b5-64556d6337f1.html Also, we have a bunch of folks that use both logseq and dendron (eg. @User ). they might be able to chime in on logseq specific details

credit to @User