How did Charlotte implement PARA inside Anytype?
She exported her account, created a new space, formatted Projects, Areas, and Resources as collections, and made an Archive implemented as a set filtered by an 'archive' tag so items can be restored by removing the tag.
Why choose collections for Projects/Areas/Resources?
Collections allow adding any object type (pages, sets, collections) — functioning like folders — which makes it easy to group heterogeneous objects under Projects, Areas, or Resources.
What steps did she take to migrate and track progress?
After importing everything into the new space she filtered for pages/sets/collections, created Area objects (e.g., Health), linked related items, deleted old links, and added a checkmark relation and filter to track which objects still needed sorting.
What practical benefits did PARA bring in Anytype?
PARA reduced search friction, made it easier to include temporary items because they can be archived, and clarified which items are actionable (projects) versus ongoing (areas) or reference (resources).
What were the main drawbacks she experienced?
Filing every new object into a category felt cumbersome and time-consuming, and the enforced structure reduced some personalization that made her workspace feel unique.