Nested Pages

A nested page is a page placed under another page.

The top page is usually called the parent page. Pages under it are child pages. Child pages can also have their own child pages, which creates a page tree.

Example structure:

• JavaScript
• Closures
• Promises
• Event loop
• Modules

"JavaScript" can be the overview page, while each child page explains one specific topic.

Nested pages help when a topic grows beyond a single page.

• keeps large topics manageable
• makes notes easier to browse
• separates broad concepts from details
• helps avoid one huge page with unrelated sections
• makes review scope easier to reason about
• helps you return to old notes faster

Nesting is not about making the workspace look complex. It should make information easier to understand.

A parent page usually works well as a topic overview and as a container for child pages.

It can contain its own notes, a summary, links to child pages, embedded child-page references, and key ideas. It does not need to contain every detail.

It can be a normal reference page or a learning page if you want to review the overview.

A parent page called "React" may include:

• what React is
• core mental model
• links to child pages
• a short checklist of important concepts

A child page should usually focus on one subtopic.

It can have its own notes, examples, links, and optional questions. It can be turned into a learning page independently. It should make sense when opened on its own.

Under "React", child pages may include:

• Components
• Props
• State
• Effects
• Rendering

Nesting and learning are separate concepts.

A child page does not become a learning page just because its parent is a learning page. A parent page does not become a learning page just because one child page is a learning page.

Learning should be enabled only for pages you want to actively remember. Each learning page has its own review behavior and due date.

Nested structure also makes scoped learning sessions useful. You can start a session from a page branch and review the learning pages inside that scope.

Questions belong to the page they are attached to.

A parent page can have overview questions. A child page can have specific questions. Questions do not replace the page hierarchy.

Questions are optional prompts, not separate required flashcards. See Questions for more detail.

Parent page "JavaScript" may ask: "What are the main areas of JavaScript you need to understand?"

Child page "Event loop" may ask: "What is the difference between the call stack and the task queue?"

Create a child page when:

• a section becomes too large
• the subtopic needs its own examples
• the subtopic should be reviewed separately
• the subtopic belongs under a broader concept
• the current page is becoming hard to scan
• the topic has enough value to stand alone

You can reorganize pages by dragging them in the page tree or moving them under another parent.

Yuhimo keeps the tree valid. A page cannot be moved into itself. A page cannot be moved into one of its own descendants, because that would create a cycle.

When a page moves, Yuhimo updates parent/child relationships and keeps embedded child-page references in parent content aligned with the tree where possible.

When a page is moved to trash, embedded references to that page are usually removed from parent content so you are not left with broken embeds. See Trash and restore.

If a move is blocked, you are usually trying to place a page inside itself or inside its own subtree. See Other common issues.

Avoid nesting when:

• the content is only a few lines
• the child page would lose necessary context
• the structure becomes harder to browse than one page
• you are creating hierarchy just for organization theater
• the topic is temporary or not important enough

Too little structure creates messy pages. Too much structure creates fragmented knowledge.

Example 1:

• Frontend fundamentals
• HTML
• CSS
• JavaScript
• Browser rendering

Example 2:

• Biology
• Cell structure
• DNA
• Protein synthesis
• Evolution

Example 3:

• Work project
• Product requirements
• UI decisions
• Technical notes
• Meeting notes

Different use cases can have different nesting depth. Choose the structure that keeps each page useful on its own.

• turning every paragraph into a separate page
• putting unrelated topics under the same parent
• enabling learning on every page automatically
• creating child pages that cannot be understood without the parent
• using nested pages instead of writing a clear summary
• relying only on links without writing key takeaways

Pages — the core unit for notes and structure.

How learning pages work — when a page enters the review system.

Questions — optional prompts attached to a page.

Scoped learning sessions — review a specific branch or topic.

Turn on learning — enable review scheduling for a page.

Trash and restore — subtree delete and restore.

Other common issues — moves and search troubleshooting.

Deleting a parent page moves the whole subtree to trash. You do not need to delete each child separately.

Restoring a parent restores the subtree when possible and keeps hierarchy valid. If the original parent location is unavailable, Yuhimo places restored pages in a safe valid location.

Subtree structure also matters for scoped learning sessions: a session started from a branch reviews learning pages inside that scope, not your whole workspace.

See Trash and restore for retention, restore, and permanent delete.

Scoped learning sessions — focused review inside a branch.

Yuhimo search helps you jump to pages by matching your query against page titles and content. It is workspace search, not AI semantic search.

Search works best with specific terms from the page title or content. Very common words (such as “the” or “and”) are usually ignored. Meaningful search terms are generally at least three characters long.

If search misses a page, check the title, whether the page is in trash, and whether your query is specific enough. See Other common issues.

Are child pages normal pages?

Yes. A child page is still a regular Yuhimo page. It can contain notes, links, tables, questions, and optionally have learning enabled.

Does a child page automatically become a learning page?

No. Learning must be enabled for the page itself.

Can a parent page and child page both be learning pages?

Yes, if learning is enabled on both. They should represent different review targets: the parent as an overview, the child as a specific topic.

Should I create a child page for every small idea?

No. Create child pages when they improve clarity, structure, or review behavior. Very small ideas often work better inside an existing page.

Do questions belong to the parent page or child page?

Questions belong to the page where they are created. Overview questions usually fit parent pages. Specific questions usually fit child pages.

Can nested pages help with focused review sessions?

Yes. Scoped learning sessions let you review learning pages inside a selected page branch, which makes nested structure useful for focused study.

Why can’t I move a page under one of its children?

That would create a cycle in the page tree. Yuhimo blocks moves into yourself or your own descendants.

Does deleting a parent delete only that page?

No. The whole subtree moves to trash with the parent.