FREE COURSE · BEGINNER
Notion

Build a simple weekly content planner

A private three-post planner with statuses, dates and a filtered view for unfinished work.

About 25 minutes4 practical stepsFree to read
Two people reviewing work together on a laptop.

Before you start

A Notion Free account in your own personal workspace. Use the web or desktop app for the easiest database setup. No Notion AI, paid template or integration is needed.

Stay on the free route

Use a workspace with one owner for this exercise. Team workspaces can have different Free plan block limits. Keep the planner private, skip AI and automations, and use text rather than file uploads.

Original practice lesson · Official references checked 14 October 2026 · Button names may differ between app versions.

Your progress

0 of 4 steps complete.

Start first step ↓
STEP 1 · ABOUT 5 MIN

Choose three useful posts

Build a planner you can use immediately. Three specific ideas make it easier to learn the structure than a blank calendar.

  1. Use the fictional North Street Bike Workshop example below. These are practice ideas, not claims about a real business.
  2. For each idea, decide what a reader should learn and what you need before drafting it.
  3. Open a new private page called “Weekly content practice”. Do not publish it to the web.
Practice example
Post: A quick tyre-check reminder
Purpose: share one useful habit
Needs: a bicycle photo I own

Post: What to bring to a repair appointment
Purpose: answer a common question
Needs: verified information from the business

Post: One lesson from this week
Purpose: share an honest progress update
Needs: my own notes
STEP 2 · ABOUT 8 MIN

Create the planner database

A database stores each post as its own item. Properties let you organise the ideas without moving separate documents around.

  1. On the page, use /database or the new Table option to create an empty database. Choose a database, rather than a simple table block. Skip Build with AI.
  2. Rename the title property to Post. Add a Status property with Not started, In progress and Done, plus a Date property called Target date.
  3. Add the three ideas as rows. Give them dates for your next practice week and leave each status at Not started.
STEP 3 · ABOUT 6 MIN

Develop one idea inside its page

Each database row opens as a page. Keep the brief and the draft inside that item so the planner stays readable.

  1. Open the tyre-check row as a page. Add short headings for Audience, Main message, Draft and Review notes.
  2. Under Draft, write two original sentences and a possible action such as “Save this reminder”. Mark any advice you need to check.
  3. Return to the database and set this item to In progress. Keep the other two at Not started.
Practice example
Audience: people who cycle for everyday trips
Main message: make time for a quick check before setting off
Draft: [write your own two sentences]
Review notes: [facts to verify, image to add, final spelling check]
STEP 4 · ABOUT 6 MIN

Create and test an unfinished view

A useful view answers one question. Here it should show the work that still needs attention.

  1. Add another table view called “To finish”. Filter Status so it is not Done, then sort Target date from earliest to latest.
  2. After reviewing your practice draft, temporarily set that row to Done. Confirm it disappears from To finish but remains in the original unfiltered view.
  3. Change it back to In progress if it still needs work. Reopen the page from the sidebar and check your planner is there. This is a planner, not an automatic publishing system.
TRY IT YOURSELF · ABOUT 5 MIN

A finished post disappears from one view

Your “To finish” view filters out Done items. You mark a post Done and it disappears from that view, but remains in the original unfiltered table.

Original fictional scenario · choose an answer, then read the explanation.

What does this test show?

See a worked example and review checklist

Original view: all three practice posts remain. “To finish”: only posts whose status is not Done. Marking an item Done changes which rows are visible, not whether a post has been published.

  • All practice records remain in the unfiltered view.
  • The filtered view answers a clear question.
  • I do not confuse a planner status with publishing.

Try it with a new example: Change the same item back to In progress. Predict which views will show it, then check.

This checks one practice decision, not your real work. Answers save only in this browser when storage is available.

MAKE THE LESSON YOURS

Keep your practice notes

Record what you made, what you checked and what you want to improve. These notes stay in this browser; they are not sent to us or synced to another device. Clearing browser data removes them.

Optional · up to 2,000 characters.

YOUR NEXT SMALL STEP

Put your practice to work

Repeat the task with a fresh brief. Check the result before using it for a real project.

Choose your next skill →

Part of Make your first content kit.

GO FURTHER WITH THE PROVIDER

Notion: database basics

Official documentation for manual databases, properties and views. Our exercise uses a small personal planner without Notion AI.

Open official learning ↗

Sources and lesson notes

The practical brief and exercises are ours. Official references support the product guidance; we do not host the providers’ course content.

Checked 14 October 2026. Tool plans can change; consult the provider before choosing an upgrade. These beginner exercises have not been presented as certified or exhaustive product testing.

