Get AI summaries of any video or article — Sign up free
Enhanced Mind Expansion Dashboard – Notion Knowledge Management System thumbnail

Enhanced Mind Expansion Dashboard – Notion Knowledge Management System

August Bradley·
6 min read

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

TL;DR

Readwise integration now feeds both books and other media into one media database, simplifying how sources are organized and surfaced.

Briefing

A redesigned “Mind Expansion” dashboard in Notion streamlines quick capture and faster retrieval by swapping toggle-heavy layouts for gallery-first views, while keeping the same underlying databases and Readwise automation. The core change is an interface built around speed: recent notes and media appear as large, tappable blocks with a single “giant new” button for rapid entry, and most lists default to “today/yesterday” (or a recent time window) so resurfacing happens at the right moment.

At the system level, the dashboard keeps the same database structure but tightens how media flows in. Readwise integration now feeds both books and other media into a single media database, eliminating the older split between books and general media. Notes and ideas live in a dedicated “notes in ideas vault,” courses remain independent in a separate “course vault,” and everything else sits in a “media vault.” The knowledge area is renamed from “knowledge lab” to “knowledge vault” to make the system’s vocabulary consistent: anything that functions like a vault is labeled “vault,” distinct from pipelines.

The biggest usability upgrade is the move to gallery view for the notes-and-ideas area. Instead of a toggle that adds extra clicks, the dashboard defaults to a filtered set of entries (typically today or yesterday) and lets users quickly shift to older ranges (week or month) by changing the filter designation rather than creating new filters. Gallery view turns recent entries into prominent blocks, making it easier to open the right note without hunting through tables. The same “quick entry” pattern is applied across other dashboard zones—especially the “action zone” and “command center”—where a top-positioned toggle expands into a gallery view with a large button designed for one-handed, low-friction capture.

On the media side, the dashboard uses list views where they fit best (narrow columns) and gallery views where visuals matter (books). Books appear as full-cover gallery cards by setting the image display to “fit image,” and sorting prioritizes “last highlighted” and “last edited” so actively engaged titles rise to the top. Articles also use list view and are filtered to a recent window (up to a month), sorted by recent interaction. Twitter threads are saved with automation via Readwise thread saving, and each thread’s posts become individually accessible items that can be tagged and marked with statuses like completed.

Videos and podcasts are handled with lighter automation: videos are clipped into Notion via the Notion Web Clipper, while podcast snippets are pulled in using an air-quote podcast workflow. The dashboard then links these media items back into knowledge-vault entries through a template-driven structure.

That template is the second major pillar of the redesign. Each knowledge-vault item includes a table of contents for headings and a “references” section that automatically pulls in related notes and related media from the notes-and-ideas database and the media database. The result is a single workspace where a user can jump between headings and immediately see the most recently touched supporting materials—sorted by recency—without manual reorganization.

Finally, the redesign is validated on mobile: the same vault sections appear as big, easy-to-tap blocks, with the “new” button and media lists working smoothly through swipes and quick opens. The overall payoff is a dashboard that feels cleaner, more engaging, and faster for both ingesting new ideas and resurfacing relevant context during review sessions.

Cornell Notes

The redesigned “Mind Expansion” dashboard improves speed and retrieval in Notion by prioritizing gallery-first layouts and large capture buttons while keeping the same database architecture. Readwise integration now feeds books and other media into one media database, and the dashboard organizes content into vaults: notes in ideas, courses, media, and knowledge vault. Notes and ideas default to recent filters (today/yesterday) in gallery view to reduce clicks and make recent entries visually scannable. Knowledge-vault templates then auto-populate a references section by pulling in linked notes and linked media, sorted by recency, so each knowledge item becomes a self-contained workspace. Mobile usability improves further because the big buttons and blocks make quick entry and navigation easier.

What changed in the dashboard’s data flow, and why does it matter for day-to-day use?

