4 ms·
I've been trying out this organizational method for about 2 months now. tl;dr - everything falls into a Project.Area.Resource.Archive (sub)folder and the ideal
by v8xi 4y ago
I've been trying out this organizational method for about 2 months now. tl;dr - everything falls into a Project.Area.Resource.Archive (sub)folder and the ideal is to rotate things through as soon as they're finished to Archives where you can ~forget about them. What I appreciate about it is how its recursive, so you can organize individual projects according to the PARA rules.
I agree with the author that its difficult to decide between Areas and Projects and appreciate his take that all Projects belong to an Area - insightful. One of the changes I've made to the system is to refer to Resources instead as Records. I like to take daily notes and keep to-do lists, summarize/link articles etc which usually have some type of temporal resolution and may not always fit in a specific project/area. So far I like it better than my old method of categorizing things by date and type and it meshes well with my fairly simple Obsidian environment.
- patleeman 4y agoI had similar challenges as well with the Archive/Resources/Areas. I didn't like the extra mental overhead to determine if something was categorized a certain way. I ended up combining Archive/Resources/Areas into a Knowledge folder and then using the root folder to hold everything else. If anyone is interested, I wrote about my simple system here: https://patricklee.nyc/blog/how-i-use-obsidian/ https://patricklee.nyc/blog/how-i-use-obsidian/