Organizing Your Documents in Reader

TL;DR

Reader organizes content using RSS folders for feed navigation and filtered views for metadata-driven document collections.

Briefing Cornell Notes

Briefing

Reader’s document organization tools focus on two goals: quickly finding saved items later and building reusable collections that stay up to date. The core shift is moving from one-off search to persistent organization—either by grouping RSS feeds into folders or by creating filtered views that automatically assemble documents based on metadata like tags, authors, formats, reading progress, and more.

For RSS subscribers, Reader supports traditional folder-style organization for feeds. Users can go to the Manage Feeds page, create a new RSS folder, and then drag and drop feeds into it. These folders appear in the right-hand sidebar and can be used to process subsets of feeds or handle individual feeds in batches. On mobile, RSS folders are accessed by opening a feed and tapping the relevant button.

Filtered views are the more flexible system. A filtered view is a dynamic subset of documents defined by combinations of attributes—examples include document type (such as PDFs and videos), day added, and reading progress. Users can also create custom views based on tags, and the transcript gives a concrete workflow: while preparing an onboarding series, the creator tagged multiple scripting and filming tutorials with “video skills.” Instead of searching across many tabs, they clicked the tag to collect every matching document, then saved that result as a filtered view pinned to the sidebar. If a tag isn’t visible in the list view, Manage Tags can be used to create new filtered views or assign additional tags to an existing view.

The key advantage over traditional folders is that filtered views are not single-location containers. A document can belong to multiple filtered views at once, avoiding duplicated copies and clutter. Filtered views also update automatically: when documents meet (or stop meeting) the filter criteria, they appear (or disappear) without manual re-sorting.

An advanced example shows how multiple filter parameters can be combined to build a weekly newsletter pipeline. The view is based on the “Community Building” tag, further restricted to documents with at least five highlights, and limited to items that have been archived—using logical “AND” to require all conditions. The resulting collection becomes a ready-made set of sources for the next newsletter roundup.

Reader also adds practical controls for managing and using these collections. New filtered views are automatically pinned to the sidebar on desktop; on mobile they can be found via search. Users can add a counter badge to show how many documents are in a view and adjust split view to see where items live—such as seen status for feed items, inbox/ later/ archive location for library items, or “None” to view everything together.

Finally, filtered views can be shared through bundles. Creating a public bundle generates a custom landing page for the filtered view. Recipients can open the original documents or subscribe to the bundle in their own Reader account to receive both existing and future documents that match the view. Because the bundle only includes documents present at the time the link is created, refreshing the link is recommended when new items should be included. Overall, RSS folders handle feed navigation, while filtered views provide the durable, multi-project organization that keeps collections current.

Cornell Notes

Reader offers two ways to organize saved items: RSS folders and filtered views. RSS folders group feeds for easier navigation by letting users drag and drop feeds into named folders. Filtered views are dynamic collections built from metadata—tags, authors, formats, reading progress, day added, and more—so a single document can appear in multiple places without duplication. Filtered views also update automatically as documents change, unlike traditional folders that require manual moving. Collections can be pinned, counted, and customized with split view, and they can be shared publicly via bundles that include documents matching the filter at the time the link is created.

How do RSS folders work in Reader, and when would someone use them instead of filtered views?

RSS folders are created from the Manage Feeds page using “create new folder.” After a folder exists, feeds can be dragged and dropped into it, and the folder appears in the right-hand sidebar. They’re mainly useful for organizing feed navigation—especially when someone wants to process or review subsets of feeds at a time. On mobile, RSS folders are accessed by opening a feed and tapping the relevant button. Filtered views, by contrast, organize documents based on metadata and are better for cross-cutting collections that aren’t tied to feed structure.

What makes filtered views different from traditional folders?

Filtered views are dynamic and multi-location. A document can exist in multiple filtered views simultaneously, which avoids duplicating the same item across multiple folders. Filtered views also update automatically: when documents start or stop meeting the criteria (for example, a tag changes or reading status changes), the view updates without manual add/remove work. Traditional folders require explicit moving and duplication if the same document needs to appear in multiple project contexts.

How can tags be used to build a filtered view?

A tag-based workflow starts by collecting documents that share a tag (for example, clicking a tag like “video skills” to gather all related tutorials). From there, the user saves the result as a filtered view. If a tag isn’t easily accessible in the list view, Manage Tags can be used to create a new filtered view or assign additional tags to an existing view. This turns repeated searching into a reusable, pinned collection.

How does the newsletter example combine multiple filter criteria?

The advanced example builds a view using several parameters together. It starts with the “Community Building” tag, then adds a highlights threshold—documents with greater than or equal to five highlights. It also restricts results to items that have been finished reading and sent to Archive. The transcript notes the use of “AND” logic to require all conditions at once, though “or” can be used for more flexible matching.

What interface tools help users manage and interpret filtered views?

Filtered views can be pinned to the sidebar on desktop and accessed via search on mobile. Users can add a counter badge showing how many documents are in the view. Split view can be adjusted to show where items exist: “seen status” for feed items, “location” for library items (inbox, later, or archive), and “None” when a view includes both feed and library items and the user wants to see everything together.

How do bundles share filtered views, and what’s the privacy/refresh implication?

Bundles are created by opening a filtered view and clicking “create public link.” The result is a public bundle with a custom landing page. Recipients can open the original documents or subscribe to the bundle in their own Reader account to receive existing and new documents. The bundle includes only documents present at the time the link is created, so if new documents should be included later, the link should be refreshed—even though the URL stays the same.

Review Questions

What are two reasons filtered views reduce clutter compared with traditional folders?
Describe a practical scenario where combining tag, highlights, and archive status would be more useful than a simple search.
When sharing a filtered view via a bundle, what determines which documents recipients will see, and why might a refresh be necessary?

Key Points

1
Reader organizes content using RSS folders for feed navigation and filtered views for metadata-driven document collections.
2
RSS folders are created in Manage Feeds and populated by dragging and dropping feeds into named folders.
3
Filtered views are dynamic subsets defined by attributes such as tags, author, format, day added, and reading progress.
4
A single document can appear in multiple filtered views without duplication, and filtered views update automatically as criteria change.
5
Split view and counter badges help users understand where items live and how many match a view.
6
Filtered views can be shared as public bundles, letting others open or subscribe to the collection.
7
Bundles include only documents that match the filtered view at link creation time, so refreshing the link is important when new items should be included.

Highlights

Filtered views let one document live in multiple collections at once, avoiding duplicated copies that traditional folders require.

Filtered views update automatically when documents meet or stop meeting criteria—no manual re-sorting needed.

Bundles share a filtered view as a public link, but recipients only get documents that were included when the link was created.

Topics

RSS Folders
Filtered Views
Document Tags
Split View
Public Bundles