Notion Office Hours: Building from Scratch 🌱

Building a Notion workspace from scratch hinges on one practical idea: start with a structured “PARA-style” system (Projects, Areas, Resources, Archives) but let Notion’s database relationships do the heavy lifting. Instead of stuffing everything into one master list, the setup uses a small number of core databases—especially a master tasks database—then “surfaces” the right slices of that data through dashboards, filtered views, and embedded databases. The payoff is a workspace that stays usable as it grows, because daily planning, weekly review, and long-term goals all pull from the same underlying records.

The session begins with workflow questions and limitations. Automation is constrained by the lack of a Notion API, but speed comes from shortcuts and external helpers like TextExpander and Alfred. Calendar integration is possible via embedding a shared Google Calendar, though it’s described as visually “hideous,” and the approach is treated as a workaround until tighter integration arrives. For capturing work, the Notion clipper is positioned as a key tool: it can save web pages into the correct database (like Reading & Learning) while pulling in titles, URLs, and images.

The PARA framework is clarified with a distinction that drives the whole build. Areas are ongoing responsibilities without a fixed end date—examples include health, product development, or volunteering roles. Projects have defined start and end dates, a set of tasks, and an outcome. Resources are reusable notes and reference material that can be pulled into many contexts. Archives are for completed or inactive items. The presenter emphasizes adaptation: the structure can be reshaped to match how someone thinks, rather than treated as a rigid template.

From there, the build focuses on interconnected databases. A Projects database is created as a database (not just a page) so it can hold properties like status, dates, assignees, and an “outcome” field. A Master Tasks database is then created as a simple table with due dates, tags, checkboxes, and a relation back to Projects. Once tasks relate to projects, tasks can be displayed inside project pages automatically, giving a high-level view without duplicating data.

Areas are set up as pages containing inline databases (or embedded views) that list projects tied to each area. The journal is treated as another connected system: daily entries include properties for feelings, effectiveness, checklists, and relations to tasks and projects, then are wrapped with templates so new entries are consistent. Dashboards tie everything together by embedding the same databases in different filtered views—such as daily “to-dos not done,” weekly planners, and project overviews—so the user sees only what matters at that moment.

Finally, the session shows how to operationalize planning cycles: weekly views connect to quarterly goals, and templates speed recurring setup (work events, personal blocks, and project scaffolding). The overall message is that Notion becomes powerful once the workspace is built around relationships and views—turning a blank canvas into a system that surfaces the right information on demand.