How to build a blog with Notion and Super! (Comprehensive guide and template)
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.
Use two linked Notion databases—essays and categories—connected by a relation property so category pages automatically list the right posts.
Briefing
A Notion blog can be turned into a fully navigable website by pairing a structured Notion template with Super, which renders the Notion pages as a public front end and lets creators restyle everything with themes, page settings, and CSS/HTML. The core move is to keep Notion responsible for content and layout blocks (sidebars, footers, synced elements, database-driven pages) while Super handles the website experience—URLs, navigation, SEO toggles, and visual customization.
The workflow starts with the “blog starter” template inside Notion. It uses two linked databases: one for essays (blog posts) and one for categories. Each essay page includes properties such as a published date, a category relation, a status select (to track whether a post is in draft/published stages), a summary, a featured checkbox, and a cover image, plus the main body content. Categories are separate entries with a title and icon, and each category links back to the essays database through a linked database view that can be filtered—such as showing only essays where the category relation matches “technology” and the status is “published.”
Templates inside those databases act as blueprints for consistent page structure. A category template includes a linked essays view filtered by the category title and published status, while the essay template provides a writing area plus the same sidebar and footer layout. This is reinforced with synced blocks: the sidebar and footer are created as synced blocks so the same design stays consistent across the original template pages and every generated page that copies that synced block. When content is edited in one synced instance, all linked instances update.
Before switching to Super, the Notion side is configured for public access. The front page is shared to the web so that all pages under it become public; if access needs to be restricted later, Super and Notion sharing controls can be adjusted (including turning web sharing off and using restricted access). On the Super side, the copied Notion link becomes a new site, where pages can be edited individually, SEO can be set per page, and password restrictions can be applied.
Super then provides website-level controls: generating pretty URLs via “sync URLs,” selecting themes (including dark/neutral/blackout options), and building a top navigation bar that links to internal pages or external URLs. Creators can customize colors, navbar behavior (like scroll visibility and shadow), and database rendering by enabling visible properties for database collections.
Finally, Super’s code injection enables deeper styling. Global CSS can change site-wide colors using Notion’s style variables (for example, overriding root background/text defaults and highlight colors). Page-specific CSS can refine components like callouts, collection headers, gallery borders, quote block styling, and spacing. Even Notion toggles can be hidden on the website by targeting a specific block ID with a CSS selector pattern (using “#” block IDs and “.notion-toggle-summary” rules). The result is a repeatable system: structured Notion databases generate the content and navigation logic, while Super’s rendering and CSS turn it into a polished website.
Cornell Notes
The template-to-website approach relies on two Notion databases—essays and categories—linked through a relation property, with filters that show only published content. Database templates provide consistent page structure, while synced blocks keep sidebars and footers identical across all generated pages. After sharing the Notion front page to the web, Super imports it as a site, where pages get pretty URLs, per-page SEO controls, and optional password restriction. Super’s theme settings and code injection (CSS/HTML) let creators restyle the site globally and per component, including callouts, collection headers, quote blocks, and even hiding specific Notion toggles by block ID.
How do the essay and category databases work together to drive navigation and filtering?
What’s the practical difference between using a select property vs a relation property for tagging?
Why do synced blocks matter for building a website from Notion?
How does Super turn Notion pages into a real site with URLs and navigation?
What kinds of styling changes can be made using Super’s CSS/HTML code injection?
How can a Notion toggle be hidden from the website without removing it from Notion?
Review Questions
- How do relation properties and database templates combine to ensure only “published” essays appear under each category?
- What role do synced blocks play in keeping a sidebar and footer consistent across all generated pages?
- Which Super features handle pretty URLs, and which features handle visual styling (themes vs CSS injection)?
Key Points
- 1
Use two linked Notion databases—essays and categories—connected by a relation property so category pages automatically list the right posts.
- 2
Rely on database templates inside Notion to standardize page layout for categories and essays, reducing manual formatting work.
- 3
Place shared UI elements like sidebars and footers inside synced blocks so updates propagate across all pages.
- 4
Share the Notion front page to the web before importing into Super, then use Super page-level controls for SEO and optional password restriction.
- 5
Build a top navigation bar in Super by linking to internal pages (generated from Notion) or external URLs.
- 6
Use Super’s theme settings for quick styling, then switch to CSS injection for precise control over callouts, collection headers, quote blocks, spacing, and colors.
- 7
Hide specific Notion toggles on the website by targeting the toggle’s block ID with CSS selectors in Super.