What phorge renders from org

This page is a living reference for the org markup phorge understands. It is itself an org file rendered by phorge, so what you see is what you get.¹

Inline markup covers bold, italic, inline code, verbatim, underline, and strikethrough. Links come in three flavours: internal like the design essay, external like the org manual, and images (below).

Sections

Any sub-heading under a published heading becomes a prose section — this very paragraph lives under an ** Sections heading and renders as an <h2>.

Even deeper

Nesting continues down to <h6>, so long essays keep their structure.

Lists

Unordered, ordered, nested, tasks, and description lists all work:

• a bullet
• another, with children
  • nested one
  • nested two
• back to the top level

1. first ordered item
2. second ordered item

• a finished task
• a task still open

Rust

the language phorge is written in

org-mode

the source format it reads

Tables

feature	supported	notes
tables	yes	header row auto-detected
footnotes	yes	collected at the bottom
images	yes	local files are copied

Code

fn main() {
    println!("phorge tags source blocks with the language");
}

plain example blocks render verbatim, no language

Quotes, verse, centering

The site should feel like warm paper meeting disciplined typography.

Images

Reference an image with a file: link. Place the file under your org dir and phorge copies it into the site; a caption above a lone image makes a figure.

Raw HTML escape hatch

Sometimes you just need raw HTML.

back-reference arrow.

---

1. Footnotes are collected and linked at the foot of the page, with a ↩