Most PARA posts on the internet are a Notion template and a wall of screenshots. Almost none of them cover the one bucket where a normal person's saves actually pile up: Resources. That is the articles, bookmarks, YouTube videos, X threads, and newsletters you will probably reread some day, and it is where PARA quietly falls apart if you try to run it inside one notes app.
This is PARA read the way someone with a thousand saved articles would read it. What each letter is for, which tool fits which letter, and why the read-later layer deserves its own home.
A one-paragraph recap, because you already know PARA
Tiago Forte introduced PARA as a system for organizing digital information across every tool you use. In his own words: Projects are short-term efforts with a goal and a deadline, Areas are important responsibilities you manage over time, Resources are topics you are interested in and learning about, and Archives are the other three after they go inactive. Four top-level folders, replicated in every app. That is the whole thing.
The book version is the quickest read; the original blog post is the canonical reference. Both are Forte's own.
What the Resources bucket actually looks like in practice
Forte's examples of Resources topics, lifted from his blog: "graphic design, personal productivity, organic gardening, coffee, modern architecture, web design, Japanese language, French literature, notetaking, breathwork, habit formation, photography, marketing assets."
Go look at whatever you have been saving for the last six months. Your browser bookmarks, your X bookmarks, your read-later queue, your Pocket export if you still have one. I will bet most of it is Resources. A Japanese grammar explainer you want to come back to. Four articles on espresso extraction. That Paul Graham essay you have saved on three different devices. Seven newsletter issues about writing. A long thread on how an indie dev priced their app.
None of that is a Project. None of it is an Area. It is reference material for topics you care about, and PARA says it belongs in Resources. Which means Resources is not a side bucket for most people; it is the bucket.
Here is where PARA as usually written breaks down. The standard guides tell you to create a Resources folder inside Notion or Obsidian and drop links into it. If you have saved twenty bookmarks in your life, fine. If you have saved two thousand, that folder becomes a junkyard with a search bar, and the search bar only searches titles and URLs because the articles themselves live somewhere else.
Resources wants a different tool than Projects and Areas
The quiet truth of running PARA over many years is that the four buckets have different jobs, and one app is rarely great at all four.
- Projects is task-shaped. Goals, next actions, deadlines, a clear finish line. A notes app or a task manager wins here. Notion, Obsidian, Todoist, Things, Apple Notes, even a text file per project.
- Areas is ongoing and responsibility-shaped. Standards, routines, reference docs that stay mostly stable. A notes app wins here too, for the same reason. This is the quiet heart of a long-running second brain.
- Archives is cold storage. Any decent notes app can do this. You need to search it, not look at it.
- Resources is reference-shaped and read-later-shaped. It is mostly external content you did not write. Articles, threads, videos, saved posts. It is also where new saves arrive the fastest, because the internet is the internet.
A notes app is built for notes you write. A read-later app is built for sources you did not. Forcing the second into the first is why most PARA setups feel like a clerical job by month three. You paste a URL into Notion or Obsidian, you mean to come back and read the article, and you never do. The URL sits there without its body, unsearchable in any meaningful way, until a year later when the link is dead.
Resources really wants a dedicated tool that captures cleanly, stores the full text, and makes every word searchable. Then your notes app holds only the notes you actually wrote, which is what notes apps are good at.
How the usual PARA tools handle the Resources letter
Same tools people recommend for PARA overall, rated for this one job. Placement is by how well each one handles saved articles and bookmarks, not by how good it is at PARA generally.
Readwise Reader is the strongest single-tool pick for Resources if your workflow is highlight-first. You read inside Reader, highlight as you go, and highlights sync to the Readwise review queue plus any notes app you connect. If PARA Resources for you is mostly "quotes and passages I want to revisit", start here. Reader is part of the Readwise Full subscription (currently listed at $9.99 per month billed annually, or $12.99 monthly, on their pricing page). It wants to be the place you read, not only the place your Resources sit.
Keep is the strongest pick for Resources if your saves are broad, come from many places, and you plan to find things by what they said rather than by folder. Every X bookmark auto-syncs once you connect your X account. Articles save via the Chrome extension, the iOS share sheet, or email. Keep stores the full cleaned body of every article as markdown, and full-text search runs across that body, not just titles and URLs. The whole library exports to markdown, CSV, or JSON so your Resources layer is not locked in. What Keep does not do is Projects and Areas. There is no task model, no daily review, no highlight queue. Use it for the R in PARA and let your notes app handle P and A.
Raindrop is the tidier bookmark-first pick. Tags and nested collections are first-class, and Pro adds full-text search plus a permanent web archive. A clean fit if you think of Resources as "links I want to keep forever, organized by topic" more than "articles I want to search by content".
Notion is where a lot of PARA content lives, because the templates are pretty and the frontmatter is flexible. The web clipper is the slowest on this list by a wide margin and the clipped result is a rough pull, not a clean reading view. Notion is a legitimate home for Projects and Areas. It is a weak home for Resources if Resources means hundreds of articles.
Obsidian can absolutely hold Resources, and if your Projects and Areas are already in an Obsidian vault, the pull to do so is real. You will spend time on plugins, clippers, and folder discipline, and your saves will live as local markdown which is genuinely nice. The cost is that your vault becomes both your writing space and your reading queue, which two populations of people handle well and most do not.
Apple Notes is fast for Projects and Areas on Apple-only setups, and bad for Resources at any volume. Capture is instant, search is weak on article bodies, and there is no extension worth naming.
One honest picture of the stack that works for most people: Obsidian or Notion or Apple Notes for Projects and Areas, plus a dedicated reading tool for Resources. If your Resources are highlight-heavy and you want review queues built in, Reader. If they are article- and X-heavy and you want full-text search and portable markdown, Keep. If they are link-first and tag-first, Raindrop.
A PARA setup that actually survives six months of saves
Here is the shape I would rebuild from scratch today.
- Pick one notes app for Projects and Areas. Whatever one you will actually open on a Monday morning. Mine is Obsidian, yours might be Notion or Apple Notes. It does not matter as long as it is one.
- Put every Project in its own file or page with a clear deliverable at the top and next actions below. Projects finish; when one does, move it to Archives.
- List your Areas explicitly, eight-ish, not forty. Health, finances, the job, a hobby you take seriously, the house. If you cannot name them from memory, you have too many.
- Send every article, X bookmark, newsletter, and save-for-later link to a dedicated reading tool, not your notes app. That tool is your Resources layer. Full text, full search, portable export.
- In your notes app, build thin Resources index pages for the topics you return to, each with a handful of links into your reading tool. "Writing", "product", "espresso", "whatever". The index lives in the notes app. The articles live in the reading tool. You stop trying to store raw external content inside your second brain, which is what killed your last three PARA setups.
- Archives is every app's archive folder. Nothing special.
The thing that makes this work is the split. Your notes app stops being polluted with other people's words. Your reading tool stops trying to pretend it knows what a Project is. Each one does the job it is good at.
Finding what you saved, months later
PARA's promise is that when you need something, you know which of four folders to check. That promise holds for Projects and Areas, where the folder list is short and the names are yours. It falls apart in Resources, because Resources scales fastest and your past self was bad at naming folders. A tag called "writing" in 2024 means nothing to you in 2026.
What holds up at scale is full-text search over the actual article bodies, not over the titles. "That piece about espresso grind size" is not in a folder called espresso. It is a paragraph inside an article called something else entirely, and you remember the paragraph, not the title.
Keep stores every saved article and X post as markdown and indexes every word, which is why the Resources layer works without your past tagging discipline being perfect. It also ships a CLI, an MCP server, an agent skill, and an HTTP API so you can run LLM queries against the whole library. "Pull the three articles I have saved about writing long pieces that would fit a draft on product messaging." That is where a Resources layer stops being an archive and starts being a tool.
This is the same loop a digital commonplace book runs. Save, then build a way to come back to it. PARA gives the folders. The find-again step is what most guides skip.
A few opinions, since everyone has them on PARA
PARA is a good framework because it is simple and it survives you switching tools. It is a weak framework if you take it literally and drop four identical folders into one app. Tiago Forte's own books (Building a Second Brain and The PARA Method, both published through his publisher) are clear that PARA is meant to span your whole digital life, not one app. The Notion-template industry has mostly ignored that.
Resources is the letter everyone underestimates. For most people it is the largest bucket, the fastest-growing bucket, and the one where the contents are not their own writing. Treat it like the read-later problem it actually is.
If you want a piece of that stack, Keep sits in the Resources slot. Every article you save is stored as full markdown, every X bookmark auto-imports, and the whole library is searchable by content, not just by title. Your notes app keeps Projects and Areas. Start saving articles and bookmarks into your Resources layer.
For the step that sits underneath any working PARA setup, the save-and-process part, this content curation workflow walks through discovery, capture, and the weekly review in more detail.