Yea in terms of “working with dendron”, it seems enough at this point that both these Palo forms are .md based. WT is probably just using same design as Wikipedia?

got it. yeah, if its markdown, you should be able to write up your notes in dendron and publish to WT. we have a publish feature that will convert dendron specific md to regular md https://dendron.so/notes/13c4a608-0a32-4c62-9c7e-2b7f9f2d18bf.html#publish

what's the recommended way to maintain dendron across two devices? can I just put the vscode workspace in a git repo?

> what's the recommended way to maintain dendron across two devices? can I just put the vscode workspace in a git repo? @User Hi, the way that I do it is to save the Dendron workspace in my Google Drive which syncs between different computers so that I can access the notes and workspace across devices - not sure if it is the recommended way, but works well for me

@User I bet it would work fine to put your vscode workspace in a git repo.

I don't sync mine, but that would make sense to me.

@21eleven yep, git will work

I put it in a git repo but am getting this error

{"ctx":"ReloadIndex.execute","error":{"status":"unknown","msg":"","friendly":"error initializing notes","payload":"{\"message\":\"parse non ref not implemented, ref: 1,100\",\"stack\":\"Error: parse non ref not implemented, ref: 1,100\\n\\tat Object.f [as parseDendronRef] (/home/x/.vscode-oss/extensions/dendron.dendron-0.15.0/dist/extension.js:68:10729)\\n\\tat s.i (/home/x/.vscode-oss/extensions/dendron.dendron-0.15.0/dist/extension.js:602:13447)\\n\\tat s.tokenizeInline (/home/x/.vscode-oss/extensions/dendron.dendron-0.15.0/dist/extension.js:855:64818)\\n\\tat s.e.exports (/home/x/.vscode-oss/extensions/dendron.dendron-0.15.0/dist/extension.js:855:80554)\\n\\tat s.tokenizeBlock (/home/x/.vscode-oss/extensions/dendron.dendron-0.15.0/dist/extension.js:855:64818)\\n\\tat s.e.exports [as parse] ...

should i just ignore that?

says

Starting Dendron...

@User this is because you have a

(( ... ))

statement. currently, we use double parenthesis to parse note references and will give that error for other content https://dendron.so/notes/f1af56bb-db27-47ae-8406-61a98de6c78c.html we'll be making the parser not emit an error until you actually preview a note for the next release

I just installed Dendron and immediately bumped into two bugs which I reported here: https://github.com/dendronhq/dendron/issues/342 https://github.com/dendronhq/dendron/issues/343 Should I just report these bugs and wait patiently for triage, or is it fine for me to bring attention to them here on Discord? If so, which channel I should use, #748936364283920495 ?

Hello all! Learning typescript from scratch, e.g. from a book "from scratch", how should I organize the structure if this is my first encounter with a dendron? According to the table of contents, language documentation or progressive progress?

@User I'm going to cop out a little and say that I don't think there's a universal structure that works, and that you should start writing things, and break up the note when you find you're scrolling too much. I usually start with a

lang.typescript

page, then as I learn more about it and find quirks I'll add e.g.

lang.typescript.type

, then maybe specific topics like

lang.typescript.type.generic

If you make a selection and then bring up lookup and type the name of a new note, when you hit enter Dendron will move the selection into the new note

@User did a walk through of how he might structure content like this in this onboarding session:

it's true, over the months I've been trying to find a way to learn new things that will be usable and not to deepen the desire for constant organization through which I still felt bad while learning.

I wanted to learn from documentation, books, videos but I never knew how to combine it

and this constant thought that in google I will find it 10x faster and better quality than the notes that I duplicate 0.o

I find that unrest too, especially when I'm working on something entirely new. I try to find connections to related things I already know and link them up early, then I'll write out a single note until I find where I can break it down. Dendron makes it pretty easy to bulk rename notes ("refactor hierarchy", it just finds and replaces in notes' names) so it's quite easy to restructure notes if you end up with a lot of smaller ones

Learning new things is a great teaching, but there is always this unfortunate element of knowledge organization.

feeling*

I'll try a dendron and describe the process. Probably many have a similar problem

Taking programming languages as an example, try to focus on the concept of a programming language more than the language itself, then structure you typescript notes around that. Use the hierarchy to model the way you categorise concepts, keeping your notes specific to one topic

I think extra branches will grow as one language progresses?

There’s another way of designing the graph that makes it easier to to navigate by language: have the languages at the root, then replicate the data and array nodes for each language. You can use * in lookup (e.g. lang.*.data.array) to find the array docs for all languages

This also allows some flexibility around some languages having different feature sets

I'll try, do you think linking in notes to others is a good idea?

like that, 'old examples from obsidian'

It definitely depends on your use case, but I wouldn't link concepts across languages unless one extended the other (e.g. TypeScript and JavaScript)