nevermind i found it 🙂

So I've forked the

dendron-template

on github, (maybe

dendron-site-template

would have communicated the repo's intent better, I found the name a little cryptic). Looking around the repo I see two copies of the notes, one with dot-hierarchical names in the vault, and one with the universal-ID naming style under the docs/notes/ directory. I guessing the notes in the vault are the ones we edit in vscode, while the ones in docs/notes/ are generated as a step in creating the static files for a jekyl site, is that correct? - are these updated as we make edits or only ever up dated when generated for the next iteration of the site? - if the later does the update work on changed/added files only, or does it wipe and generate anew? - are these files even needed or could you empty the docs/notes/ directory? Some renaming of the directory structure from conventions used in sphinx might make things clearer and make a place for enhancements (pod outputs?). Instead of docs/notes use

builds/

, then place the generated files in two level subfolders. Where the first level is named for generator-purpose, the second level names the type of output, prefaced with an underscore, (indicating the file in this directory are are generated, and may be overwritten when the generator is invoked again. e.g. builds - dendron-ID-renamer _IDs-md - jekyl _static-site-files - sphinx _html _pdf - pandoc _md _html _pdf

> So I've forked the

dendron-template

on github, (maybe

dendron-site-template

would have communicated the repo's intent better, I found the name a little cryptic). This is helpful feedback, thanks. Can you remember where you were directed to the

dendron-template

repo? The getting started docs suggest initialising an empty workspace from within VS Code: https://www.dendron.so/notes/d95b93bf-5e6f-4dd0-b7d7-c8e29e061876.html#install > the notes in the vault are the ones we edit in vscode, while the ones in docs/notes/ are generated Yep! The filenames in that directory match the

id

values in the frontmatter (between the

---

) at the top of the markdown files. > - are these updated as we make edits or only ever up dated when generated for the next iteration of the site? They're updated whenever you run the "Dendron: Build pod" command. The relevant docs look a little sparse right now, but here they are: https://www.dendron.so/notes/eea2b078-1acc-4071-a14e-18299fc28f47.html#pods > - if the later does the update work on changed/added files only, or does it wipe and generate anew? Incremental update support requires

rsync

for now, but it can be enabled: https://www.dendron.so/notes/401c5889-20ae-4b3a-8468-269def4b4865.html#incremental-builds https://discordapp.com/channels/717965437182410783/739186036495876126/759169016333336596 > - are these files even needed or could you empty the docs/notes/ directory? They're not necessary for Dendron to work properly, they're just for publishing. > Some renaming of the directory structure from conventions used in sphinx might make things clearer and make a place for enhancements (pod outputs?). I'm not sure there's been much discussion around this yet. Dendron is getting support for multiple vaults (root directories for notes) soon, so that may be an ideal opportunity to rethink the directory structure. @User hope this 👆 helps, thanks for the thoughtful feedback and welcome to Dendron 😊

Ignore this, I'll try again, (dang shift-return instead of return, get's me every time!)

I did exactly the same thing 😅

lol, same here

> This is helpful feedback, thanks. Can you remember where you were directed to the

dendron-template

repo? I wasn't directed there, I set up the fork so I can summit PR's on the documentation on on things I've found as I'm working through Dendron. One of my use cases for dendron is to help me revamp the doc for a opensource project I contribute to, (Leo Editor - written in Python), so I'm exploring dendron with an eye towards that end. As I don't know all the nuts and bolts of markdown, and Leo's doc is too complex to just wade in and start there with out a plan, I'm practicing by making a set of notes for Markdown from resources on the web, e.g. https://github.com/mattcone/markdown-guide This is giving me a chance to practice the "Amoeba technique", as a lot of the stuff I'm finding are monolithic pages, adapt the markdown source to how dendron uses markdown, and so on. Some of the principles that guide me in rewriting doc: - rename things to make what they represent as obvious as possible - watch out for things that break existing conventions The first informs the proposed renaming of

dendron-template

, delving into it I see that Kevin8 use of template is as the dendron web site,

dendron-site-template

, or even

denron.so-site-template

make the repo's use more apparent. I haven't got to the point where I'm ready to publish/host things, so my questions in the post where just to see if my intuitions about this must work were right or not. Going by the structure of other projects,

docs/

, is were I was expect to find doc on the project, which is not what kevin8 is doing here, hence the proposed directory layout. Perhaps Pod's should create/update a

pod-log.md

file along with the other files to write timestamps and files updated, (when use the rsync version). `aside: `I never notice that

git clone

clobbers creation dates.

@User > The first informs the proposed renaming of dendron-template, delving into it I see that Kevin8 use of template is as the dendron web site, dendron-site-template, or even denron.so-site-template make the repo's use more apparent. the reason the repo was named

dendron-template

was because in the early days, it was originally meant to be used for folks who wanted to setup a dendron vault via github. we eventually settled on using

> Dendron: Initialize Workspace

instead and cloning the

dendron-template

during initialization. it probably does make sense to rename it to

dendron-site

or something equivalent today > docs/, is were I was expect to find doc on the project the reason why

docs/

is the publication folder is because that is the convention that was established by github pages (eg. auto-publication by branch or by contents inside the

docs/

folder).

docs/

in this case is for the published docs

> > the reason why

docs/

is the publication folder is because that is the convention that was established by github pages (eg. auto-publication by branch or by contents inside the

docs/

folder).

docs/

in this case is for the published docs @User Of course one of the problems with conventions is that you have to know them 😊 ! I might still argue for some of what I was talking about in the future as other targets than jekly become possible.

@User heh, yeah, that's completely fair. we have plans for making a big overhaul to publishing in the upcoming weeks so will take this into account

in the meanwhile, i think i will take your comment on renaming

dendron-template

since the name is misleading at this point 😅

Hey @User I am new here. I just posted in #734966064957620294. I am very excited to discover Dendron. I have a question about specific scenario. Apologies if it is already answered somewhere, still familiarizing myself with all the available documentation. What is Dendron's answer to situation in which I don't remember the exact hierarchy, but I remember the tags? Can I search for tags intersection? Let me explain my use case. Let's say that I remember I have noted down a Troubleshooting Guide for when I run "Frobz" CLI command for some project FooBar, and I get an error. In a tag based system I would search for a note that has all of these tags: #FooBar #TSG #CLI #Frobz. However, in a hierarchy based system, I might not remember: Should I do projects.FooBar.CLI.TSGs ? Or maybe TSGs.FooBar.CLI.Frobz ? What if this is some combination of hierarchy and tags?

@User multiple solutions here. first, dendron supports tags, we recommend using hierarchies to represent tags https://dendron.so/notes/8bc9b3f1-8508-4d3a-a2de-be9f12ef1821.html the nice thing with these tags is that you are able to leverage backlinks and refactoring with tags. so searching for tag is one solution

another way to slice this is to use search but use it with hierarchy to narrow the scope. for example, if I run into a gotcha with project X, I might search for

gotcha

under

pro.x.*

the nice thing with hierarchies is that they can be leveraged to make how you already search for things for effective

@User got it, thanks! Sounds good 🙂

Hi @User, Is there a way to enable autocomplete for the Lookup bar?

@User not at the moment. you can autocomplete wiki-links but vscode doesn't support autocomplete in the lookup component

@User Thanks for hasty reply!

Hello guys! Is it possible to put an additional line in the yaml section globally? I mean for all future md-files?

When creating a note through the lookup, if I use title case for the said note, the title of the note (after the id field) does not respect the title case.

Is it a feature? A bug?

Trying to figure out schemas I have the following "projects.schema.yml" file

I have some content in "projects.template.diy.md" file that I need in all new notes that I create. When I create a new note "Projects.Tech.IoT.DIY.Test01", the content from the template file is not there. Please advise on what am I doing wrong

The template filename is the culprit.

Templates have filenames like this:

projects.diy.template.md

Not

projects.template.diy.md

The filename ends with

template.md

.

Renamed

But still not working