Brilliant video, friend. It's great to see use cases like these than demos of functionality as such. Sometimes I'm more interested in the how / why than the tool itself. Thank you!
Good stuff. Thanks. BTW other videos have pointed out that the %2F in filenames (14:24) can mess up other apps using the same folders - Obsidian for example. logseq settings let you use 3 underscores instead which, apparently, is more compatible.
This is great, thanks! Wondering if you'd considered adding the project metadata as page properties, and if so, why you decided against it? I had been creating projects as namespaces under Projects/, but I just didn't like it from a readability standpoint. I'm now testing out applying the tag "Projects" to page properties for the project itself. And then I use namespaces for all of the sub-sections. Ex. Project = "Identify new product name." I create a page for "Identify new product name", add "tags:: projects" as a page property, and then create namespaces for any big chunks of work, i.e. "Identify new product name/Meeting notes," "Identify new product name/Hire branding agency," etc.
Thank you so much for your comment. I was also in a debate on namespaces for projects but in the long run, although the readability is not great, I needed something to create a bit of order. It is funny you mentioned Projects - reading Tiago Forte's book, I am very interested in the PARA approach - will keep you updated how that goes.
Brilliant video, friend. It's great to see use cases like these than demos of functionality as such. Sometimes I'm more interested in the how / why than the tool itself. Thank you!
Glad you enjoyed it!
Thank you. You Can explain very good. Its funny to listen and Watch.
Good stuff. Thanks. BTW other videos have pointed out that the %2F in filenames (14:24) can mess up other apps using the same folders - Obsidian for example. logseq settings let you use 3 underscores instead which, apparently, is more compatible.
Very helpful! Thanks.
This is great, thanks!
Wondering if you'd considered adding the project metadata as page properties, and if so, why you decided against it?
I had been creating projects as namespaces under Projects/, but I just didn't like it from a readability standpoint.
I'm now testing out applying the tag "Projects" to page properties for the project itself. And then I use namespaces for all of the sub-sections.
Ex. Project = "Identify new product name." I create a page for "Identify new product name", add "tags:: projects" as a page property, and then create namespaces for any big chunks of work, i.e. "Identify new product name/Meeting notes," "Identify new product name/Hire branding agency," etc.
Thank you so much for your comment. I was also in a debate on namespaces for projects but in the long run, although the readability is not great, I needed something to create a bit of order.
It is funny you mentioned Projects - reading Tiago Forte's book, I am very interested in the PARA approach - will keep you updated how that goes.
How do I get that calendar/date-picker thing you show around 8:40?
Muy bueno, muchas gracias!
Muchas gracias a ti
Can you make youtube video to insert weather condition ? , Kihwnag Kim from Seoul, Korea