Preciate the tutorial! I think your life might be easier if your scale for things goes from 1-10 but otherwise, great videos seriously helped a ton. Thank you so much! :D
While I was making this video, I was thinking the same thing, although I really feel attached to the -2 to 2 rating system. The 10-point rating system feels like too much, as we tend to choose the extremes in any case (very bad, very good, or very neutral). I could change the numbers to range from 1 to 4, with 1 being the worst and 4 being the best, but my mind doesn’t like that solution. When I find a solution, or if I give up and go back to the good old 10-point system, I’ll be sure to let you know!
Thanks for the roll-up, I really like the philosophy behind your vault. I bought your first vault a few months ago; and I am in the process of updating it. I have an issue with the Average section though. I get the following error message in the Weekly file "Error parsing YAML" . When I have a look at the daily file, there is a warning sign in front of each of the logs in the frontmatter "type mismatch, expected text" - I noticed that in the traditional frontmatter view your numbers are in quotation marks (e:g: "-2") mine aren't. What property type did you use for the logs in the daily template?
Hi there! If you already purchased a previous vault send me mail with your email address that I can give you access to the latest one! Regarding your question, it should be in a "number" format. If you see quotes around the numbers it probably won't work. It might be that there is a mismatch between the days in that week. Meaning some days might have the normal numbers (-2 to 2) without quotes, and some have the quotes around them. This might cause the calculation in your weekly note to break because it is trying to sum a number with a text. Again, send me your mail and you can see the latest vault in action ;)
Thank you for this review, I agree with a lot of it. Though i dont agree to making folders for the daily notes (year, month etc). We have dataview and various search methods we can use. Making folders is redundant.
I can appreciate how folders aren't necessarily required, but i fail to understand how folders are redundant. As you can drive behavior in Obsidian given a folder a note is in, can't folders serve a purpose? Try eliminating templates from your graph unless the folder they are in is excluded. Putting templates or other system oriented (not note related) items into an excluded folder seems efficient. Also some are more visually oriented and folders can serve them. I do believe folders are often overused when YAML properties or tags can better serve the intended purpose. The flexibility of Obsidian means that there are many ways to accomplish the same or a similar task in a multitude of ways. No one size fits all, it seems.
@@cmx-v3x You are right, folders can serve a purpose. I should not have said "redundant". But in the case of splitting them to distinguish between them, in this case, isn't required.
Hi there! I agree-the folder structure isn't always necessary. My thought process is to avoid unnecessary folders in my system, but when a note clearly belongs in a specific folder, like a daily note, I don't see any harm in creating it (if that’s what you prefer). For me, having a designated folder makes it easier to find a specific daily note by navigating through the folder structure in my storage system (Google Drive). If I were a chef, I might have just one folder called "Recipes" where I'd store all my recipes. That way, it would be easy to find or share any file from my Google Drive in the future. So, in conclusion, you can eliminate the journal folder if you prefer-but personally, it's a folder I still enjoy using! That is the great thing about Obsidian, so many different ways of doing things :) Thanks for the comments! I always enjoy testing some of the beliefs I've built up.
Howdy! I'm in the process of updating "Evergreen" to "Evergreen 2.0." This update will include changes to the daily-to-yearly layout, enhanced functionality for the work vault, and an improved theory based on the original Evergreen. I'm about 90% done and aim to have it completed by the end of this week.
@@construct_by_dee that's awesome. I went ahead and purchased the evergreen the other day and just made a lot of these updates manually but would love to see how you implement it and other changes you make!
@@jtsmith2LA thanks for the support! I sent you a 30-day free membership with access to all the vaults so you can download and compare the latest one when I release it.
I really like how you kept it simple. Just a quick question, what’s the difference between the highlights and the aliases. To me they look like they serve the same use. I know you said to only use the aliases for serious events. But if you let go of that and decide to instead think of one single thing about each and every single day and put that into the aliases,I think this is better structure. Overall this structure is really good, I just don’t understand what the difference is between highlights and aliases
Howdy! It's open to interpretation. For me, "aliases" would be things like: reaching 10k subscribers on my UA-cam channel, quitting my job, getting married, moving to Japan, or going into outer space. On the other hand, "highlights" are anything and everything that made you happy or proud on a specific day. For instance, playing with a puppy, enjoying a fantastic coffee, having a good consulting session, helping a granny cross the street, going to bed early, having an interesting thought, or enjoying playing the guitar. So, in essence, if you create an "alias" for every day, it becomes a little diluted. The big moments won’t stand out as much. With highlights, the intention is to use them in your weekly reviews to track the things that make you happy and fulfilled, with the aim of maintaining an optimistic, rose-colored lens through which you view your life. Hope that makes sense! :)
Hi there! I'm 90% done with the Evergreen 2.0 vault which would include the theory, work vault, and journal (weekly to yearly rollup) vault. I aim to have it done by the end of this week :)
Love the walkthrough on this, thank you! I've been having a blast following along with this and setting it all up, but I've run into a problem... For the review roll ups, the momentjs code at ua-cam.com/video/m5SYja0V29w/v-deo.html throws an error when I put it in. Expected one of the following: '(', ')', 'null', boolean, date, duration, file link, list ('[1, 2, 3]'), negated field, number, object ('{ a: 1, b: 2 }'), string, variable I know the videos only two weeks old, but did something get updated that broke momentjs working inside Dataview?
Update: Got my stuff working, though using date() and not momentjs, in case anyone else runs into a similar issue. >[! highlight]- Highlights! >```dataview TASK FROM "" WHERE contains(text,"#log/highlight") AND date = date(this.date) GROUP BY file.name as filename SORT filename ASC >[! Calendar]- Weekly Reviews >```dataview TASK WHERE icontains(text,"#log/week-review") AND date = date(this.date) GROUP BY file.name as filename SORT filename ASC Hope it helps someone else :D
Hi there! The error you're seeing is expected when viewing the template itself. It should resolve once you activate the template for a specific month. I just tested it on my end, and it still seems to work correctly once activated for a specific month. It’s possible that something in the Templater plugin isn't functioning properly. Have you tried updating all the community plugins you have installed? I see you found an alternative solution-thanks for sharing that and helping out the community! Let me know if I can give you access to my vaults as a way to say thanks :)
@@construct_by_dee That makes sense! I didn’t even think about it throwing an error because it doesn’t have a date to reference in the template. Access to your vaults would be awesome. Thank you!!
What I mean is that it might be desirable to consider images as log as well. Possibly with tag #log/picture. Now images are simply added to a day log. But then you would have to create a separate file for each image, and that might be a bit too complicated....
I think I have it. If you were to insert an image (with tag: #log/picture) into a log, you might be able to get an overview of a day's images in a data view
Preciate the tutorial! I think your life might be easier if your scale for things goes from 1-10 but otherwise, great videos seriously helped a ton. Thank you so much! :D
While I was making this video, I was thinking the same thing, although I really feel attached to the -2 to 2 rating system.
The 10-point rating system feels like too much, as we tend to choose the extremes in any case (very bad, very good, or very neutral). I could change the numbers to range from 1 to 4, with 1 being the worst and 4 being the best, but my mind doesn’t like that solution.
When I find a solution, or if I give up and go back to the good old 10-point system, I’ll be sure to let you know!
been waiting for this . thanks mate!
Thanks for the roll-up, I really like the philosophy behind your vault. I bought your first vault a few months ago; and I am in the process of updating it. I have an issue with the Average section though. I get the following error message in the Weekly file "Error parsing YAML" . When I have a look at the daily file, there is a warning sign in front of each of the logs in the frontmatter "type mismatch, expected text" - I noticed that in the traditional frontmatter view your numbers are in quotation marks (e:g: "-2") mine aren't. What property type did you use for the logs in the daily template?
Hi there!
If you already purchased a previous vault send me mail with your email address that I can give you access to the latest one!
Regarding your question, it should be in a "number" format. If you see quotes around the numbers it probably won't work.
It might be that there is a mismatch between the days in that week. Meaning some days might have the normal numbers (-2 to 2) without quotes, and some have the quotes around them. This might cause the calculation in your weekly note to break because it is trying to sum a number with a text.
Again, send me your mail and you can see the latest vault in action ;)
Thanks! I have a problem with the grid view of the images. I see images in one column. I set up the plugin correctly but it doesn't want to work.
I had the same issue. The problem was that I was not in 'reading mode.' If you have your hotkeys in default I think just press Ctrl + E
Sorry it isn't working for you. Did Hermites comment below fix the issue for you?
For some reason i can't make highlights section in weekly notes work, is it dependent of a previous section or something? :(
THanks for the content btw it has been truly inspirational :)
Hi there!
Can you provide me with more information?
Also provide your code so I can see what went wrong :)
Thank you!!!!!
Thank you for this review, I agree with a lot of it. Though i dont agree to making folders for the daily notes (year, month etc). We have dataview and various search methods we can use. Making folders is redundant.
I can appreciate how folders aren't necessarily required, but i fail to understand how folders are redundant. As you can drive behavior in Obsidian given a folder a note is in, can't folders serve a purpose? Try eliminating templates from your graph unless the folder they are in is excluded. Putting templates or other system oriented (not note related) items into an excluded folder seems efficient. Also some are more visually oriented and folders can serve them. I do believe folders are often overused when YAML properties or tags can better serve the intended purpose.
The flexibility of Obsidian means that there are many ways to accomplish the same or a similar task in a multitude of ways. No one size fits all, it seems.
@@cmx-v3x You are right, folders can serve a purpose. I should not have said "redundant".
But in the case of splitting them to distinguish between them, in this case, isn't required.
Hi there!
I agree-the folder structure isn't always necessary.
My thought process is to avoid unnecessary folders in my system, but when a note clearly belongs in a specific folder, like a daily note, I don't see any harm in creating it (if that’s what you prefer). For me, having a designated folder makes it easier to find a specific daily note by navigating through the folder structure in my storage system (Google Drive).
If I were a chef, I might have just one folder called "Recipes" where I'd store all my recipes. That way, it would be easy to find or share any file from my Google Drive in the future.
So, in conclusion, you can eliminate the journal folder if you prefer-but personally, it's a folder I still enjoy using!
That is the great thing about Obsidian, so many different ways of doing things :)
Thanks for the comments! I always enjoy testing some of the beliefs I've built up.
This is great. Will you be updating your evergreen demo with these templates as well?
Howdy!
I'm in the process of updating "Evergreen" to "Evergreen 2.0." This update will include changes to the daily-to-yearly layout, enhanced functionality for the work vault, and an improved theory based on the original Evergreen.
I'm about 90% done and aim to have it completed by the end of this week.
@@construct_by_dee that's awesome. I went ahead and purchased the evergreen the other day and just made a lot of these updates manually but would love to see how you implement it and other changes you make!
@@jtsmith2LA thanks for the support!
I sent you a 30-day free membership with access to all the vaults so you can download and compare the latest one when I release it.
I really like how you kept it simple. Just a quick question, what’s the difference between the highlights and the aliases.
To me they look like they serve the same use.
I know you said to only use the aliases for serious events.
But if you let go of that and decide to instead think of one single thing about each and every single day and put that into the aliases,I think this is better structure.
Overall this structure is really good, I just don’t understand what the difference is between highlights and aliases
Howdy!
It's open to interpretation.
For me, "aliases" would be things like: reaching 10k subscribers on my UA-cam channel, quitting my job, getting married, moving to Japan, or going into outer space.
On the other hand, "highlights" are anything and everything that made you happy or proud on a specific day. For instance, playing with a puppy, enjoying a fantastic coffee, having a good consulting session, helping a granny cross the street, going to bed early, having an interesting thought, or enjoying playing the guitar.
So, in essence, if you create an "alias" for every day, it becomes a little diluted. The big moments won’t stand out as much.
With highlights, the intention is to use them in your weekly reviews to track the things that make you happy and fulfilled, with the aim of maintaining an optimistic, rose-colored lens through which you view your life.
Hope that makes sense! :)
@@construct_by_dee This is actually a really good explanation, thank you!
Is there a premade vault available also for the Logredis type vault?
Hi there!
I'm 90% done with the Evergreen 2.0 vault which would include the theory, work vault, and journal (weekly to yearly rollup) vault.
I aim to have it done by the end of this week :)
Love the walkthrough on this, thank you! I've been having a blast following along with this and setting it all up, but I've run into a problem... For the review roll ups, the momentjs code at ua-cam.com/video/m5SYja0V29w/v-deo.html throws an error when I put it in.
Expected one of the following:
'(', ')', 'null', boolean, date, duration, file link, list ('[1, 2, 3]'), negated field, number, object ('{ a: 1, b: 2 }'), string, variable
I know the videos only two weeks old, but did something get updated that broke momentjs working inside Dataview?
Update: Got my stuff working, though using date() and not momentjs, in case anyone else runs into a similar issue.
>[! highlight]- Highlights!
>```dataview
TASK
FROM ""
WHERE contains(text,"#log/highlight")
AND date = date(this.date)
GROUP BY file.name as filename
SORT filename ASC
>[! Calendar]- Weekly Reviews
>```dataview
TASK
WHERE icontains(text,"#log/week-review")
AND date = date(this.date)
GROUP BY file.name as filename
SORT filename ASC
Hope it helps someone else :D
Hi there!
The error you're seeing is expected when viewing the template itself. It should resolve once you activate the template for a specific month.
I just tested it on my end, and it still seems to work correctly once activated for a specific month.
It’s possible that something in the Templater plugin isn't functioning properly. Have you tried updating all the community plugins you have installed?
I see you found an alternative solution-thanks for sharing that and helping out the community!
Let me know if I can give you access to my vaults as a way to say thanks :)
@@construct_by_dee That makes sense! I didn’t even think about it throwing an error because it doesn’t have a date to reference in the template.
Access to your vaults would be awesome. Thank you!!
@@bw4679 Send me a message via mail so I can add your email address :)
DeeConstruct.workbench@gmail.com
Learned a lot from your videos. What does bother me is the fact that an image is also a log. But how to implement that is still an issue
Hi there! What do you mean? Do you want to use images more in logs?
What I mean is that it might be desirable to consider images as log as well. Possibly with tag #log/picture. Now images are simply added to a day log. But then you would have to create a separate file for each image, and that might be a bit too complicated....
I think I have it. If you were to insert an image (with tag: #log/picture) into a log, you might be able to get an overview of a day's images in a data view