How to organise notes with nested pages

To organise notes with nested pages, give each top-level page one clear job, keep most notes within three levels, and name every page so it makes sense when you see it in search results. Put a short index at the top of busy parent pages. When you find yourself creating many similar pages with the same details, switch to a database instead.

Why nested pages work

Pages inside pages mirror how people think about their lives. Work contains clients. A client contains projects. A project contains meeting notes. Nesting lets you follow that path without a separate folder system.

The risk is that nesting has no natural limit. Without a few rules, you end up seven levels deep, unsure where anything lives.

Rule 1: Keep the top level short

Your top-level pages are the front door. Keep between four and seven. A common set:

• Inbox for anything new and unsorted.
• Work or Projects for things with a finish line.
• Personal or Areas for ongoing parts of life.
• Reference for things you look up but rarely change.
• Archive for finished work.

If you have more than seven, some of them probably belong inside another.

Rule 2: Three levels for most notes

A good default is three levels: top-level page, topic, note. For example, Work, then Bakery client, then "2026-10-14 Kick-off call".

Go to a fourth level only when a topic has grown big enough to need its own sections. Most notes never need it. If you have to click through five pages to reach a note, the structure is too deep.

Rule 3: Name pages for search, not for the parent

Names like "Notes", "Ideas" or "Meeting" make sense inside their parent page. In search results they are useless, because you will have twenty of them.

Write names that stand on their own:

• Meetings: start with the date in year-month-day order, then the topic. "2026-10-14 Bakery kick-off call". Written this way, dates line up in the right order in any alphabetical list.
• Topics: use the plain name. "Bakery client", "Kitchen renovation", "Spanish course".
• Reference: describe what is inside. "Boiler service checklist", "Tax return documents list".

Avoid "Misc" and "Other". They become the place where notes go to be forgotten.

Rule 4: One home for every note

Each note should live in exactly one place. If a note feels like it belongs in two places, pick the one where you would look first. Search will cover the other case.

Rule 5: Add a short index to busy parent pages

When a page has more than about ten sub-pages, add a few lines at the top explaining what is inside and which sub-pages matter most. A heading and a short list is enough. It saves you scanning a long list every time.

Rule 6: Think about sharing when you nest

If your app shares a page together with its sub-pages, structure affects what other people can see. Keep anything you plan to share in its own branch, and keep private notes out of it. Before sharing a page, check what sits underneath it.

When to use a database instead of pages

Pages are best for writing. A database is better when you have many items of the same kind, each with the same few details.

Switch to a database when:

• you have more than ten or so sibling pages of the same type, such as books, clients or projects,
• you keep writing the same details at the top of each page, such as status, date or rating,
• you want to see items side by side in a table, or as cards on a board.

For example, a "Reading list" with one page per book works at first. Once you have thirty books, a database with Title, Author (text), Status (select), Finished (date) and Link (url) is much easier to scan.

A worked example

Leo had 140 notes spread across nine top-level pages, including "Misc", "Stuff" and "Notes 2". Here is how he reorganised in one evening.

1. He created five top-level pages: Inbox, Work, Personal, Reference and Archive.
2. He moved each old page under one of the five. "Misc" went into the Inbox to sort later.
3. He renamed 30 meeting notes to the date-first format.
4. He replaced 25 book pages with one Reading list database.
5. He moved the empty old pages to the trash, knowing he could restore them for 30 days if he had made a mistake.

His deepest note is now four levels down, and most are at three.

Common mistakes

• Vague names. "Notes" tells you nothing in search.
• Duplicating notes. Two copies drift apart. Keep one.
• Using pages for list data. Thirty similar pages should be one database.
• Reorganising every week. Change the structure when it fails you, not for fun.

Where Asendify Notes fits

Asendify Notes lets you nest pages inside pages and add simple databases with table and board views when a list outgrows pages. It has search across everything, a trash you can restore from for 30 days, and read-only share links that cover a page and its sub-pages, which is why Rule 6 matters. The price is £1,450 a year (£1,000 plus a 45% service fee, shown openly), with no free plan or trial.

Key takeaways

• Keep four to seven top-level pages, each with one job.
• Aim for three levels and rarely go beyond four.
• Name pages so they make sense in search, with dates first for meetings.
• Give every note one home.
• Use a database when you have many similar items with the same details.

FAQ

How deep should nested pages go?

Three levels suits most notes: top-level page, topic, note. Use a fourth level only for large topics. Deeper than that, notes become hard to find.

Should I use folders, tags or nested pages?

In a notes app built around pages inside pages, nested pages do the job of folders. Combine them with clear names and search, and you rarely need anything else.

When should I turn pages into a database?

When you have many pages of the same type, such as books or clients, and you keep recording the same details on each. A database lets you see them side by side.

More playbooks on other topics: https://www.asendify.co/books/

More Asendify Notes articles