Notion Masterclass: Build a Second Brain from Scratch

Introduction to the PARA Method

• The PARA method is a system for organizing digital information, including tasks, notes, projects, and web clippings, developed by Thiago Forte as part of his "Building a Second Brain" course and book 0s.
• The system is structured around four primary categories: Projects, Areas, Resources, and Archive 0s.
• A complete PARA system can be built from a blank Notion page, incorporating task management, note-taking, and dedicated sections for each of the four PARA staples 0s.
• The system includes an archive section designed to store completed tasks or items that are no longer needed in the active workspace 0s.
• A free template of the PARA system is available for users to add to their own Notion workspaces 0s.

Advanced Productivity Templates

• The "Ultimate Brain" template is a more comprehensive productivity system for Notion that includes the PARA method, a robust task manager with recurring tasks and subtasks, a "Getting Things Done" (GTD) dashboard, a "My Day" planning dashboard, a note-taking system, and a recipe tracker 0s.
• The PARA dashboard provides a high-level view of the entire system and incorporates inboxes for tasks and notes, allowing for quick capture of information without needing to navigate to specific project or area folders 0s.
• Areas and resources are merged into a single database within the system to manage both broad life categories and topic-based reference information 0s.
• Individual area dashboards allow users to track ongoing or completed projects, store reference materials, and view notes associated with that specific area of life 0s.
• Projects within the system are designed to be flexible, allowing users to associate both tasks and notes directly with a specific project 0s.

Notion as a Second Brain

• Notion is presented as a superior tool for building a "second brain" system because it allows users to consolidate tasks, notes, and reference materials in one location, avoiding the need to use multiple disparate applications 0s.
• The PARA model serves as the organizational framework for this system, categorizing all information into four distinct folders or lists based on their level of actionability 42s.
• Projects are defined as the most actionable category, consisting of groups of tasks that are linked to a specific, common goal 1m15s.
• Areas represent spheres of activity or "buckets" of life that require maintenance over time, such as personal life, business ownership, or specific professional roles 1m25s.
• Resources are defined as topics or themes of ongoing interest, such as hobbies or subjects of study, where users can store clipped articles and notes 1m35s.
• The archive category is the least actionable, serving as a repository for information that is no longer relevant but should be kept for potential future reference rather than deleted 1m45s.

Visualizing and Structuring PARA

• Whimsical is recommended as a free tool for creating mind maps and flowcharts to visualize the PARA structure 35s.
• Notion’s database-driven architecture provides greater flexibility than traditional folder-based systems, allowing for the creation of customized dashboards and linked databases 2m6s.
• The implementation of the PARA model in Notion requires databases for both tasks and notes, which serve as the granular units of information within the system 2m30s.
• Unlike traditional implementations of PARA, the Notion-based system allows notes to be associated with projects, resources, or areas, reflecting the increased flexibility of the platform 2m55s.
• The specific system being built excludes goals and milestones, focusing instead on the core PARA components and the integration of tasks and notes 2m20s.

Database Configuration and Setup

• The PARA (Projects, Areas, Resources, Archives) system structure utilizes a specific database configuration where areas and resources are combined into a single database to improve visual clarity and functionality on smaller screens 0s.
• A "PARA dashboard" page is created as the primary interface, set to full width with a book icon 18s.
• A dedicated "databases" page is established within the dashboard to house source databases, allowing for centralized structural management while using linked databases on the main dashboard 32s.
• The system requires four primary databases: tasks, notes, projects, and a combined areas/resources database 1m25s.
• The areas and resources database uses tags to visually differentiate between the two categories, simplifying the process of assigning tasks or notes to a specific area or resource 1m45s.

Task and Note Database Properties

• The tasks database is configured by removing the default tags property and adding a status property, which allows for a default status upon the creation of a new row 2m15s.
• A date type property labeled "due" is added to the tasks database to track deadlines 2m55s.
• While a checkbox property can be used for task completion, a status property is recommended for its ability to automatically assign a default status to new entries 2m35s.
• The task database is initialized with a status property containing the default options of "not started," "in progress," and "done." 0s
• A notes database is created to categorize information into two types: original notes generated by the user and web clips captured from the internet using tools like the Notion web clipper or Save to Notion extension. 15s
• A URL property is added to the notes database to distinguish between web clips and original notes, allowing for the creation of separate views based on whether a URL is present. 35s
• A formula property named "base URL" is implemented to extract the domain from a link, which facilitates the grouping of web clips by their source website. 55s

