Thanks for opening the issue. I have started a GitHub discussion here about tutorial feedback, feel free to add into the conversation too: https://github.com/dendronhq/dendron/discussions/1756 I'll be reviewing/revamping what the Tutorial involves, and tracking what does/doesn't work, etc.

dendron-publish-latency

What project is this?

I bind ctrl enter cannot remember why I did that instead of cmd enter

What are these

{ ctx: 'procRehypeFull' }

messages? I'm using Node.js 16.13.0.

It should be sufficient to point to the obsidian directory as your Dendron vault. You only need to run

Dendron Doctor

with the

fixfrontmatter

subcommand for Dendron to create ids and recognize the notes. I use my Dendron vault on mobile with Obsidian and it works nicely

I'm in the same boat as @foureyedsoul using Dendron as my note taking app of choice with no publishing since almost a year if I recall correctly. It's been very stable and dependable for me. Only very now and then I encountered a hiccup but the community and @kevins8 are super helpful. The main USP for me are the hierarchies and in particular the lookup. It was never as easy to find notes again

@User awesome...thanks for that info

@User hmm....pointing at the existing directory created a vault and seeds directory there but it doesn't see my md files. Should the md files be moved into vault?

Ok, moving the md into vault works. But now, of course, the obisidian mobile client still creates new notes in the parent directory. hmmm...

Hello everyone. I hope everyone is doing well. I'm trying to use some of the keybindings from a Treehouse talk from @User and have placed them in the correct place. All of the keybindings work just fine with the exceptions of the items that are calling the command

dendron.lookup

. I'm not sure what is misconfigured. Here is a full keybinding entry for reference.

{
      "key": "ctrl+s s",
      "command": "dendron.lookup",
      "args": {
        "noteType": "scratch",
        "selectionType": "selection2link",
        "noConfirm": true
      }
    },

When using this keybinding I get the following message.

command 'dendron.lookup' not found.

Does anyone have any ideas what I'm doing wrong?

ok, I've reinitialized Dendron to the parent folder and added the Obisidan vault as a vault to Dendron. I think this is the way

Figured it out. The command changed. It is now,

dendron.lookupNote

.

hey @User , thanks for taking the time to go through the tutorial. probably the biggest issue in dendron right now is that the feature set changes pretty quickly and documentation (eg. tutorial) gets out of date fast

@User what's your workflow on this? Just occasionall run fixfrontmatter on new notes created by obisidan?

@User no worries and thanks. glad to know it wasn't me 🙂

its an area of work. this is why we've done a refactor of our docs (https://wiki.dendron.so/notes/NWuXh9ZreX3XKI6NhRIBJ.html#wiki-site-reorg) and why @User is building a new getting started experience

hey @User I finally moved over from the previous publishing pipeline and I'm encountering this too. the DOM shows Katex-mathml next to Katex-html. Not sure why both are showing up but I'm about to look into it

I made a bug report on Git earlier https://github.com/dendronhq/dendron/issues/1746

ty!!

Does anyone know of a VSCode extension that lets your annotate text/write comments similar to how you can comment on content in MS Word/Docs?

katex-in-publishing

Sort of. There's a syntax / extension to Markdown called "CriticMarkup" that some people use for making annotations in Markdown. The annotations are still right there in the text file (not separate, like comments in MS Word or Goggle Docs), but they don't have to appear when you render the Markdown file in a different format. Here's an extension for it in VSCode: https://marketplace.visualstudio.com/items?itemName=jloow.vscode-criticmarkup Here's the current page for CriticMarkup itself: https://github.com/CriticMarkup/CriticMarkup-toolkit

absolutely. see https://wiki.dendron.so/notes/nB75cmdPhL7CTOATG6wpT.html#4-first-class-web-experience

I thought the critic markup project was abandoned? How is the extention in practical use? Another one that is somewhat relevant is this: https://marketplace.visualstudio.com/items?itemName=aaron-bond.better-comments

done here https://github.com/dendronhq/dendron/issues/1769

I think this is because the default command palette tries to clone and build the nextJS template every time. Install the dendron CLI and directly run

dendron publish export

to get around this (https://wiki.dendron.so/notes/yg3EL1x9fEe4NMqxUC3jP/)

Is there a way for Dendron built websites to support latex/katex macros? Currently just dumping all macros

\newcommand

near the top of the document, which pandoc can interpret and render correctly as macros. This is rendered as messy plain text in dendron built websites

Yes I have a "morning routine" that syncs the git repos, run the doctor command to fix front matter and then create a new daily journal note

Is it possible to allow specify a macros field in say, the Dendron yml, which gets passed onto Katex rendering options? https://katex.org/docs/options.html