Certainly the project itself has a vault.

I can't wait to explore that

Thats the question Work-Item does not really make sense to me in generall and since its meant to be used for internal use I figuered who ever creates an Item has the Permission to add labels.

I do not 😄 but I understand your point.

I was discussing work-item templates in a completely different context just yesterday. Perhaps they are more generic than not.

So I think I know how my vault got multiple vault instances - I have VS Code on a personal thumb drive so that I can take my work with me from company owned computers to my own computers, and dendron is installed there. The problem comes from how dendron is initializing workspaces and likely directly from being a different drive letter at different workstations. Now deleting the excess vaults isnt solving the problem, because it is adding the old one. It didn’t use to have this problem, but I’m running into every time I go from one workstation to the other, but not when I utilize the same workstation in a row

I haven't tried syncing across machines yet though I was looking at perhaps initializing the vault as a discrete repo.

It would be nice to throw s3 at it a la joplin.

I need to understand the role of the workspace, more, tbh.

but -- naive as I am I'm just thinking git might be The Way.

If I had to solve such a problem without sync, I'd look at remote ssh via the remote explorer.

sounds like the right thing to do. what did you have in mind? and what warnings are we seeing?

just invited you as a collaborator to the repo so you should now 🙂

ah, yeah, we don't handle that use case yet since we determine vaults by their absolute path. we also do a sync on startup to make sure that vaults didn't get out of line (eg. delete in vscode workspace but in yml). can you submit an issue with your use case?

git is the primary way dendron operates today 🙂

yeah i will submit that. Thanks

I can't figure out what might be failing with this looking at the code. But I found a workaround: using

editor.action.revealDefinition

now I can navigate between links

submitted here https://github.com/dendronhq/dendron/issues/522

If anyone is interested in working on markdown transformations within Dendron, check out the pairing session with me and @bvautier which covers how to upgrade Dendron's markdown capabilities docs and additional material here https://dendron.so/notes/1bce1c33-c14b-4e5e-b493-45683c8cf54f.html @cameron

reminds me of https://docs.antora.org, but in antora the orchestrator yaml (dendron.yml for dendron, *playbook.yml for antora) is in a separate repo

Antora have a nice demo at https://gitlab.com/antora/demo - Would a dendron demo be as simple if the multi-vault proposal was implemented?

multi-vault is implemented 🙂 need to read through the docs on antora. never heard about it until now

@User In some ways, antora addresses the same problem as dendron, I've got documentation in lots of repos, and it's getting versioned, how do I present that material to user and interested contributors, who might wanna edit at the drop of a hat. If antora had schemas.. or if dendron was asciidoc native, tech writers (like me) would flock! That sounds like i might be dissing dendron, I'm not.. AsciiDoc is very formal (eg makes linking worse than wiki/markdown), and things get complex quickly. I just think you'll enjoy looking at card ui filtering at https://docs.couchbase.com/tutorials/tutorial-template/sample.html (I'm not affiliated) and how couchbase pull asciidoc from repos, https://github.com/couchbase/docs-site/blob/master/antora-playbook.yml and always offer 'edit' affordance - It's like mindmapping in git? - now this is way too long a message 😃

Correction: IMO, dendron addresses a notes problem (with an excellent "writer's experience' (WX?) where as antora/asciidoc address a publisher's experience (I know this note needs to fit into an overall website) - Antora is all about formal doc, keeping everything in a lightweight markup language is the common theme

some folks here have been discussing about asciidoc and got me interested 😄 I'm considering using it at work to learn what it's all about.

Will chime in about Antora.... Antora is built by the same developer who currently maintains AsciiDoctor. Dan Allan (https://github.com/mojavelinux). He created Antora a bout a year or two ago to overcome some of the limitations in Hugo. Antora squarely targets the technical documentation market rather than personal blogging sites. The benefits is that it is extremely easy to put a documentation site from multiple different git repositories AND branches within those repositories. Dan created the concept of a playbook that allows people to create a documentation site that pulls info from GitHub, GitLab, BitBucket, as well as different branches within these repos, which mostly correspond to different version numbers. The whole experience (when I tried it a year ago) was rather painless. I didn't pursue it more as I was looking for a company website solution rather than a documentation site. There are certainly some great ideas there, and a lot could be leveraged if Dendron natively supported the AsciiDoc format 😉

> I'm not.. AsciiDoc is very formal (eg makes linking worse than wiki/markdown), and things get complex quickly Sorry can't let this slide 😄 . It is different not complex. Once you appreciate the thoughtfulness you realise it is extremely well put together. The apparent complexity comes from the fact that people need to build complex documents. Markdown does not allow you to build complex documents. AsciiDoctor does. You only need to worry about the more advanced features if you really need them, otherwise you can happily ignore them. However, it is reassuring to know that when you need advanced features AsciiDoctor has you covered. You will breath a big sigh of relief when you realise AsciiDoctor has all the features you will ever need and it all comes out of the box.

Just checked the Couchbase documentation site. Wow they did a great job. It looks amazing.

yes, 100% agree - badly written sentence on my part, OOB AsciiDoc has a huge feature set.

I was trying to find this article this morning... finally remembered how to find it (going into Dendron now so I can "recall" it faster next time 🙂 It is aimed at people wanting to build their own documentation site. (So not really applicable to PKM). However, I like his take on the whole CMS "situation": https://medium.marqeta.com/write-your-developer-docs-in-asciidoc-78febf2a1304 Check out their documentation site (the first link in the article). They did a great job.