Get AI summaries of any video or article — Sign up free
How to use "folders" in Reflect thumbnail

How to use "folders" in Reflect

Reflect Notes·
5 min read

Based on Reflect Notes's video on YouTube. If you like this content, support the original creators by watching, liking and subscribing to their content.

TL;DR

Use pinned “folder” notes as table-of-contents pages that list backlinks to real notes, keeping the familiar sidebar navigation while staying in a network-note system.

Briefing

Reflect’s folder-style workflow can be recreated as a “hybrid” that lowers the learning curve for people used to Evernote, Apple Notes, or Google Drive—without abandoning the core network-note approach of backlinks and tags. The key idea is to keep the familiar mental model of “folders” (a table-of-contents list of related items) while still organizing content the Reflect way: daily notes link outward to dedicated pages, and those links power navigation.

The first and easiest method uses pinned “folder” notes. Instead of physically placing notes inside a folder, a dedicated page acts like a folder by serving as a table of contents. For example, a pinned “Projects” page can list active projects as backlinks—each entry is a backlink to a separate project note. The practical difference is that the “folder” is a single page pinned to the left sidebar for quick access, while the actual content lives in linked notes. The transcript’s examples include a “Projects” folder listing current work, plus other pinned lists such as “Growth ideas,” a customer support FAQ list that grows as questions arrive, and article drafts. The emphasis is that the real mechanism remains backlinks from daily notes to the relevant project, article draft, or other item; the pinned page simply makes those relationships feel like folder navigation.

The second method uses tags to approximate folder lists. A “Projects” tag can be applied to notes that belong to a project category. From Reflect’s “all notes” view, clicking a tag like “projects” produces a list of all tagged notes—functionally similar to a folder’s contents, though not identical. This tag-driven approach can also be extended to other categories such as “article drafts” or “meetings,” letting users treat tag collections as folder-like entry points.

Both approaches aim to make the network-note system feel intuitive. As users start creating backlinks in their daily notes—such as linking a brainstorm to “growth ideas,” or linking an article draft to a specific topic—they become more aware of what should be linked next. The workflow described is incremental: create a backlink note for the specific topic, tag it appropriately (e.g., “article draft”), and then link to it from daily work. The result is a stepping stone away from folder thinking and toward Reflect’s backlink-and-tag organization.

A final caveat matters: the hybrid setup is not an argument for replacing network note taking with folders. The transcript frames folders as a digital habit that doesn’t match how brains naturally organize information, and positions this technique as a short-term bridge. The payoff is expected quickly—after a few days to a week of mild friction, backlinks and tags start to feel natural, and the folder approach becomes harder to imagine returning to.

Cornell Notes

Reflect users coming from folder-based apps can ease into network note taking by building “folder-like” entry points. One approach creates dedicated pinned notes (e.g., a “Projects” page) that function as a table of contents by listing backlinks to individual project notes. A second approach uses tags (e.g., a “projects” tag) so clicking a tag shows all related notes in the “all notes” view. Both methods help people see what they should backlink from daily notes, making the shift away from folders feel faster and more intuitive. The bridge is meant to teach backlinks and tags, not to replace network organization permanently.

How can a single page behave like a folder in Reflect without storing notes inside it?

Create a dedicated “folder” note that acts as a table of contents and pin it to the left sidebar for quick access. Then populate it with backlinks to the actual notes (e.g., a “Projects” pinned page listing current project notes as backlinks). The daily note still links to the relevant project note; the pinned page simply provides the folder-like navigation layer.

What’s the practical difference between using a pinned “folder” note and relying on tags?

Pinned “folder” notes work like a curated table of contents: the page lists specific items via backlinks, such as “Growth ideas,” “Customer support FAQ,” or “Article drafts,” and stays visible in the sidebar. Tags work more like dynamic collections: applying a tag like “projects” to notes lets users click the tag in the “all notes” view to see every note with that tag, such as all project-related notes.

Why does the hybrid approach make backlinks easier to learn?

As soon as users start linking from daily notes—like backlinking a brainstorm to “growth ideas” or linking an article draft to a topic note—they can clearly see what should be linked next. The folder-like pages (pinned lists or tag views) make those backlink targets obvious, turning organization into a guided habit rather than a blank-page decision.

How might someone organize an article-draft workflow using these ideas?

First, create a topic note (e.g., “The ups and downs of remote work”) and then add an “article draft” tag to it. Next, when working in daily notes, backlink to that draft note from the relevant work session. The pinned “folder” page or the “article drafts” tag view then becomes the quick entry point for future work.

What warning is given about treating folders as the long-term solution?

Folders are framed as a digital habit that doesn’t match how brains naturally organize information. The hybrid setup is presented as a temporary bridge to help users learn backlinks and tags, not as permission to abandon network note taking permanently.

Review Questions

  1. What are the two main techniques used to mimic folder navigation in Reflect, and how does each one generate a list of related notes?
  2. In the pinned “folder” approach, where do the actual project or draft notes live, and what relationship connects them to the pinned page?
  3. How does backlinking from daily notes change the way users decide what to organize next?

Key Points

  1. 1

    Use pinned “folder” notes as table-of-contents pages that list backlinks to real notes, keeping the familiar sidebar navigation while staying in a network-note system.

  2. 2

    Treat backlinks as the core mechanism: daily notes should backlink to the relevant project, draft, or topic note.

  3. 3

    Create a “Projects” pinned page (and similar lists) to represent active work items like growth ideas, customer support FAQs, and article drafts.

  4. 4

    Use tags as a second, dynamic way to approximate folders by clicking tag names in the “all notes” view to see all related notes.

  5. 5

    Expect a short adjustment period (a few days to about a week) before backlinks and tags feel natural.

  6. 6

    Use the hybrid setup as a stepping stone toward full network note taking, not as a reason to keep folder thinking long-term.

Highlights

A “folder” in Reflect can be a pinned note that functions purely as a table of contents, populated by backlinks to separate notes.
Tags provide a folder-like experience through dynamic lists: clicking a tag such as “projects” surfaces every note carrying that tag.
The fastest learning path comes from backlinking from daily work into those folder-like entry points, making the next link feel obvious.

Topics