Roam Tour with Historian Mark Robertson Pt. 1: Daily Notes, Structured Roam, Course Organization

A historian built a Roam Research setup that turns daily capture, teaching planning, and long-form writing into one connected workflow—using transclusion, queries, and block references to reduce clutter and prevent repeated edits across multiple course pages. The core shift is less about “backlinking” and more about reusing the same source blocks everywhere, so a single wording change can propagate without hunting through dozens of copies—an approach that matters when one confusing sentence can derail a whole class.

The workflow starts with a mobile-first “daily notes” page driven by an iOS shortcut. That daily hub pulls in structured inputs automatically: a journal area with an “evening reflection” query that surfaces the prior day’s entry, a randomly selected camera-roll memory for reflective prompts, weather attributes, a sleep log, and calendar data. It also includes a daily inbox for fleeting thoughts and an action list for tasks. Instead of trying to make every task show up in every query, tasks are managed with tags that control what appears by default—especially for subtasks. Subtasks are excluded from the main task query so the daily view stays readable; they only appear when expanded via transclusion, letting projects retain context without flooding the interface.

That design choice feeds into a broader tension: Roam’s “non-hierarchical” network of notes still needs hierarchy in real working life. The setup therefore imposes structure where it counts—particularly for teaching and curriculum. For courses, the system uses a Kanban-style project view for status (on deck, ongoing, done) and a course “modules” structure that must repeat each semester. Rather than migrating old content, the historian recreates course modules from a curated collection of reusable blocks. Those reusable blocks are maintained as templates using block references, so updates happen once and then flow outward.

Teaching organization is handled through course-specific pages that link to shared assignment directions and learning-management-system (LMS) materials. The course pages also track which foundational questions are being “remixed” depending on course length (e.g., a 15-week version versus a 7-week version). Visual cues—like colored dots or unicode icons—help distinguish references to content that lives elsewhere, while keeping the course map navigable without constantly checking the LMS.

Finally, the writing system adds lightweight self-interaction without turning prose into an outline. In an article workspace, the historian uses an inbox query for project capture and then annotates drafts inline with markers (pushpins) that function like argumentative or stylistic notes. A key benefit is rapid review of past writing introductions: clicking into an “introduction” section surfaces prior intros so the writer can compare style and context. The result is a Roam environment that treats daily life, teaching logistics, and drafting as one connected system—designed to stay fast, minimize clutter, and make updates reliable through transclusion rather than copy-and-paste repetition.