Writing Notes

A note is whatever you wrote — a thought, a meeting, a recipe, a chapter. Notes are the raw material Mikipage's AI organizes into pages, so the only job here is to capture things. Where they belong is not your problem. See [1] for how notes relate to pages.

The basics

Creating one. Click Write and start typing. There is no Create button: about a second after you pause, the note saves itself and appears in the notes list. A quick type-then-delete never leaves anything behind.

Viewing and editing. An existing note opens in view mode, with formatting rendered. Click Edit — or just double-click the text — to change it. Save with the button or Cmd/Ctrl+S. If your browser closes mid-edit, the draft is recovered when you come back.

Only the owner edits. A note you shared to a group is readable and commentable by members, but they can't change it. A note somebody else shared with you shows a "View only" badge and their avatar.

Other things you can do from the note's action bar: star it (starred notes are filterable in search), share it to one or more groups, add it to related pages, and delete it. Notes you find later through [2].

Choosing an editor

Two editor styles, switchable any time under Account → Preferred Editor:

• Markdown — a formatting toolbar, and your text renders as rich content when you view it. This is what you want if you'd like bold text, headings, links, images, or lists.
• Plain — a clean text box, no toolbar, no rendering. Good if markdown syntax is just noise to you.

The markdown toolbar carries bold, italic, strikethrough, headings, bulleted and numbered lists, links, quotes, tables, horizontal rules, undo/redo, full-screen, attach a file, insert a picture, and AI Polish.

Markdown

Notes are written in Markdown, the same lightweight syntax used by GitHub, Reddit, and most developer tools. The essentials:

**bold**  *italic*  ~~strikethrough~~  `code`

# Heading      ## Smaller heading

- bulleted item        1. numbered item
> a quoted passage

[link text](https://example.com)
![image caption](https://example.com/picture.png)

If that's new to you, the Markdown guide is a good ten-minute read. You don't have to learn any of it — the toolbar inserts the syntax for you, and the plain editor skips it entirely.

Mikipage's additions

Four things work in a Mikipage note that aren't part of standard Markdown.

A heading on the first line becomes the title

If a note's very first line is a level-one heading, that text is the note's title — it's what shows in the notes list, in search results, and in links to the note.

# Sourdough starter, week 3

Fed it at 8am. Doubled in four hours, which is the fastest yet.

Without a first-line heading, the note is identified by a preview of its opening text instead. Nothing breaks; titles are just easier to scan.

Hashtags become real tags

Write a hashtag anywhere in the body and it's recognized as a tag on the note. You can then filter by it in search, or click any tag in the app to see everything carrying it.

Finished the quarterly report. #work

The rules, if you need them:

• Letters, numbers, and underscores, in any language. A tag must contain at least one letter, so #2026 on its own isn't a tag.
• A hashtag can't follow directly after a letter or number, so you#me isn't a tag.
• Tags are lowercased, so #Work and #work are the same tag.
• Web addresses and in-page links are left alone, so a URL ending in #section doesn't create a tag.

You never have to tag anything. AI finds relevant notes on meaning alone; tags are for when you want a hard, exact filter.

References to other notes

You can link one note to another inline:

[[note:0d5c8f2a-6b1e-4a77-9c3d-1e2f8a4b6c90]]

The easiest way to write one is to drag a note out of the notes list and drop it into the editor — the reference is inserted for you. Pasting a full note URL works too, and you can add a label after a second colon ([[note:0d5c…:Q3 planning]]) purely to keep the raw text readable; the label is ignored when the note is displayed.

These same references are what the citations on a generated page are made of. When AI writes a page, every claim carries one pointing back to the note it came from, which is how you can always check a page against its sources.

Attachments live in the text

When you attach a file or insert a picture, a reference like [[file:abc123]] is placed in the note body. The body is the single source of truth for what's attached — so removing the reference and saving deletes the underlying file (after asking you first), and moving the reference moves where the file appears.

Notes vs. attachments

Worth understanding, because it affects what AI can do:

	Note text	Attachment
Size limit	32KB	10MB
Found by search	Yes	No
Readable by AI	Yes	No — AI cannot see inside the file
Good for	Anything you wrote	PDFs, images, spreadsheets, scans

Because AI can't read inside an attached file, describe it in the note. A note saying "scan of the 2026 insurance policy — $2,400/yr, renews in March, covers flood" with the PDF attached is useful to every page you'll ever build. The same PDF attached to an empty note is invisible.

The 32KB limit

A note holds about 32,000 characters — roughly 5,000 words. This is on purpose:

• Long notes summarize badly. A page built from ten focused notes is better than one built from a single sprawling document.
• Long notes read badly, and they're miserable to edit.
• 32KB is more than enough to get an idea across.

If you have something longer, two good options:

1. Attach the full thing and write a summary as the note itself. You keep the document; AI gets something it can actually use.
2. Split it into several notes. AI will connect them again when it builds a page — that is precisely what pages are for.

Next: [4] for turning these notes into something organized.