Readwise integration was adjusted so it feeds both books and other media into the same media database. That removes the older separation between a book database and a general media database, leaving one media vault for most sources. The practical impact is simpler navigation and consistent filtering/sorting across media types, so recently engaged items can rise to the top regardless of whether they came from Kindle highlights, articles, or other Readwise-supported sources.

How does the new notes-and-ideas interface reduce friction compared with the earlier toggle-based approach?

Notes and ideas move to gallery view and remove the toggle. The dashboard defaults to a recent time filter (typically today or yesterday), and older ranges (week or month) are reached by changing the designation rather than adding new filters. Gallery view turns entries into large blocks, and a giant “new” button sits in a prominent location for faster capture—one less click and less hunting for the right note.

Why are different view types (gallery vs list vs table) used for different content?

Gallery view is used where visuals help scanning—books show full covers using the “fit image” property. List view is used for cleaner narrow-column layouts, especially for articles and other media categories where text and metadata matter more than cover art. Table views still exist for deeper inspection, but the system favors list or gallery for day-to-day speed and readability.

How does the knowledge-vault template create a self-contained workspace for each knowledge item?

Each knowledge-vault entry uses a template that includes a table of contents and a references section. The references section pulls in linked notes and linked media automatically via self-referencing list views: notes come from the notes-and-ideas database filtered by the knowledgevault property, and media comes from the media vault filtered similarly. Sorting prioritizes recent edits/touches, so the most relevant supporting material appears first.

What’s the workflow for capturing and re-accessing media sources like Twitter threads, videos, and podcasts?

Twitter threads are saved with Readwise thread saving (with options like saving to comments or saving via DM), and each post in the thread becomes accessible as part of the saved thread item. Videos are added using the Notion Web Clipper, and users can watch directly while writing notes (sometimes using a separate window for notes). Podcasts are handled by saving snippets through an air-quote podcast app workflow, then bringing those snippets into Notion so they can be revisited or shared with transcripts.

How does mobile layout reinforce the redesign’s goal?

On iPhone, the dashboard uses the same vault structure but emphasizes big buttons and block-based navigation. The notes-and-ideas “new” action is easy to tap, recent entries remain accessible, and media lists open cleanly with swipe navigation. The interface is described as working even better on mobile because the larger touch targets make quick capture and retrieval more reliable.

Review Questions

  1. How does combining books and other media into a single Readwise-fed media database change filtering and sorting across the dashboard?
  2. What specific template mechanics make a knowledge-vault entry automatically gather related notes and related media?
  3. Why might gallery view be preferred for books while list view is preferred for articles in this system?

Key Points

  1. 1

    Readwise integration now feeds both books and other media into one media database, simplifying how sources are organized and surfaced.

  2. 2

    The dashboard shifts from toggle-heavy navigation to gallery-first layouts for faster scanning and fewer clicks when capturing new notes.

  3. 3

    Notes and ideas default to recent filters (today/yesterday) in gallery view, making resurfacing and quick entry the default behavior.

  4. 4

    Books use full-cover gallery cards via the “fit image” property, while articles and other text-heavy sources use list views optimized for narrow columns.

  5. 5

    Knowledge-vault templates auto-populate a table of contents plus a references section by pulling in linked notes and linked media, sorted by recency.

  6. 6

    Twitter threads, videos, and podcasts are ingested through different capture paths (Readwise thread saving, Notion Web Clipper, and podcast snippet workflows) but end up linked into the same vault structure.

  7. 7

    Mobile usability improves because the redesigned interface uses larger touch targets and block-based navigation for quick capture and retrieval.

Highlights

The redesign’s centerpiece is speed: recent notes appear as gallery blocks and a prominent “giant new” button enables rapid capture with one fewer interaction.
Readwise integration consolidates books and other media into a single media database, making recency-based sorting work across source types.
A knowledge-vault template turns each knowledge item into a self-contained workspace by auto-linking related notes and related media into a references section.
Full book covers are displayed using the “fit image” setting, while articles favor clean list views for fast scanning in narrow columns.
On mobile, the same vault structure becomes more effective because big buttons and blocks make quick entry and navigation easier.