Notion for Productivity: Dynamic Navigation Bars & Show Empty Cells
Based on Red Gregory's video on YouTube. If you like this content, support the original creators by watching, liking and subscribing to their content.
Separate backend databases from front-end procedural pages using callouts so the interface stays readable.
Briefing
A Notion workflow can be made dramatically easier to navigate by combining synced blocks, linked databases, and a “missing info” system that automatically flags empty, high-priority fields. The core setup starts with splitting a complex database into two layers: backend data stores and front-end procedural pages. From there, a left-side navigation bar is built once and reused across multiple steps, so moving through a multi-stage process feels consistent even as the underlying database views change.
The tutorial’s example uses a family-research database (“who’s who”) with many properties. To keep the interface manageable, the creator adds callouts that separate “links” (backend databases) from “procedures” (step-by-step pages). Each procedure step gets a structured layout: a header callout for the step name, a nested callout describing what to do, another nested callout listing what to avoid, and an “important links” area that can contain bookmarks. The key move is creating a linked database view inside each step page. Linked databases let filters, sorts, and views affect only the linked view—new entries still write back to the original database—so each step can show only the properties relevant to that stage (identification, dates, places, and so on).
Navigation is handled with a synced block. A synced block containing the navigation bar is created, placed alongside a linked database view, and then duplicated across steps so recurring elements (like the step header and the database link) stay aligned. Filters can be applied per step—for example, showing only entries created “today” using a created timestamp filter—so the workflow doesn’t drown in older rows. To make the navigation reflect where the user currently is, the synced block is unsynced and then re-synced selectively: each step’s navigation item can be colored differently (e.g., red) to indicate the active page.
The second major feature is an automated “empty cells” tracker. A board view groups entries by a select property called bookmark (e.g., “save for later” vs. “important”). Then a formula property called cells to fill is built to detect empty fields in key properties such as summary, place of birth, date of birth, and sources. For each empty field, the formula outputs a pencil/exclamation message and line breaks; a checkbox property (“missing info”) is converted into a formula that checks whether cells to fill is not empty. Finally, a dedicated table view (“all missing info”) filters to show only rows where cells to fill has content and where bookmark status is relevant. This yields a practical dashboard: entries with missing critical information surface automatically, without manual auditing.
Together, synced navigation plus formula-driven missing-field detection turns a sprawling database into a guided, step-based workflow that’s easier for individuals and teams to follow and maintain over time—especially when working through large templates and repeated processes.
Cornell Notes
The workflow uses synced blocks and linked databases to create a reusable, step-by-step navigation system in Notion. Each procedure page contains a linked database view filtered to show only the properties needed for that step, while the navigation bar stays consistent via a synced block. To flag incomplete records, a formula property (“cells to fill”) checks specific high-priority fields (like summary, place of birth, date of birth, and sources) and outputs messages when they’re empty. A checkbox (“missing info”) is then replaced with a formula that turns true when cells to fill is not empty. Board and table views are configured to group by bookmark and to surface only entries needing attention.
How does a linked database help each step show different fields without breaking the original dataset?
What’s the purpose of using a synced block for the navigation bar, and how is the “current step” highlighted?
How can filters prevent a step from showing an overwhelming list of entries?
How does the formula property “cells to fill” detect empty fields and generate actionable messages?
Why convert the “missing info” checkbox into a formula, and how does it work with the “cells to fill” output?
How do board and table views differ in how they display the formula’s line breaks?
Review Questions
- What are the practical differences between using a synced block for navigation versus syncing a callout that contains step content?
- If a record has an empty “sources” field but all other fields are filled, what should “cells to fill” and “missing info” show?
- How would you modify the cells to fill formula to add a new required property (e.g., “place of burial”) to the missing-fields checklist?
Key Points
- 1
Separate backend databases from front-end procedural pages using callouts so the interface stays readable.
- 2
Use linked databases inside each step page so filters and views change per step while new entries still write back to the original database.
- 3
Build a navigation bar once with a synced block, then duplicate it across steps to keep recurring layout elements consistent.
- 4
Apply per-step filters (such as created “today”) to prevent each step from loading an unmanageable list of rows.
- 5
Create a “cells to fill” formula that checks empty high-priority properties and outputs specific, user-facing messages with line breaks.
- 6
Replace manual “missing info” checkboxes with a formula that turns on when cells to fill is not empty.
- 7
Use board views to group by bookmark status and table views (with wrapped cells enabled) to list all records needing attention.