if you have the

dendron.code-workspace

file in the repository you can open that in your work machine and it will open up your dendron workspace

okay - so I should just delete the dendron folder on my current work machine and then create a blank one to clone my repo into?

if the dendron folder in your work machine is not something you wanted to keep, then yes.

It's blank

the

git clone

command will automatically make it's own folder so it shouldn't really matter.

ahhhhhhh!!! it worked

hell yeah

awesome 😄

rinse and repeat on any other machines you want to access your vault.

Yes, finally. Thank you! I was going to give up on this tool until coming to this Discord.

I'm glad you did because it's such an awesome tool.

it wasn't even hard once people take a step back and explain a few github commands. @User is so fast and fluid in his tutorials that I felt like an idiot for not even being able to get my notes on 2 machines.

It's second nature for people who do this for a living, but it's quite a hard thing to understand if it's your first time using it.

Hell, most the juniors at work have a hard time using it.

for a while.

yeah - it feels like a much easier way to attract users if there were a non-dev dummy tutorial for getting the workflow down. This is the only open source tool I found that will do what I want so I was very sad when I thought it was too 1337 for me.

There are a lot of "git for non techies" blog posts on the internet but this may confuse people even more because the context is a bit different.

and these articles have a lot of filler material explaining the nuanced concept of git which is kinda pointless for their target audience 😄

I'll open an issue to add a note on a

dead simple straight to the point git tutorial for using dendron

on the wiki. Just the other day I was teaching an intern how to use git and it kinda made me think what's the most smoothest way to introduce git to new people (I don't have a good answer yet)

It will definitely be a value add for people like me.

not a dev, but in a technical role where I need a tool like this.

I published my attempt at this dead simple tutorial here: https://mstempl.netlify.app/post/dendron-git/. Let me know if it makes sense and is useful.

That was fast

Hehe

thanks for writing that up @User linked to the guide on the wiki 🙂 https://wiki.dendron.so/notes/401c5889-20ae-4b3a-8468-269def4b4865.html#using-dendron-with-github-and-git

How would one go about creating a 'Comments' section that will allow visitors to leave comments on your published Dendron page?

not yet but we want to enable it in the form of webmentions: https://github.com/dendronhq/dendron/issues/543 will probably be a may or june roadmap item

Happy Wednesday all. I have a yaml-frontmatter related question: I realize many relationships are meant to be worked into the canonical hierarchy directly, but there are definitely relationships that call for links where the meaning diverges from the note's place in the hierarchy. (This is not to disparage hierarchies, just to clarify) What kind of syntax/workflows are dendron users doing for recurring note relationships? Here is some context for clarity: Roam Research: Recommends the format

Director :: Scott Ridley

at the top of each note -- ctrl-f "a standard Metadata" @ https://www.nateliason.com/blog/roam. Obsidian: Recommends having yaml frontmatter for note metadata and then another frontmatter below that for recurring note relationships. They also have some (many?) users that do or want to add these relationships to their yaml frontmatter and subsequently have those attributes treated the way [[bidirectional-links]] are in the note-body. (The relevant syntax convo is here: https://forum.obsidian.md/t/allow-links-in-yaml-front-matter-notion-like-databases-from-metadata-links-as-first-class-citizens/10052/1) It may also be worth mentioning that remnote also leverages relationships with the

::

, but that is simultaneously for spaced repetition, so perhaps not totally relevant...?

I'm not quite sure which relationships you have in mind but I use two types of links: - wiki style links [[link]] in the body to link between certain notes from different hierarchies - an entry like

tags: [journal, gtd]

in the front matter for tagging notes. There's an extension for these tags in VSCode (https://marketplace.visualstudio.com/items?itemName=vscode-nested-tags.vscode-nested-tags) and also Gitjournal reads them mobile

Thanks for the link! 🙂 I'm wondering about relationships between notes however, like

synonym

,

antonym

,

books

,

author

,

director

,

location

, etc.