Markdown Formatting

Lithium supports inline markdown-style formatting within blocks. You can use two different formatting styles: markdown (standard) or mrkdwn (Slack-style). Toggle between them in Settings.

Formatting Style

You can choose your preferred formatting syntax in Settings. The main difference is how bold and italic are marked:

Format	Markdown	Mrkdwn
Bold	**bold**	*bold*
Italic	*italic*	_italic_
Strikethrough	~~strike~~	~strike~
Highlight	^^highlight^^	^highlight^

Code, links, and quotes work the same in both styles.

Supported Syntax

Bold

Markdown style: **bold text** → bold text

Mrkdwn style: *bold text* → bold text

Italic

Markdown style: *italic text* → italic text

Mrkdwn style: _italic text_ → italic text

Strikethrough

Markdown style: ~~strikethrough~~ → strikethrough

Mrkdwn style: ~strikethrough~ → strikethrough

Highlight

Markdown style: ^^highlighted text^^ → highlighted text (yellow background)

Mrkdwn style: ^highlighted text^ → highlighted text (yellow background)

Inline Code

Both styles: `code here` → code here

Displays with monospace font and subtle background. Markdown inside inline code is not processed.

Code Block

Both styles: ```code block``` → code block (displayed in pre/code block)

Multi-line code blocks with syntax highlighting. Code blocks take priority over inline code (``` matches before `).

Wiki Links

Both styles: [[Page Name]] → clickable internal link

Links to other pages in your workspace. The link renders with brackets visible and underlined text. Clicking navigates to the linked page.

URLs

Both styles: https://example.com → https://example.com (clickable link with external icon)

HTTP and HTTPS URLs are automatically detected and rendered as clickable links. No markup required.

Quotes

Both styles: Start a line with > to create a quote block:

> This is a quoted line
> Multiple consecutive lines
> are grouped together

Renders with a left border spanning all quoted lines. The > marker is hidden. Consecutive quote lines are consolidated under a single border.

Tags

Both styles: Type # followed by a tag name (no spaces)

Tags like #project or #work are stored separately from block content and displayed as colored pills. Tags support hierarchy with / separators like #project/lithium.

Formatting Rules

• Code blocks have priority over inline code. ```text``` is parsed as a code block, not three backticks with text between.
• Longer delimiters match first. For example, ^^highlight^^ matches before ^highlight^ in markdown style.
• No nesting. You can’t put bold inside italic or vice versa. Adjacent formatting works fine: **bold***italic*.
• Code blocks preserve everything inside. Markdown inside `code` or ```block``` is not processed.
• Tags are detected but stored separately. The #tag syntax triggers tag autocomplete and stores tags as metadata, not inline content.

Examples

Combining formats (markdown style):

Check out [[Project Plan]] for **bold ideas** and *italic notes*.
Use `npm install` or see https://example.com for more.

Same in mrkdwn style:

Check out [[Project Plan]] for *bold ideas* and _italic notes_.
Use `npm install` or see https://example.com for more.

Quotes with formatting:

> This is a *quote* with **formatting**
> that spans multiple lines

Complex example:

Meeting notes for [[Q1 Planning]]

> Key decision: use ^^XChaCha20^^ for encryption

Tasks: #urgent
- Implement `crypto.encrypt()` function
- Review ~~old approach~~ and **commit new code**
- Deploy to https://lithium.ac