P.A.R.A method implemented in Anytype

Hi everyone.
I was just thinking to restructure my Anytype using P.A.R.A method.

I imagine someone has already done the same thing.

How did you achieve it?
Did you create new objects (area, resource,…) and then used sets? collections? tags?



Thank you very much for your help/feedback.


I use a modified version. I don’t use “projects”, but rather call them milestones etc but very similar. I do use areas. Area is a collection of pages, sets and other collections. I do use anytype for project management and it is very handy to change the type “opportunity” into type goal and then have daily tasks that are coded by several different tags and statuses show up in a daily dashboard. It is much more powerful than I thought at the first two attempts to use it. Once you get the terminology clear it is not hard to configure your system. I have found it so much easier than obsidian, logseq, Tana, or even notion.

1 Like

Hi there,

here you go :slight_smile:



have a good one :slight_smile:


Bookmarks = Resources
Tasks = Projects
Pages = Areas

Sorting by Status for realising Archives

That’s my AnyType PARA (Project Areas Resources Archives)

1 Like

You know you can create custom object types right? You’re not stuck with the default objects.

There are many ways to organize within Anytype, specially for P.A.R.A.

  1. You can simply make a Map of Content page for each main category and go from there.
  2. Create an object type for each category (though I would not recommend that)
  3. Use the tag relation and make tags for each category. Then make sets based on the tag relation and filter.
  4. Create a custom relation called P.A.R.A. like the status relation and go from there.

All depents on your workflow and wishes.

I am currently testing a custom Note status relation. Where different status means it appears in different sets across my workspace.

1 Like

Yeah, I know. Usually, to start using programs such as AnyType, the user will be able to use ready-made (system) types and relationships. Over time, when the user understands how to use them, they will start creating them on their own.

Could you elaborate on why you wouldn’t recommend this approach?

This would mean that any object can only have one of the four P.A.R.A. types.

You only have Project, Area, Resources and Archive types and I think that would limit you to much in my opinion. I would use object types for what type it actually is, like meeting notes, human, bookmark, etc.

But that comes down to personal preference and what type of content you want to manage in Anytype.

I think I don’t quite understand the problem about this. I’d still have Notes, Pages, Meetings notes etc. but I’d add them to a Project, right?

I don’t see an issue with creating object types (at least for projects and areas).

So let’s say you are using a type Project. How do you add notes to this project? It’s not a folder. So just in-line within the note? Or reference it with a relation or similar?

:wave:t3: Hi @tony1

That sounds very interesting. :thinking:
Could you show some pictures of your project management system? I’m still tinkering with mine and haven’t found the right solution for me yet. Maybe your pictures will give me some new insights on how I could build my system.

What has changed over the attempts? What did you learn?

once I understood what sets collection type and relations were used it was easy to set things up. I have a few different dashboards that I like to use toggle on to put several inline sets on one page that can be hidden.
I use a tag named thread to mark each area and then you can add things on the fly as needed
It is like the super tags in tana (except it does not inherit from parent which is really cool in tana) and obsidian meta info. Anytype is not great at capturing info just yet and I still use mem.ai for that but for a daily note taking and project management it is really good. I can spend more time working that trying to get a system in place in notion or tana or obsidian. When collaboration is finished I will transition our teams over to anytype

1 Like

If someone needs further ideas or explanation for a possible approach: