Pages

A page is a document-like space for notes and structured knowledge.

A page can contain content and also act as a parent for other pages. You can write explanations, lists, tables, links, and references inside a page. Pages are meant to hold meaningful context, not just isolated question-and-answer pairs.

Yuhimo is page-first, not flashcard-first. The page is the main unit you browse, edit, organize, and optionally review.

Every page has a title. Clear titles make the page tree, search, and review easier to use.

If you create or save a page without a title, Yuhimo may save it as Untitled. You can rename it anytime.

Workspace search matches your query against page titles and content. It is not AI semantic search.

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

More detail on search and the page tree is in Nested Pages.

Every learning page starts as a regular page.

Turning on learning adds scheduling behavior to that page. The content itself remains a page. When the page becomes due, it can appear in review sessions.

Learning can be enabled only for pages you want to review. Not every page should become a learning page.

Some pages are better kept as reference notes. Enable learning for content you want to actively remember.

See How learning pages work for more detail.

Questions are optional prompts attached to a page. They help you test recall, but they are not separate flashcards in Yuhimo's core model.

A page can be reviewed even if it has no questions. Questions do not replace the page content.

AI-generated questions are helpers only. You still review the page and rate your own recall.

A page called "React rendering basics" may contain explanations, examples, and links. It can also have questions like "What triggers a React re-render?" or "Why can unnecessary renders hurt performance?"

These questions help recall the page, but the page remains the main learning unit.

Pages can be organized hierarchically. A parent page can contain child pages, which helps split large topics into smaller parts.

A parent page can work as both a normal note and a container. Child pages hold specific subtopics under that branch.

Yuhimo prevents moves that would break the page tree, such as moving a page into itself or into one of its own children. See Nested Pages for hierarchy, moves, trash subtrees, and scoped learning.

Example structure:

• JavaScript
• Closures
• Promises
• Event loop
• Modules

This structure helps you browse and organize knowledge. It also makes scoped learning sessions useful when you want to review a specific branch.

Useful page content includes:

• concise explanations
• examples
• important facts
• tables
• checklists
• links to sources
• personal notes
• questions if useful

Write pages so they remain understandable later, without relying only on the original source.

Yuhimo does not store files, images, or videos directly inside pages. Use links to external resources instead.

A page can reference external material through links, but you should also write the key takeaway inside the page.

This helps reviews remain useful even if the external source is unavailable later.

Create a new page when:

• the topic is large enough to stand alone
• the current page is becoming too long
• a subtopic needs its own learning schedule
• you want to review it separately
• the content belongs to a different branch of the page tree

Do not create too many tiny pages if they lose context. Split when structure, clarity, or review scheduling improves.

Learning is optional. It may not be useful for:

• temporary notes
• project drafts
• copied references
• content you only need to find, not remember
• pages that are still incomplete or messy

Keep these as normal pages until the content is worth remembering long-term.

Deleting a page moves it to trash first. It is not removed forever immediately. If the page has children, the whole subtree goes to trash with it.

Trashed pages can be restored within 10 days or permanently deleted from trash when you are sure. Trashed pages do not behave like normal active pages.

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

How learning pages work — what changes when learning is enabled.

Questions — optional prompts attached to a page.

Turn on learning — enable review scheduling for a page.

Nested Pages — parent/child structure and moving pages.

Scoped learning sessions — review a specific branch or topic.

Trash and restore — deleting a parent moves its subtree to trash.

Other common issues — search and page-tree troubleshooting.

Is every page a learning page?

No. A page is a normal note by default. It becomes a learning page only when learning is enabled.

Do pages need questions?

No. Questions are optional prompts. They can help recall, but the page itself is the main unit.

Can I use Yuhimo only for notes?

Yes. Pages can be used as normal notes without enabling learning.

Should I split every topic into many pages?

No. Split only when it improves structure, clarity, or review scheduling. Too many tiny pages can remove useful context.

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

Yes, if learning is enabled for each of them. Each page should represent something useful to review on its own.

Should I paste full external resources into a page?

Usually no. Store the key summary, notes, and links. Avoid turning pages into unprocessed dumps of content.

Why is my page titled Untitled?

Yuhimo saves pages without a title as Untitled. Add a clear title when you are ready.

What happens if I delete a page with children?

The parent and its whole subtree move to trash together. See Trash and restore.