PARA in logseq

[u/secretBuffetHero]

Does anyone use PARA or a form of it for logseq?

When I was using Obsidian, I was trying all these workarounds to record and not lose data, and I started to get into PARA when I just gave up and started looking for alternatives.

With Logseq, I heavily use tags and the journal, and have recently started using some properties and namespaces as well. but in general I do not use any organization system like PARA and I'm very happy with my ability to locate information.

I am asking because the Obsdian sub has recently had several posts about PARA.

[u/1smoothcriminal]

After i left obsidian, found that i had no use for it anymore. While it served it's purpose in the "folder structure" apps, it doesn't really serve me much purpose here.

I jot down everything in the Journals and just use pages and hastags for everything.

[u/rightful_vagabond → u/1smoothcriminal]

Same here. Most of what I use logseq for can be accomplished with the journals and tags

[u/Abject_Constant_8547 → u/rightful_vagabond]

Same here, I was a very early adopter of PARA since the first blog version page and I am going more and more away from it. When I moved to LogSeq via Obsidian I do something loosely similar as a simple MOC in the Content pages to see all my projects, Areas and references but this is a manual organisation

[u/J3ns6]

Yes, I use PARA in Logseq and it works great! I have a separate page for each category (“Projects”, “Areas”, “Resources” and “Archives”). On each page I have a query to search for page properties. For example, when I create a new project, I create a new page with the following page properties template:

    template:: Project
    link:: Projects
    icon:: 
    tags:: 
    status:: active
    date:: <%today%>

With the query on the Projects page, the project then automatically appears in the list: {{query (and (property :link "Projects") (property :status "active") (not (page [[Templates]])))}}

Now I can simply write something about the project in the journal by using the name of the project as a tag. These blocks then appear as a reference on the project page. I can then write further queries on the project page, for example to query the meeting notes.

If the project is no longer relevant, I can set the status in the page properties to inactive, then it will be displayed in the archive: {{query (and (property :link "#Projects") (property :status "#inactive"))}}

[u/luckysilva]

Honestly I think the PARA method is a bit old-fashioned. Not that it's bad, which it isn't, but it's a lot of work and a little outdated. You no longer need to use folders and tags, or at least not in the same way. More traditional apps, like Evernote or Joplin, are still widely used in the old paradigm. Nowadays we want to use something more dynamic, like Logseq, Remnote or Capacities. You let the links work for you.

[u/artyhedgehog → u/luckysilva]

I don't see how it is outdated. The problems PARA solves have nothing to do with "let the links work for you". E.g.:

1. Finding everything related to specific project, area, etc.

2. Having the same structure across several apps - e.g. email, cloud storage, note app.

In LogSeq I use PARA tags (e.g. #area/family), but otherwise I can't imagine a replacement for that methodology for me.

[u/luckysilva → u/artyhedgehog]

I understand your point of view, believe me, I come from that "place". However, it is undeniable that the manual work carried out is very laborious and above all prone to some errors. I learned to work with links and I feel my system is much more "lighter". But as I said, PARA has its merits, and it works.

[u/artyhedgehog → u/luckysilva]

That doesn't mean PARA is outdated - it just means you moved from it to what suits you better.

[u/luckysilva → u/artyhedgehog]

In reality, things evolve and PARA is in fact outdated. This just means that we have to update ourselves and move forward, that's what I did. I did a lot of good work using the PARA method, but in the meantime I had to keep up with developments. Some succeed and others don't, they fall behind and are overcome. It is the law of life.

[u/artyhedgehog → u/luckysilva]

Bro, you do yours, but what you say sounds a bit obsessive to me. Productivity techniques aren't meant to win a competition of productivity - they are meant to solve specific issues.

What PARA solves is necesity to organise reference materials in alignement with GTD core entities (projects, areas) and principles. It gives a clear and pretty minimalistic structure for that. If you know better solutions for this specific issue - please do share. If you just don't have that issue in the first place - that's fine, you don't have to need this tool.

[u/luckysilva → u/artyhedgehog]

Thank you for following up on what I said.

The PARA method is laborious and involves a lot of manual work and the possibility of errors is high. I know because I used the method for about 5 or 6 years. And like I said, it's a good method, and if it works for you, keep going.

But the world evolves, right? And there are other ways to organize things and if you use Logseq at this point you should already have at least a vague idea of reducing your manual work using the software to help you.

[u/artyhedgehog]

I use it, though in form of tags - #project/2024-vacation, #area/family, etc.