We recently did a blog post that may be helpful, where we worked to make it more introductory and detailed on how templates work, then how to use schema for them: - https://blog.dendron.so/notes/P1DL2uXHpKUCa7hLiFbFA/ The docs version (pretty much a duplicate, based on the blog) is: - https://wiki.dendron.so/notes/5U4eAiqshI67VxIL40KWH/

Schemas are more like a type system in programming terms, although they are more like suggestions right now because they are not enforced. I think there are plans for schemas that are enforced too. I guess a template would be like a base class?

Good written piece for beginners. Thanks. Is there a way to fix the layout of a Dendron published page on mobile view? Like with your given link to wiki, i have to manually zoom in to read on mobile. But some other pages on the Dendron wiki can be read normally on mobile without the need to zoom. I hope I used the right terminology to ask 😊

I think the problem is with images, all the pages where the text is too small seem to have images in them. I'd really appreciate it if you could send a bug report for this.

hi i've just started using dendron. just a beginner's feedback

Dendron: Rename Header

does not change links if your header contains spaces

Welcome to Dendron! Rename Header seems to work for me even with spaces in the header, could you share a bit more about the bug?

Thanks for your suggestion. I have recently filed a bug report https://github.com/dendronhq/dendron/issues/2175

i had this bug when i was working on my office Windows laptop which i left in the office and will try to reproduce on Monday. In the meantime, there is an error message I keep getting on my home desktop Linux system:

{"errno":-2,"code":"ENOENT","syscall":"open","path":"1642181213165"}

. I killed VS Codium when it was unresponsive and now I keep getting this error message despite deleting and recreating the Dendron Workspace. Dendron not initializing workspace and i keep getting this error

Could you try running

rm -rf ~/.dendron*

? That should delete any Dendron files that might be left. I'd also recommend uninstalling and reinstalling Dendron. If you still get an error after that, could you run the command "Dendron:Dev: Open Logs" and then send me the output?

the fix I found was in the extension's settings... to restart codium after initializing Dendron workspace

Glad it's working now, let us know if there are any more problems!

i'm having difficulties to publish : it throws this errors: error while running command: Command failed with exit code 1: npm install npm ERR! code ERESOLVE npm ERR! ERESOLVE unable to resolve dependency tree npm ERR! npm ERR! While resolving: @dendronhq/nextjs-template@0.76.0 npm ERR! Found: three@0.136.0 npm ERR! node_modules/three npm ERR! peer three@">=0.126" from @react-three/fiber@7.0.24 npm ERR! node_modules/@react-three/fiber npm ERR! peerOptional @react-three/fiber@"*" from framer-motion@5.6.0 npm ERR! node_modules/framer-motion npm ERR! peer framer-motion@"3.x || 4.x || 5.x" from @chakra-ui/react@1.7.4 npm ERR! node_modules/@chakra-ui/react npm ERR! @chakra-ui/react@"^1.6.7" from the root project npm ERR! npm ERR! Could not resolve dependency: npm ERR! peerOptional three@"^0.135.0" from framer-motion@5.6.0 npm ERR! node_modules/framer-motion npm ERR! peer framer-motion@"3.x || 4.x || 5.x" from @chakra-ui/react@1.7.4 npm ERR! node_modules/@chakra-ui/react npm ERR! @chakra-ui/react@"^1.6.7" from the root project npm ERR! npm ERR! Fix the upstream dependency conflict, or retry npm ERR! this command with --force, or --legacy-peer-deps npm ERR! to accept an incorrect (and potentially broken) dependency resolution. npm ERR! npm ERR! See /home/mihaim/.npm/eresolve-report.txt for a full report. npm ERR! A complete log of this run can be found in: npm ERR! /home/mihaim/.npm/_logs/2022-01-14T21_35_56_755Z-debug.log

Could you tell us more about how you are publishing? Which command did you use?

i tried from vscode crtl-shift - p --> dendron: Publish export

then it tries to install dependencies and fails

mihaim@hqdelea:~/Dendron$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 21.10 Release: 21.10 Codename: impish

I'm not sure if the publish export command is up to date. Could you try out the publishing guide on the wiki? https://wiki.dendron.so/notes/4ushYTDoX0TYQ1FDtGQSg/

i can try sure . what i want to achieve is to export the notes in a static format so i can see how it looks like

The quickstart guide on that page should help, although it looks like that page is not loading right now. Let me tag a few people who can take a look at it. @User @User the publishing quickstart guide isn't loading, could you take a look if you have a moment? https://wiki.dendron.so/notes/e5st4LFLtIwwbQmC6JBaF/

and ... mihaim@hqdelea:/mypool/par3disk/mihaim/tests/dendron$ npx dendron publish build npm ERR! could not determine executable to run npm ERR! A complete log of this run can be found in: npm ERR! /home/mihaim/.npm/_logs/2022-01-14T22_48_10_908Z-debug.log

Could you try

npx dendron-cli publish build

instead?

npm ERR! code E404 npm ERR! 404 Not Found - GET https://registry.npmjs.org/dendron-cli - Not found npm ERR! 404 npm ERR! 404 'dendron-cli@latest' is not in the npm registry. npm ERR! 404 You should bug the author to publish it (or use the name yourself!) npm ERR! 404 npm ERR! 404 Note that you can also install from a npm ERR! 404 tarball, folder, http url, or git url.

Okay sorry about that,

npm install -g @dendronhq/dendron-cli

then

dendron publish build

should definitely work. We must have gotten confused with the docs because the team probably already has dendron installed

one sec 🙂

sudo required

re-running with sudo

yeah, I think you need it for the global npm install

yup

174 packages are looking for funding run

npm fund

for details 16 vulnerabilities (4 low, 1 moderate, 11 high) To address all issues, run: npm audit fix Run

npm audit

for details.

npm's vulnerability checker is a little confusing, it doesn't mean anything is actually vulnerable, you can safely ignore it: https://overreacted.io/npm-audit-broken-by-design/