Markdown in Mikipage

Notes are written in Markdown — the same lightweight formatting syntax used by GitHub, Reddit, and most note-taking tools. You never have to learn it: the toolbar above the editor inserts every piece of syntax on this page for you, and the plain editor (Editor → "Use plain editor (no markdown)") skips formatting altogether.

This page is the full reference for what Mikipage understands.

🧩 marks a Mikipage extension — syntax that works here but is not part of standard Markdown, so it will not render the same way if you paste the note into another tool. Everything unmarked is ordinary Markdown and travels anywhere.

Text↑

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

bold, italic, ~~strikethrough~~, code.

Toolbar: B and I have their own buttons; strikethrough is under Tools.

Headings↑

# Heading 1
## Heading 2
### Heading 3
#### Heading 4

Headings are how a long note becomes skimmable, and they are what the table of contents is built from. Toolbar: Style.

Lists↑

- bulleted item
- another one
  - indented one level

1. numbered item
2. the numbers renumber themselves when rendered

- [ ] something to do
- [x] something done

Press Enter at the end of a list item and the next item starts itself; press it again on an empty item to end the list. Tab and Shift+Tab indent and outdent. Toolbar: List.

Quotes↑

> A quoted passage.
> It can run over several lines.

Toolbar: Style → Quote.

Links and images↑

[link text](https://example.com)

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

To link a picture you already have, don't write this by hand — use Insert → Insert picture, which uploads the file and writes the reference for you (see Attachments, below).

Horizontal line↑

---

Keep a blank line above it. Written directly under a line of text, --- means something else in Markdown: it turns that line into a heading.

Tables↑

| Ingredient | Amount |
| --- | --- |
| Flour | 500g |
| Water | 350g |

The columns do not have to line up in the source — only the | --- | separator row matters. Toolbar: Insert → Table.

Code↑

Put three backticks on their own line above and below:

```
git commit -m "message"
```

Naming the language after the opening backticks (```python) is allowed and travels fine.

One difference from standard Markdown 🧩: indenting a line by four spaces does not make it code here. In a notes app that rule fires by accident far more often than on purpose — a pasted paragraph or a hanging indent would silently turn into a grey box. Fenced code is the one deliberate way to write code.

Mikipage extensions↑

Everything below is ours. It is what makes a note more than a text file, and none of it is standard Markdown.

🧩 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 — what shows in the notes list, in search results, and in every link to the note.

# Sourdough starter, week 3

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

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

🧩 Hashtags become tags↑

Write a hashtag anywhere in the body and it becomes a real tag on the note — filterable in search, and clickable to see everything else carrying it.

Finished the quarterly report. #work #q3

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: #Work and #work are the same tag.
Web addresses 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.

🧩 Math↑

LaTeX between dollar signs. One pair for a formula inside a sentence:

The relation $E = mc^2$ still surprises me.

For a formula on its own, centered, put $$ on a line by itself above and below:

$$
\int_0^\infty e^{-x}\,dx = 1
$$

Toolbar: Insert → Math block and Insert → Inline math. This is the same syntax Obsidian uses, so notes move between the two without edits.

Two things to know:

Keep $$ on its own line for a centered formula. Written inline as $$x$$ it renders in the middle of the sentence instead.
Prices are safe. "It cost $5 and $10" stays text, because a formula can't begin or end next to a space and can't be followed by a digit. If a stray $ ever does turn into a formula, write \$ to force it back.

🧩 Preformatted block↑

A fenced block marked plain renders as literal, monospaced text — nothing inside it is interpreted as Markdown, and long lines wrap instead of scrolling sideways.

```plain
Dear Sir/Madam,

  Item          Qty
  ------------  ---
  Widget          4
```

Use it for anything that must survive exactly as typed but isn't code: pasted output, an address block, ASCII art, a fragment of Markdown you want to show rather than apply. Toolbar: Insert → Preformatted block.

🧩 Timeline↑

A fenced block marked timeline renders as a vertical timeline. One event per line, three fields separated by pipes:

```timeline
2026-01-15 | Kickoff | Agreed the scope and the budget.
2026-03-02 | First draft | Sent to review; two chapters still missing.
2026-05-20 | Shipped | Public launch, 1,200 signups in week one.
```

A line without both a date and a title is skipped. The description accepts Markdown. Toolbar: Insert → Timeline.

🧩 Table of contents↑

Put this marker on a line by itself and it is replaced by a linked list of the note's headings:

```table-of-content
PLACEHOLDER


Toolbar: **Insert → Table of contents**.

### 🧩 References to other notes and pages

You can link one note to another inline:

[1]


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. You may 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. A page is referenced the same way, with
`[[miki:<id>]]`.

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.

### 🧩 Attachments live in the text

When you attach a file or insert a picture, a reference 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. Images render inline; anything else renders as a download link.

Write these with **Insert → Insert picture** / **Insert → Attach file** rather than by hand:
the id doesn't exist until the file is uploaded.

### 🧩 Navigation

A fenced block marked `navigation` renders a nested list of note references as a navigation menu
rather than as prose. AI writes one into a page's sidebar, but it is plain Markdown inside, and
you can write one yourself in any note:

~~~
```navigation
- Getting started
  - [[note:0d5c8f2a-6b1e-4a77-9c3d-1e2f8a4b6c90]]
- Reference
  - [[note:7b1e4a77-9c3d-4a77-8f2a-1e2f8a4b6c90]]


A list item with no reference in it is a section heading.

---

## A note on HTML

Standard Markdown lets you drop raw HTML into a document. Mikipage allows a small, safe subset
— basic text and layout tags — and strips everything else, including scripts, styles, and
anything that could load from another site. If a tag you wrote disappears when the note
renders, that's why: use the Markdown equivalent instead.

## Learn more

- [Markdown](https://en.wikipedia.org/wiki/Markdown) on Wikipedia — where it came from and who
  else uses it.
- [Getting started with Markdown](https://www.markdownguide.org/getting-started/) — a good
  ten-minute read covering the standard syntax in more depth.
- [[note:c209edf5-efc8-4051-a122-c06b76fc17c9]] — writing notes in Mikipage: editors, attachments, limits, and what AI can read.