Project and Resource Database Configuration

• The project database is configured with a status property using the default options of "not started," "in progress," and "done." 2m6s
• The tags property is removed from the areas and resources database and replaced with a status property renamed to "type." 2m20s
• The "type" property in the areas and resources database is configured with two options: "area" (colored orange) and "resource" (colored purple), with the status set to "in progress" to maintain a single grouping. 2m35s
• A checkbox property labeled "archive" is added to the databases for projects, areas, and resources to assist with the PARA model, while tasks are excluded from this property because they are archived upon completion. 3m15s
• An archive property is created using a checkbox to allow for the filtering and removal of items from active views 0s.

Establishing Database Relations

• The database structure is designed to approximate the PARA model by relating tasks, projects, notes, and areas/resources to one another 35s.
• Areas are defined as life buckets that contain projects and resources, representing a departure from traditional implementations where these categories are kept as separate lists 53s.
• A two-way relation is established between the tasks and projects databases, allowing tasks to be linked to a single project and enabling the viewing of related tasks directly within the projects database 1m15s.
• One-way relations can be created by opting not to show the reciprocal property on the target database, which prevents the link from appearing in both locations 1m48s.
• The notes database is configured with relations to the projects database and the areas and resources database 2m6s.
• Relation limits can be set to one page to improve user experience, though these limits can be disabled if a note needs to be associated with multiple projects or resources 2m35s.
• A relation is added to the projects database to link projects to the areas and resources database, specifically to associate projects with areas 3m15s.

Hierarchical Organization and Rollups

• A relation is created within the "Areas and Resources" database to link resources to their respective root areas, allowing for hierarchical organization 0s.
• The relation is configured to allow multiple resources per area, but the "root area" property is restricted to a one-page limit to ensure each resource is associated with only one area 25s.
• A rollup property is added to the "Notes" database to identify the root area of a note that is contained within a specific resource 1m5s.
• The rollup functions by reaching through the resource relation to retrieve the root area information associated with that resource 2m5s.
• This rollup configuration enables the filtering of notes within an area dashboard, allowing users to view notes that are either directly related to an area or contained within a resource that belongs to that area 1m35s.

Project Template Construction

• Following the completion of the database structure, the next steps involve creating templates for projects, areas, and resources to standardize the dashboard layouts 2m35s.
• The final stages of the build process include constructing the overall home dashboard and performing aesthetic refinements and cleanup 2m55s.
• The PARA dashboard implementation focuses on creating a project template within the projects database, rather than creating templates for tasks or notes. 0s
• A "Quick Links" toggle block is recommended for templates, containing a table of contents created via the "/toc" command to facilitate easier navigation on mobile devices where layouts are compressed into a single column. 35s
• A callout block titled "Project Overview" serves as a space for a project synopsis or "North star," and can be styled with a default background color to create a clean outline. 1m15s
• Within a callout block, pressing enter followed by the tab key allows for the creation of new blocks inside the existing callout. 1m35s
• A two-column layout is established for tasks and notes by using the "/2c" command, with horizontal rules added beneath the headings for visual separation. 1m55s
• Notion allows for the adjustment of column widths on standard-width pages by using handles, which enables multi-column layouts to be wider than the default page width while keeping single-column text restricted for better readability. 2m15s

Linked Database Views and Filters

• Linked databases are created by typing the desired view type, such as "list," and selecting the relevant database. 2m45s
• When creating a linked database view, selecting "new empty view" is necessary to ensure the specific view format—such as a list view—is applied rather than defaulting to the existing table format from the parent database. 3m0s
• Status properties in Notion can be configured to display as a checkbox rather than a select menu, which limits the status options to either "to do" or "complete" 0s.
• Using a checkbox for status properties prevents the use of an "in progress" status, which may be a consideration for those who prefer Kanban-style workflows 15s.
• Advanced filters are used to create a self-referential filter by setting the project relation to contain the project template, which automatically updates to the specific project name once the template is applied 42s.
• To maintain a comprehensive view of a project, tasks are grouped by their "done" status rather than filtering out completed items 1m15s.
• The "in progress" status group can be hidden from the view if the checkbox property is being utilized 1m25s.
• Database titles can be hidden for aesthetic purposes, and tasks can be sorted by their due date in ascending order 1m55s.
• A list view for notes is created using the same self-referential filter logic, ensuring that notes are automatically associated with the specific project 2m10s.
• A project template can be set as the default for all views within the projects database, ensuring that every new project automatically inherits the configured task and note structures 2m35s.
• Once the template is applied to a new project, any tasks added within that project view are automatically related to that specific project 2m55s.

Resource and Area Template Design

• Two distinct templates are required for the Areas and Resources database: an "Areas" template and a "Resources" template 0s.
• The "Resources" template is designed to be simpler, containing only notes and web clips 0s.
• When creating the "Resources" template, the type property should be set to "resource" so that it is automatically applied when the template is used 25s.
• A "quick links" section is created within the template, followed by a two-column layout for "Notes" and "Web clips" 42s.
• A list view for notes is configured with an advanced filter where the area and resource property contains the "resource template" 1m5s.
• An additional filter is applied to the notes view to ensure that only items where "archive" is unchecked are displayed 1m25s.
• A filtration rule is added to the notes view to ensure that only notes where the URL is empty are displayed 1m45s.
• The notes view is copied and pasted to create the "Web clips" view, where the filtration rule is updated to show only items where the URL is not empty 2m6s.
• The "Web clips" view is grouped by the "base URL" property, and the database title is hidden 2m25s.
• An archive filter is added to the previously created project template to ensure that archived notes do not appear within projects 2m45s.
• The "Resources" template is not set as a default template, as it may be used interchangeably with an "Areas" template 3m10s.
• The "Areas" template is created with the type property set to "area" 3m35s.
• The "Areas" template includes a "quick links" toggle block and a two-column layout featuring "Area projects" and "Area resources" 3m50s.
• The area template is set to full width to accommodate a new section titled "area notes" at the bottom of the page. 0s

Dashboard View Configuration

• A board view is created for projects, using the projects database as the source and grouping items by status. 25s
• A self-referential filter is applied to the project board view so that only projects related to the specific area template are displayed. 55s
• An additional filter is added to the project board view to exclude archived projects by ensuring the archive property is unchecked. 1m8s
• The layout for the project board view is configured with a small card size and the card preview set to page cover. 1m17s
• A gallery view is created for resources, linking to the areas and resources database, with the card size set to small and the card preview set to page cover. 1m30s
• The resource gallery view uses a self-referential filter where the root area contains the area template, and an additional filter ensures only unarchived resources are shown. 1m45s
• A list view is established for area notes by linking to the notes database. 2m12s
• The notes list view uses a self-referential filter where the area and resource property contains the area template. 2m25s
• The notes list view is converted into a group to allow for an "or" filter, which includes notes where the root area roll-up contains the area template. 2m38s
• The notes list view includes a filter to ensure only unarchived notes are displayed. 2m55s
• A separate tab for web clips is created by duplicating the notes view and filtering for entries where the URL is not empty. 3m5s
• The web clips view is configured to show the URL property and is grouped by the base URL, with the "no base URL" option hidden. 3m25s
• The notes template is updated by configuring grouping options to organize by area and resource, allowing for better visibility of where notes are located 0s.

Dashboard Layout and Inbox Setup

• Following the completion of database templates, the process shifts to constructing the dashboard, followed by the creation of an archive page and aesthetic refinements 13s.
• A "quick links" block is added to the dashboard, and a two-column layout is initiated to organize different sections 24s.
• Heading sections for tasks and notes are created, separated by horizontal lines 35s.
• A layout technique is used to prevent stacking issues by dragging elements to span the full width of the page, ensuring that tasks, notes, projects, and areas/resources appear in the desired order 50s.
• The dashboard structure is finalized by adding headings for projects and areas/resources, after which the temporary column-structuring blocks are deleted 1m25s.
• Linked databases are implemented using specific views: list views for tasks and notes, a board view for projects, and a gallery view for areas and resources 1m40s.
• A "task inbox" is created as a list view to serve as a capture point for new items before they are processed into specific PARA (Projects, Areas, Resources, Archives) databases 1m55s.
• Properties for the task list are configured to display "done" and "due" statuses, with the "done" status represented as a checkbox 2m15s.
• The inbox view is filtered to show only tasks where the project field is empty, which facilitates moving tasks out of the inbox once they are assigned to a project 2m55s.
• An additional filter is applied to the inbox view to exclude tasks marked as complete, allowing for the management of multiple completion statuses 3m15s.

Task and Note Inbox Management

• The task inbox is configured by removing completed tasks from the view and hiding the database title. 0s
• A "next seven days" view is created for the task inbox by filtering for tasks due on or before one week from the current date, while also displaying the project property for each task. 15s
• The "next seven days" view is sorted by the due date in ascending order. 48s
• A "completed" view is added to the task inbox, filtered to show only tasks marked as done, and sorted by the due date in descending order. 54s
• A note inbox is established using a list view linked to the notes database, with the URL property displayed to facilitate access to web-clipped content. 1m15s
• The note inbox is filtered to display items where the area, resource, and project properties are empty, and where the archive status is unchecked. 1m45s

Dashboard Project and Area Views

• A projects area is created using a board view grouped by the status property, with card previews set to page covers and card sizes set to small. 2m13s
• The projects board view is filtered to show only projects where the archive status is unchecked. 2m45s
• A gallery view is initiated for the areas and resources database. 2m56s
• To configure the dashboard view, the card preview is set to "page cover" to display images, and the card size is adjusted to "small" to increase visibility 0s.
• An example area titled "Music" is created using the area template, and a cover image is added to ensure it appears on the dashboard 15s.
• Advanced filters are applied to the dashboard to ensure only items where the "archive" property is unchecked are displayed 35s.
• A specific filter is added to the areas view to ensure the "type" property is set to "area," while the resources view is filtered to ensure the "type" property is set to "resource" 50s.
• The database title is hidden for aesthetic purposes, and the view is renamed to "Areas" 1m12s.
• The areas view is duplicated to create a separate resources view, with the filter updated to reflect the "resource" type 1m18s.
• The area template is set as the default specifically for the areas view, and the resource template is set as the default specifically for the resources view 1m33s.
• Within the area template itself, the resource template is set as the default for the gallery view, ensuring this configuration persists when new areas are created 2m12s.

Archive Page Implementation

• An archive page is created to complete the P.A.R.A. (Projects, Areas, Resources, Archives) model, using a trash icon to represent the archive section 2m35s.
• The archive page is organized into sections for completed tasks, archived notes, archived projects, and archived areas and resources 2m55s.
• A linked database in list view is created for the tasks database, filtered to show only items where the "done" status is complete 3m15s.
• A linked database for notes is created on the archive page, filtered to display only items where the "archive" property is checked 3m45s.
• The archive section is organized by creating list views for projects, areas, and resources, each filtered to display items where the "archive" property is checked 0s.
• For the areas and resources database, two separate views are created using advanced filters: one for items where the type is "area" and one for items where the type is "resource" 15s.

Aesthetic Refinements and Interface Cleanup

• Aesthetic adjustments are made to the dashboard by accessing the three-dot menu to customize the page and minimize visible elements, such as backlinks 45s.
• A two-column layout is implemented to display the databases and the archive side-by-side 1m0s.
• Database properties are customized to hide unnecessary information, such as base URLs and root areas, to ensure a cleaner interface across all pages 1m15s.
• Within the project database, the "tasks" property is set to "always hide" because these items are accessible through linked databases 1m30s.
• The area and resource templates are configured to hide notes, projects, and resources, while keeping the "root area" property visible to provide a link back to the parent area 1m45s.
• The "notebooks inbox" is updated to show area and resource properties, allowing users to categorize items directly from the inbox 2m15s.
• The relation picker for areas and resources is customized to show the "type" property, which helps distinguish between areas and resources at a glance during the sorting and processing of information 2m30s.

Additional Resources and Support

• A template version of the PARA system is available for free in the description of the video. 0s
• The Ultimate Brain template is a more advanced productivity system that includes the PARA framework, a robust task management system with recurring tasks, subtasks, and a Getting Things Done (GTD) processing dashboard. 15s
• The Ultimate Brain template includes tutorials on automating recurring tasks, active support from a team member named Alex, a 30-day refund guarantee, and access to an active community of users who share customizations and support. 35s
• A discount of $50 is available for the Ultimate Brain template by using the code "Let's go 2023" at ThomasJFrank.com/brain. 1m5s
• The website ThomasJFrank.com features a "Learn Notion" mega menu, developed by Martin, which offers free learning tracks covering Notion fundamentals, databases, formulas, and automation. 1m15s
• The website provides a Notion API crash course that covers JavaScript coding and the use of the Notion API. 1m35s
• A newsletter is available through the website to provide updates on new tutorials, templates, and various Notion reference materials. 1m45s
• Questions regarding Notion can be directed to the comment section or via Twitter at the handle "TomFrankly." 1m55s