got it. i don't see any immediate problems with dendron preview support the

{{}}

syntax. the biggest blocker is time as our roadmap is pretty full this year with existing items. can you submit a feature request so we can track it in our roadmap? https://github.com/dendronhq/dendron/issues/new?assignees=&labels=&template=feature_request.md&title=

@User i think at the most basic it would be simply rendering it as a table (eg. github) as for populating the frontmatter, that would be nice. you can see how dendron does it here https://github.com/dendronhq/dendron/blob/master/packages/common-all/src/nodev2.ts#L38:L38

as for supporting wiki-links via id - you would be ahead of the curve. that's a planned addition and not supported in dendron yet 😅

what happens is that we convert ids to filenames during publication

this way you can rename the note but preserve the url

ah.

and while we're talking about features, the last thing i'll add for now is a logical view of

.

delimited files

dendron currently uses a flat file structure which means everything is in one folder

dendron has its own logical tree view that converts this into a folder hierarchy view https://dendron.so/notes/f7ebd4aa-8ba7-4bc5-bd00-a1efc5315f07.html

Alright. I think the folder hierarchy is probably the most important.

I've filled all the things we have spoken about over here - https://github.com/GitJournal/GitJournal/labels/Dendron

My current priorities are "iCloud support" / "Multi repo support" / more obsidian compatibility (which overlaps with Dendron)

But I get distracted and sometimes implement features so my workflow is better 😄

nice. i like the bias for action and note first approach. feel free to post here if you have any questions about anything

heh, same here. a roadmap is nice but i find that it helps with motivation in the long run when you work on things that are immediately affecting your workflow

Alright. I'm going to call it a night, I'll keep you posted about how it goes.

sounds good. gnight 🙂

Feel free to ping me if you think of anything else.

i'll probably have more things soon enough. will ping!

I was doing some hierarchy refactoring last night (awesome feature) and had a question around formatting. I use a slightly different syntax to the output from Dendron CLI operations (in lists, * instead of -, 4 space indents rather than 2, empty line under headings, etc.). Is canonicalising formatting when performing these operations intended and desirable? If so, did you plan to add formatting options for this, or maybe document/lint the formatting? I'm fairly precious about consistency of formatting, so I'm all for help maintaining this 😅

@User it is intended though what canonical means should be tunable. was waiting for someone to bring it up before working on it 😅 indents and formatting is controlled here: https://github.com/dendronhq/dendron/blob/master/packages/engine-server/src/topics/markdown/utilsv2.ts#L47:L47

Please don't get distracted from more useful features by my OCD 😊

I love that you've already thought about it haha

haha, it's all good. can you submit a feature request? meanwhile, i'll do a little writeup of changes that need to be made to enable this and either you or I can race to get to it 😉

Sure thing, thanks 😁

It'd be great if there was some kind of

dendron-cli lint

command that could both list formatting violations and indicate "compliance" with its exist status, and maybe a

--fix

flag for correcting them. This would work really well for the Pages publishing workflow

Would you like separate tickets?

yes please 🙂

I've raised #278 and #279, happy to add to them if I can help