notion-pages
Create advanced, aesthetic, and efficient Notion pages, templates, and systems. Use this skill whenever the user asks to build, design, create, or set up anything in Notion — including dashboards, roadmaps, Life OS systems, kanban boards, PARA setups, design systems, project trackers, weekly planners, content calendars, second brains, OKR trackers, or any Notion page/template. Also trigger when the user mentions making Notion "look better", "more aesthetic", "more advanced", or asks for Notion formula/database/automation help. If the user says anything like "build me a Notion X", "set up my Notion for Y", or "how do I make Notion do Z", use this skill. Do not skip this skill for Notion-related requests.
Notion Pages & Templates Skill
Build beautiful, efficient, advanced Notion workspaces grounded in research-backed design patterns. This skill covers aesthetics, database architecture, formulas, automations, and the major template archetypes.
CORE PHILOSOPHY
"Less is more" for databases. "Design intentionally" for layout.
Two rules govern everything:
- One master database with filtered views beats many separate databases
- Visual design follows a system (palette, icons, covers) — never ad hoc
1. AESTHETIC FOUNDATIONS
Color & Theme
- Pick 2–4 colors max and use them everywhere: callouts, tag colors, covers, icons
- Popular theme systems:
| Theme | Font | Colors | Vibe |
|---|---|---|---|
| Minimalist | Default | Black / White / Gray | Clean, corporate |
| Dark Mode | Mono | Dark bg + pastel accents | Modern, eye-friendly |
| Vaporwave | Mono | Pink / Purple / Blue / Neon | Creative, bold |
| Nature | Serif | Green / Brown / Gray | Calm, organic |
| Dark Academia | Serif | Brown / Gray / Cream | Classic, artsy |
Covers & Icons
- Covers: Treat like a "hero section". Make in Canva at ~1600px wide using brand colors. Reuse the same style family across sections (content, clients, personal) for visual unity.
- Icons: Every page gets one. Keep all icons the same style — all emojis, all minimal PNGs, or all native Notion icons. Never mix styles. Match the color palette.
- Sources for icons: Icons8, Flaticon, Noun Project, native Notion icon set
Layout Principles
- Multi-column layout makes pages feel like systems, not notes. Typical dashboard layout:
- Left column (narrow): tasks, quick links, priorities
- Center column (wide): main database or content
- Right column (narrow): widget, quote, image
- Callout blocks = visual cards/containers. Change background color, remove emoji for cleaner look, nest other blocks inside. Use for: Today's Focus, Quick Links, Weekly Goals, In Progress notes.
- White space: Group related blocks, add dividers between sections, tuck non-urgent links into Toggle blocks. Never stack 5+ callouts with no breathing room.
- Breathe: Add blank paragraph spaces between text; use
/dividerbetween sections; use Quote blocks as vertical dividers.
Advanced Visual Tricks
- LaTeX dividers: Create a column, paste
$$\color{gray}\rule{3px}{400px}$$in an inline equation block → vertical divider - Custom fonts: Make a heading image in Canva with your brand font → embed as an image block. Looks like real custom fonts.
- Fake text centering: Add spaces to the left of headings until visually centered (Notion has no native center-align)
- Clean up pages: Turn off Backlinks and Top-level discussions via ⋯ → Customize Page
Widgets (Use Strategically — Max 2 per page)
- Indify / WidgetBox: Weather, Pomodoro timer, countdown, clock, quotes, Spotify embed
- Don't add widgets just because you can. Each widget must earn its spot.
2. DATABASE ARCHITECTURE
The Golden Rule: Single Source of Truth
❌ Bad: 12 separate "Events - January", "Events - February" databases
✅ Good: 1 Events database with filtered views per month/quarter/type
One master database:
- Loads faster (fewer blocks for Notion to compute)
- Easy to maintain (change a property once, updates everywhere)
- Scales as you add data
- Powers multiple filtered views as "tabs"
Core Database Views
| View | Best For |
|---|---|
| Board (Kanban) | Agile workflows, status tracking (Backlog → In Progress → Review → Done) |
| Timeline | Roadmaps, project planning, release scheduling |
| Gallery | Resources, content ideas, products, client libraries |
| Calendar | Deadlines, editorial calendars, event scheduling |
| Table | Data entry, detailed property editing |
| List | Simple task views, reading lists |
Gallery tips: Set card preview to "Page Cover", hide extra properties, delete empty default pages → instant Pinterest-style visual grid.
Relations & Rollups
Connect core databases to each other using Relations:
Clients ←→ Projects ←→ Tasks
- Relation: Links records across databases (e.g., each Task belongs to a Project)
- Rollup: Aggregates related data (e.g., count of completed tasks → project progress %)
- Rollups can: Sum values, Count items, Calculate % complete, Find min/max dates
Example: Progress bar formula using a Rollup:
toNumber(prop("Tasks Done")) / toNumber(prop("Total Tasks"))
Auto-Archiving Setup
Create an "Archive" filtered view with an advanced filter:
- Filter:
Start Dateis before1 month ago(relative date) - Main view filter:
Start Dateis after1 month ago
Notion auto-moves items between views as dates pass — zero manual maintenance.
3. FORMULAS 2.0
Key Concepts
// Dot-notation (new in 2.0)
prop("Due Date").dateAdd(7, "days")
// Variables with let
let(score, prop("Impact") * prop("Confidence") / prop("Effort"),
ifs(score > 8, "🔥 High", score > 4, "⚠️ Medium", "⬇️ Low")
)
// Multi-variable with lets
lets(
impact, prop("Impact"),
effort, prop("Effort"),
impact / effort
)
// ifs() — replaces nested if()
ifs(
prop("Score") > 90, "A",
prop("Score") > 75, "B",
prop("Score") > 60, "C",
"F"
)
// List operations (arrays)
prop("Related Tasks").filter(current.prop("Status") == "Done").length()
// Styled output
style("🔴 Overdue", "red", "bold")
Useful Formula Recipes
// Priority Score (for roadmaps)
prop("Impact") * prop("Confidence") / prop("Effort")
// Schedule Risk indicator
ifs(
prop("End Date") < now() and prop("Status") != "Done", "🔴 Late",
dateBetween(prop("End Date"), now(), "days") < 3, "🟡 At Risk",
"🟢 On Track"
)
// Days until due
dateBetween(prop("Due Date"), now(), "days")
// Task completion status (without rollup, using relation)
lets(
tasks, prop("Tasks"),
done, tasks.filter(current.prop("Status") == "Done").length(),
total, tasks.length(),
ifs(total == 0, "No tasks", done == total, "✅ Done",
done > 0, "⚙️ " + format(round(done/total*100)) + "%", "⬜ Not started")
)
4. AUTOMATIONS
Access via the ⚡ lightning bolt icon in any database.
Trigger types
- Property changed (e.g., Status → "Done")
- Page added to database
- Date arrives (e.g., Due Date = Today)
- Button clicked (page-level or database property)
Action types
- Edit property in same or other database
- Add page to database
- Send Slack/email notification
- Send webhook (for Zapier/Make integrations)
- Define variables (reuse across multiple actions)
Key Automation Recipes
WHEN Status → "Done"
→ Set Completed Date = Now()
→ Send Slack notification to #team-updates
WHEN new page added to Inbox
→ Set Status = "To Review"
WHEN Due Date = Today
→ Send email to owner
5. TEMPLATE ARCHETYPES
A. Dashboard (Home Page)
Purpose: Nudge attention toward urgent tasks + portal to workspaces
Layout:
[Cover Image - branded hero banner]
[Icon + Page Title]
[Column 1 - narrow] [Column 2 - wide] [Column 3 - narrow]
Callout: Today's Focus Linked DB: Active Projects Widget: Clock/Pomodoro
Callout: Quick Links Filtered view: This Week Widget: Quote of day
Toggle: Resources ────────────────────── Image: Inspiration
Key elements:
- Linked databases with filters (not raw databases)
- 1-2 widgets max
- Persistent synced block side-menu for navigation across all pages
B. Roadmap
Purpose: Visualize product/project progress over time
Database properties:
- Name (title)
- Status (select: Backlog / In Progress / Review / Done / Shipped)
- Priority (formula: Impact × Confidence ÷ Effort)
- Phase/Epic (relation → Epics database)
- Owner (person)
- Start Date / End Date (date range)
- Schedule Risk (formula — see above)
- RACI (multi-select: Responsible / Accountable / Consulted / Informed)
Views to create:
- Timeline (grouped by Epic) — drag to adjust dates
- Board (grouped by Status) — kanban flow
- Table (full edit mode)
- Calendar (deadlines)
- Filtered: "My Tasks", "This Sprint", "Shipped"
C. Kanban Board
Purpose: Agile workflow management
Columns (Status options):
Backlog → Ready → In Progress → Review → Done
WIP limit formula (add as database description or callout):
Max 3 items In Progress per person at any time
Scrum variant: Add a Sprints relation database + sprint goals + burndown chart (via Blocky widget)
Kanban variant: Set WIP limits per column, track cycle time with date formula:
dateBetween(prop("Done Date"), prop("Start Date"), "days")
D. Life OS (PARA Method)
Purpose: All-in-one personal productivity system
Four core databases:
- Projects — short-term efforts with a goal + deadline
- Areas — ongoing responsibilities (Health, Finance, Career, Relationships)
- Resources — reference material, interests, notes
- Archives — inactive items moved out of active view
Key pages:
- Home Dashboard: Today's priorities, active projects, quick capture inbox
- Weekly Review: Template page linked to all 4 PARA databases
- Quick Capture Inbox: Dump ideas here → sort into PARA weekly
- Persistent Side Menu (synced block): Navigation present on every page
PARA Tips:
- Areas have standards to maintain (not goals to achieve)
- Resources are shareable; Areas are private
- Archive aggressively — it's not deleting, just moving
E. Design System
Purpose: Single source of truth for brand/product visual identity
6-section structure:
- 🖼 Brand — Logo files, mission statement, value prop, guiding principles
- 🎨 Visual Design — Gallery DB of: typography guidelines, color tokens, grid system, iconography, spacing rules
- 📝 Content — Tone of voice, UX writing guidelines, brand vocabulary
- 🧰 Components — Atomic UI elements (buttons, banners, tables, forms) + embedded Figma prototypes + developer code snippets
- 💼 Resources — Tools, links, onboarding docs
- 📱 Prototypes — High-fidelity mockups (embedded Figma frames)
Components section tip: Use a Kanban-style board view with Status + Tags + Assignee so teams can track component build progress.
F. Content Calendar
Database properties: Title, Type (video/blog/social), Platform, Status, Publish Date, Owner, Related Project (relation)
Views: Calendar (by Publish Date), Board (by Status), Gallery (visual preview), Filtered: "This Week", "My Content"
G. Project Tracker
Links to: Tasks database, Clients database, Team database
Progress formula (requires Rollup "Tasks Done %"):
style(
format(round(prop("Tasks Done %") * 100)) + "% Complete",
ifs(prop("Tasks Done %") > 0.8, "green",
prop("Tasks Done %") > 0.4, "yellow", "red")
)
6. QUICK REFERENCE: BUILDING A NEW PAGE
Step-by-step checklist:
- Choose cover image (Canva 1600px, brand colors)
- Set page icon (match style to rest of workspace)
- Turn off Backlinks + Top-level discussions (⋯ → Customize Page)
- Set full-width layout (⋯ → Full width ON)
- Define color palette (2–4 colors, note them in a callout at top)
- Build structure with columns (3 columns for dashboard layout)
- Add callout blocks as visual containers
- Use dividers + toggles to organize depth
- Place only 1–2 widgets max
- Connect databases with Relations before adding Rollups
- Set up filtered views before embedding on dashboard
- Add automations for repetitive status changes
7. NOTION MCP INTEGRATION (Creating Pages via API)
When using the Notion MCP to create pages programmatically:
Tool: notion-create-pages
- Always set a page icon (emoji or external URL)
- Set cover via external image URL
- Use rich_text arrays for formatted content
- Build databases with proper property schemas before adding pages
- Use relation properties to link databases at creation time
Property type reference:
title— page namerich_text— formatted text contentselect/multi_select— fixed option listsstatus— built-in status with Done groupdate— single date or date rangeperson— workspace member assignmentrelation— link to another databaserollup— aggregate from related databaseformula— computed propertynumber— numeric valuecheckbox— boolean toggleurl/email/phone_number— contact/link fieldsfiles & media— attachmentscreated_time/last_edited_time— auto-filled timestamps
SOURCES
Research grounded in 50 web sources covering:
- Aesthetic Notion setup guides (Gridfiti, Studio Brittany, Simple.ink)
- Official Notion templates (Marketplace: roadmap, design system, PARA, Life OS)
- Formulas 2.0 documentation (Notion Help, Noxen Studio, Notion Mastery)
- PARA Method (Forte Labs, Tiago Forte's Building a Second Brain)
- Project management patterns (Kanban, Scrum, OKR, Agile in Notion)
- Relations & Rollups deep-dives (Notion VIP)
- Automation guides (Zapier, Make, native Notion automations)