🗃️ Lesson 3.1: Your First Database — What a Database Really Is

The Big Idea: A Collection of Pages

Back in Lesson 1.1 we said databases are the idea that lifts Notion above every ordinary notes app. Here is the whole secret, in one sentence:

A Notion database is a collection of pages that all share the same properties.

That's it. No servers, no SQL, no scary jargon. If you can picture a stack of index cards where every card has the same labeled fields — Title, Status, Due Date — you already understand a Notion database. Each card is a page. The labels are properties. The stack is the database.

The magic is that because every item is structured the same way, Notion can show that one collection in many different shapes — a spreadsheet-like table, a kanban board, a calendar, a gallery of cards — and filter, sort, and connect them. You store the information once and look at it however the moment needs.

Every Row Is a Page (Not a Cell)

This is the single most important thing to understand in this entire module, and it's the thing a spreadsheet can never do. In a spreadsheet, a row is just a line of cells. In Notion, every row is a full, openable page — with its own body where you can write paragraphs, add checklists, embed images, or nest more content.

So a row in your Reading List isn't just "Dune — Sci-fi — Reading." Open that row and you get a whole page about Dune, where you can jot your favorite quotes, a review, links, and notes — all while the row still shows its tidy properties in the table. The properties are the summary; the page is the depth.

Inline vs. Full-Page Databases

When you create a database, Notion asks — implicitly, by which command you use — whether you want it to live inside another page or to be its own page. Both hold identical data; the only difference is where the database sits.

📥 Inline database

An inline database is embedded in a page alongside other blocks. You can have text above it, three databases stacked on one dashboard, a heading and a table and a callout all together. Inline is perfect when the database is part of a bigger page — like a "Projects" dashboard that shows a task table plus some notes.

🗂️ Full-page database

A full-page database is the page. It takes over the whole canvas and shows up in your sidebar as its own item, with no room for other blocks around it. Full-page is best when the database is a major thing in its own right — your master Tasks database, your whole Reading List.

Creating Your First Database

Everything in Notion starts with the slash command, and databases are no exception. Put your cursor on an empty line and type / to open the block menu, then pick the kind of database you want.

Here are the commands worth memorizing:

• /table — the classic spreadsheet-style view; the most common way to start.
• /database — creates a database and lets you pick its first view.
• /board, /calendar, /gallery, /list, /timeline — start the database directly in that view. (We cover every view in Lesson 3.3.)

When you pick one, Notion offers to create a new empty database or to show data from an existing one (that's a "linked view" — more in Lesson 3.3). For now, choose New database. You'll get a small table with a couple of starter columns and empty rows, ready to fill.

👁️ The "table" is just one view

Here's a mindset shift that pays off all module: what you see is not "the database" — it's one view of it. The data lives underneath, invisible. A table view arranges it into rows and columns; a board view would arrange the exact same rows as cards. Changing the view never changes the data. This is why the same Reading List can be a checklist today and a visual shelf of covers tomorrow.

Notice the Aa icon on the Title column — that's Notion marking the mandatory title property. The colored pills are select and status properties, which you'll add in Lesson 3.2.

Opening a Row as a Page

Remember: every row is a page. To prove it, hover over any row and an OPEN button appears at the left edge of the title cell. Click it (or click the row's title) and the page opens. Notion gives you three ways to open a row, and you'll use all three:

You can set your preferred default with the ⋯ menu at the top of the page, and switch on the fly from the icons at the top of the peek. Once open, a row page has two zones: its properties across the top (the values you'd see in the table) and its body below — a completely normal page where every block and skill from Module 2 works.

⚠️ Important: Adding blocks inside a row's page does not create a new database column. The body is free-form page content; the properties are the structured data. Keep the two straight: quick facts you'll filter or sort → properties; longer freeform notes → the page body.

Database vs. Page vs. Subpages — a Clear Rule

The most common beginner question in all of Notion is: "should this be a database, a plain page, or a few subpages?" Here is a rule you can actually use.

Ask yourself two questions:

1. Are these items alike? Books, tasks, contacts, recipes, expenses — many of the same kind. → Leaning database.
2. Will I ever want to sort, filter, or see them another way? "Show only unread," "sort by due date," "see this month on a calendar." → Definitely a database.

🎯 Project: Your Reading List Database

Time to build the real thing. This Reading List becomes your database sandbox for the whole module — in Lesson 3.2 you'll add proper properties, and in Lesson 3.3 you'll view it as a board, calendar, and gallery. (Prefer tasks to books? Build a "Tasks" database instead with the same steps — either works beautifully.)

Reading List

- Dune
- Atomic Habits
- The Hobbit
- Educated
- Project Hail Mary

Best Practices for Your First Database

✅ Do's

• Start small. One database, a few rows. You can always add properties and views later.
• Write meaningful titles. The title shows in every view — make it the label you'd want on an index card.
• Use the row's page body for long notes, and properties for facts you'll sort or filter.

❌ Don'ts

• Don't confuse a simple Table block with a database. If you want views and filters, create a Table view database.
• Don't make everything a database. One document is a page; a collection is a database.
• Don't stuff notes into the title. That's what the page body is for.

📓 Learning Journal

📝 Lesson Summary

🎉 What You've Accomplished

You built your first real database and — more importantly — you understand what it is. That "every row is a page" insight is the mental model most Notion users never quite articulate, and it's the foundation for every dashboard, tracker, and wiki you'll ever build. From here, databases only get more powerful, and you'll always know what's happening underneath.

❓ Common Questions at This Stage

🔭 Looking Ahead

Your Reading List has titles but not much structure yet. Next up, Lesson 3.2: Properties — The Many Column Types, where you'll meet every property type — status, date, select, number, checkbox, and more — and learn which to reach for when. That's where your database gains real intelligence.

✅ Before the Next Lesson

• Keep your Reading List (or Tasks) database — you'll enrich it next lesson
• Open at least one row as a page and notice the properties vs. body split
• Write your Learning Journal entry for this lesson

📚 Additional Resources

• Notion Help — Intro to databases
• Notion Help — Create a database
• r/Notion — see how others structure their databases