maybe "set to default" is perceived as "not set at all"? I could try some other dark theme)).

all good. currently, i'm using the not so nice way of reading settings from json files. switching to using vscode

WorkspaceConfiguration

api which will read all settings

@User took your feedback about dev docs. updated the docs and consolidated everything to the website: https://www.dendron.so/notes/64f0e2d5-2c83-43df-9144-40f2c68935aa.html this should address everything except the

watch script

swallowing warnings/errors 😅

Thanks, will take a look!

> there is very loose documentation about the code here: https://www.dendron.so/notes/c160ddce-edec-4f6e-841b-418d6030fa37.html > > if you end up diving into this, happy to point you to the relevant parts of the code to add rst support in the #748936364283920495 channel @User \n

started to look into this so I could use dendron to review/revise the Leo documentation. Problem anticpated: * yaml frontmatter get pass to Sphinx can 'comment out' such line by prefixing each line with ".. " or do something like this:

.. frontmatter-(yaml for Dendron)
   ---
   id: a7c3a810-28c8-4b47-96a6-8156b1524af4
   title: Lookup
   desc: ''
   updated: 1595952505038
   created: 1595952505038
   ---

This means generating/update frontmatter would have to be adjusted.

* use *.rst for files created/imported complication, sometimes the files just use a *.txt extension, so that may be what you want to use, (markdown does this too}

N.B. some of this might be generalized for use with other markup

@User i've had a number of questions regarding whether we can remove the frontmatter and have created a ticket that will store frontmatter outside of a note: https://github.com/dendronhq/dendron/issues/160 let me know if you're interested in this and I can make a list of changes necessary

This is an interesting one, but where would the 'outside' be?

Oh I see your example? Seems reasonable. Just one json file per vault I assume or it would get very very messy.

yep. there's lots of alternative ways as well. going with a json blob for now because its the most straightforward (and something we were going to do anyways for caching purposes) some alternatives: - metadata folder inside vault with one json file per note (makes it easier for people to edit) - metadata file alongside note

- foo.md
    - .foo.meta.json

- using sqlite

I like the JSON approach

Blob or folder

Are you looking for PR's?

always 🙂 if you're interested in taking this on, happy to point you to the relevant portions of the code

you can find the general dev docs here https://www.dendron.so/notes/64f0e2d5-2c83-43df-9144-40f2c68935aa.html we also have good discussions in the #748936364283920495 channel about features

I'm not a super wiz at JS/TS, more of a Python guy but moreso interested in how the interface will get developed. More than happy to learn and wield what skills I have in the right direction

i started off as a python guy myself and, package management nightmare non-withstanding, will always have a special place in my heart 🙂

i find typescript to be pretty similar to python in many ways. i'm going to do a writeup of changes (was going to do it anyways) and break the issue down into sub-tasks and you're free to take on as many/little of them as you feel up to. happy to provide pointers or get on a call as well to talk about the typescript/dendron code

that would be awesome!

to get started, i would recommend trying to clone the repo and be able to run dendron locally. just updated the setup instructions so you can tell me if they're any good 😅

Ha, okay. I'll give it a shot now

So whats the process once I've built it locally? Is that now available to my vscode install and would it conflict with the already existing version that I have via the extensions?

you can run the extension via the

launch extension

launch configuration https://www.dendron.so/notes/b239c77e-52f2-4cc3-8390-69e0bc776a72.html#plugin

if you uncomment this line before launch, it will disable all your existing extensions when launching https://github.com/dendronhq/dendron/blob/master/packages/plugin-core/.vscode/launch.json#L14

@User created an issue for the engine to read metadata from json. https://github.com/dendronhq/dendron/issues/165 the engine is responsible for indexing files in dendron https://www.dendron.so/notes/c160ddce-edec-4f6e-841b-418d6030fa37.html#dendron-engine this will be a good place to start. the other tasks will be: - [ ] engine write metadata to json if specified - [ ] add new vscode config to store metadata to json and pass it into engine if specified - [ ] add a

dendron doctor

command to convert between

frontmatter

and

json

i'll write up the details of those once we get there. this ends up being quite an involved change. you definitely choose a meaty first task to get started with 😅

rather than json, you might use

MessagePack structured communication like they do in Neovim, transferred bytes are smaller and would support writing plugins in a lot of different languages.