[feature request] option to setup a dir where all notes are to be published about obsidian-digital-garden HOT 11 CLOSED

I am working on a release which will make it alot easier to manage and apply the dg-publish attribute to many notes at a time. Hopefully these two features combined will solve your problem. I'll let you know when the release becomes available

from obsidian-digital-garden.

Yeah, that would surely be cool (choose specific directories in a filetree).

However, my first thought was something as simple as what we have in Settings > Files & Links > Default location for new notes:

It could be something like "Default location for public notes", and then every note inside that location (subdirs included) would be automatically published, except the notes with an explicit dg-publish: false.

from obsidian-digital-garden.

This feature would be awesome, would make my life easier ;)

from obsidian-digital-garden.

You can use Templater with option to create an empty note with enabled frontmatter.

from obsidian-digital-garden.

Yeah, I think it can be add as a tip :)

from obsidian-digital-garden.

Although the Templater seems to be a really handy way to start creating notes that will be public, I think it doesn't fully address the feature request.

Example: if I have a directory with subdirectories and full of hundreds of notes. If I understood correctly Templater is not able to go into each one of the notes and add the dg-publish: true in the frontmatter.

Anyways, the solution we've found so far (the shell script and the Templater plugin) is ok for my current workflow. So, yeah, I also consider this issue as "closed.

Thanks guys! :)

from obsidian-digital-garden.

As a workaround, I've created this script: https://gist.github.com/meleu/f9667e76a2744d46686702edeb3cc77c

Requirement: the vault itself must be a git repository (what I usually do).

The script adds a dg-publish: true to all versioned *.md files that don't have a dg-publish: defined in it's frontmatter.

Consequences of this:

• non versioned files won't be affected (e.g.: gitignored files)
• files without any frontmatter will have one with dg-publish: true
• files with a dg-publish: (any value) in its frontmatter won't be touched

While the feature requested in the OP is not implemented, I'll be using that script as pre-commit git hook.

from obsidian-digital-garden.

Thanks for providing a workaround. Hopefully it will serve as a solution for people until this is properly supported.

I'm thinking that this could be implemented by creating a GUI presenting you with the filetree of your vault which would allow you to select folders and/or notes and marking them all with dg-publish: true with the press of a button. Also, the notes already marked with dg-publish, should already be selected.

What do you think? Would that work for your usecase, or did you have something different in mind?

from obsidian-digital-garden.

You can use Templater with option to create an empty note with enabled frontmatter.

This dies the trick for me, thanks! Now Obsidian + Digital Garden is everything I need for making and presenting stuff to my students 👍

from obsidian-digital-garden.

That's such a cool workflow. Thank you so much for sharing this tip. I wasn't to keen on making a setting where you define a folder that did not have the publish flag, as I think it would be confusing for a lot of users. All published notes should have a flag. This solution fixes that problem.

I hope it's okay that I add this tip in the readme? It needs a bit of cleaning up and I think adding this worfklow would be helpful for a lot of people.

from obsidian-digital-garden.

Great work on this project @oleeskild ! Do you have any updates on applying dg-publish so we can publish an entire subdirectory of notes with a single property? I am looking for a way to 1. Publish all my notes existing 2. Publish all notes in a subdirectory

from obsidian-digital-garden.