Self destructing notes 💥 sounds like a fun extension.

Are the next steps/features for RFC 13 task notes decided? I'm curious about what comes next, and if there's anything I can do in terms of preparation in how I manage tasks.

@User is working on creating a note type system (https://wiki.dendron.so/notes/E8ZUvTzJ7cVOyZtqHiIKX.html) which will let people create their own notes. we're still working through the details but I can see adding hooks to the type system will make something like your ask possible

we had a team meeting on it this week and i still need to write up the followup. still in iteration but if you have any suggestions, we're actively monitoring the discussion -> https://github.com/dendronhq/dendron/discussions/1358

I just noticed that the new schema validation (nice work -- surfacing information about why they failed to apply is a huge improvement!) doesn't seem to deal with merging YAML block references -- I get "Detected invalid property "<<"". I guess this is unexpected -- would it be possible to expand those merges before validating the schema?

Hey folks, I recently added the basic "create task note" functionality, and I'm now working on improving task notes. We've had very useful feedback in the discussions already, and we'd love to your thoughts on where task notes should go from here: https://github.com/dendronhq/dendron/discussions/1358

@User! It's CROP time 🙂 Please vote for your favored crop 👨‍🌾👩‍🌾 1. [Ability to use

F2

to rename a note whose link is under the cursor · Issue #1694 · dendronhq/dendron](https://github.com/dendronhq/dendron/issues/1694) 2. [Export Markdown Preview to PDF Natively · Issue #1698 · dendronhq/dendron](https://github.com/dendronhq/dendron/issues/1698) 3. [discover broken internal links · Issue #1718 · dendronhq/dendron](https://github.com/dendronhq/dendron/issues/1718) 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

BV.User interface frustrations* 001. I am working my way through the tutorial and immediately I have a problem. I am on windows. If I am on a preview pane L brings up the lookup pane and everything is good. If I am not on a code pane L deletes a line and nothing happens. If I use shift L I am looking up a schema. If I try to follow the introduction I tend to make a schema called 'recipes' but can't make a schema called 'recipes.vegitarian' because schemas can only be one level deep. Q Is this normal? Do I have another extension or something causing grief? If this is normal how do I limit myself to the preview screen where things work? I am going to go through the documentation and offer my reactions as a QA exercise. Expect more posts like these, or tell me how I can better contribute and where? I am not hiding that I don't know this program or VSCode. I hope this makes my problems useful because others will have them too.

Tutorial 3 Links. I don't think you've had the user keep an editing window open. My choices are the code window for tutorial 3 or the preview of tut 3. Where are the instructions for the editor window I'm supposed to use? If I create a new file, which is how I open an editing space in other software, the file has no name and the [[tutorial]] instruction doesn't work.

For pdf export, is it possible to have custom page sizes? What one typically wants is the whole note on one page, not several printable pages. An 'export as one page' option maybe?

image previews are broken for me in 69.1. they do work fine in the standard vscode preview and they did work fine before. any advice?

what is the markdown you are using for the image? is this legacy preview or new preview?

I'm going to create a GitHub Discussion for Getting Started feedback, later today, to act as a friction log of feedback. I'm going to be reviewing the tutorial for refresh, and want to make sure I capture what I notice but also what other Dendronites are noticing. I'll update later today when I set it up 🙂

Hmmm I just tested, this seems to work fine with

Dendron: Show Preview

(preferred path) on VSCode

1.62.3

w/ Dendron

0.69.1

. Images look to also appear with

Markdown: Open Preview to The Side

(which is the built-in, standard vscode option). This is while using the following image format:

markdown
![Super cool image showing awesome](https://example.com/image.png)

Troubleshooting Image Preview rendering

@User When it comes to the Getting Started Guide, it's time for a revamp! Dendron has been growing 🌱 at a rapid pace, and that means revisiting and refreshing the experience for new users. I've seen a few users commenting about these tutorials, and the initial experience is really important for fellow Dendronites giving things a go. With that said, I wanted to get a GitHub Discussion going on so that I can combine that feedback with my own as I dip into reviewing the content next week. Feel free to contribute to the conversation on GitHub here 🙂 https://github.com/dendronhq/dendron/discussions/1756

thanks for checking. i have the same versions as you on two machines. one works the other does not. both show images in the vscode preview. not sure what is going on

CROP winner

👏 Thank you very much Dendron team for the recent changes and improvements to the NextJS publishing - with the code block syntax highlighting, tables formatting and various other improvements. I am now very happily using Dendron published live-in-the-wild for my client-facing documentation. And, they seem to like it too! 🙂

so happy to hear that 🙂 we have lots of improvements coming down the pipeline 🙂

I just noticed when a page has an iframe, the rest of the text on the page shrinks to about half the width of the column. Maybe that's a known thing with iframes, but I filed an issue in case it's news to you: https://github.com/dendronhq/dendron-site/issues/290 Feel free to just ignore & close it, if you already know about this wonky behavior!

Could you please reopen https://github.com/dendronhq/dendron/issues/1343 ? It's still an issue even on 0.69.

I think the new 0.70 update broke published websites Now my website looks like this:

Hmmmm I just tested out on my site with latest, seems to be working well. I did, though, make sure to do a config migration. We usually have Dendron, within VSCode, auto-update the

dendron.yml

config file, but you can run on demand too from CLI:

dendron dev run_migration --migrationVersion 0.70.0

See if that works in updating the

dendron.yml

of your workspace. I'm thinking I may add that to the release notes, when we have new migration choices become available.

0.70 publishing

I also encountered similar behavior when navigating Dendron-published sites. Though I don’t know the reason. Thanks for pointing out and raised the issue 👍

Have you already tried putting the following lines into settings.json?

json
    "vim.handleKeys": {
        "<C-l>": false
    }

this is what works for me to get that behavior

Will try, thank you!

nice catch. will take a look!

vim-keybinding-conflict