Progress saves in this browser. No site account needed.

THE OTHER FEW

Find the few things worth knowing.

Explore AI tools, software and technology through official sources, clear trade-offs and practical comparisons, so you can find the few that matter to your task.

Popular searches:

🔥 Fresh Few

Recently added to our catalogue, with a reason to explore each one.

💎 Hidden Gems

Editorial alternatives with a specific reason to consider them.

📊 Popular Categories

More from The Other Few
Personal Few

Build the few tools that work together.

Describe the outcome, not the software. The Other Few turns the job into a practical stack, keeps overlaps visible, and explains the trade-offs.

Stack suggestions are task-fit decisions, not product rankings. Commercial relationships must never change compatibility.
READY

Tell us the outcome.

We'll break it into jobs, choose the fewest sensible tools and show the trade-offs.

Evidence-first: current pricing, feature availability and platform support should be shown only when verified from an appropriate source.
THE OTHER FEW · INTELLIGENCE LAYER

From task to decision.

The shortlist now explains the fit, the trade-offs and what to do next.

PERSONALISED FIT
✦

Task understanding

Translate natural-language goals into task signals before matching products.

GoalUse caseConstraints
◎

Compatibility

Show why a tool fits this search instead of presenting a permanent product score.

PlatformExperiencePriority
↗

Decision path

Move naturally from shortlist to profile, alternatives, compare and saved tools.

ExploreCompareSave
DISCOVERY

Go beyond the shortlist.

Browse editorial collections when you want to explore rather than solve one task.

Fresh FewOnly products with a genuine freshness signal.Explore →
Hidden GemsInteresting products that deserve a closer look.Explore →
Popular CategoriesStart with the job, then narrow to the Few.Browse →
VERIFIED SOURCES · EDITORIAL FIT · NO PAID RANKING
RECOMMENDATION GRAPH

See why the Few connect.

The recommendation layer connects tasks, constraints, products, alternatives, workflows and evidence without turning the catalogue into a popularity ranking.

GRAPH ACTIVE
YOUR TASKgoal + constraintsTASKFITTOOLEVIDENCE intentexperienceplatformpriorityproductalternativesourcefreshness
EXAMPLE DECISION PATH
1 · GoalBuild a website for a small business.
2 · ConstraintsBeginner · web · low-code · ease.
3 · Candidate setReplit · Lovable · Claude — narrowed before presentation.
4 · Trade-offLovable favours simplicity; Replit offers more control; Claude is broader rather than purpose-built for the build.
Compatibility is task-specific. It is not a permanent product rating.

Graph signals

These are the relationships the engine can reason over as the catalogue grows.

Goal / intentConstraintTask fitAlternativeWorkflow overlapEvidenceFreshnessSaved context
Important: the graph does not invent evidence. Unsupported claims remain unsupported until verified.
PERSONAL DECISION LAYER

Make the decision smaller.

Bring your goal, saved tools, workflows and fresh changes together. The Other Few narrows the decision without pretending there is one universal winner.
● Decision context ready
Launch a businessBuild a websiteCreate videosResearch & decide
GoalWaiting
ConstraintsWaiting
Your FewLocal saves
ChangesFreshness ready
Start with the outcome.

We'll turn it into a smaller, clearer decision using the intelligence already built into The Other Few.
Fit is contextual. Editorial judgement, evidence and commercial relationships remain separate.Private on this device.
Intelligence Core
Make the catalogue smarter, not just bigger.
The intelligence layer now treats products, tasks, constraints, alternatives and workflows as connected evidence. Expansion is staged into verification lanes rather than filling the catalogue with unverified entries.
18 core records · verification-first
18Core records
7Categories covered
14Relationship types
0Fabricated records

Connected catalogue

Core products are connected to the tasks and categories they are already structured to serve.

Expansion lanes

These are research lanes, not unpublished product claims. A lane becomes catalogue data only after source verification and taxonomy review.
Editorial rule: catalogue breadth never outranks evidence quality. A product can enter the research queue without entering the public Few.
Intelligence Core

One brain. Every decision.

The catalogue, Finder, Decision Engine, workflows, Your Few and freshness signals now have a shared conceptual layer. The goal is not more results — it is better decisions with fewer tools.
● CORE MODEL READY

Decision graph

The same product can play different roles depending on the user's outcome and constraints.
18core products
7active categories
0saved tools
0watched tools
GoalOutcome
IntentTask
ConstraintsFit limits
ProductsCatalogue
DecisionFew