# moaki.net

notes, projects, and things worth keeping

## Now

everything here is supposed to be a display for some org files i write. so i'm building the parser for org ~->~ html atm.

- setting up gitlab selfhosted (gl.moaki.net  ~->~ gl.bitpolito.it)
- setting up personal hermes agent
- setting up playwirght mcp for qa tests

## Node: phorge — a hub grown from org-mode

started: 2026-06-29 · state: building · updated: 2026-06-30 · stage: growing

phorge renders a public-facing site from my org notes. nothing is authored in the site itself; everything is surfaced by tag. the design thinking behind it is written up in essay:designing-phorge.

### 2026-06-30 — stack: rust + a hand-rolled org parser

committed to rust for only for learing purposes. chose to hand-roll the org parser rather than depend on a library, as i couldn't find anything with the publish semantics i care about are narrow, and i want to own exactly what does and doesn't get surfaced.

## Essay: Designing a personal hub that composts (2026-06-30)

The brief was simple to state and hard to hold: make the ongoing texture of my work legible as a /byproduct/ of notes I'm already taking, not as a second job of "content."

*Structural scarcity over feed-style abundance.* The homepage shows a small, curated surface — a single sentence of current focus and three doors. Depth is one click away, never scrolled to.

*The link-tree mechanic is the differentiator.* A project, book, or course is a /node/. Reading progress, short posts, external threads, and eventually a long essay all hang off that node. The site visualises the engagement trail, not just the latest update. The live example is node:phorge itself.

*Composting, not append-only.* Short posts decay off the front after about a month unless they get promoted into an essay or linked into a node. The point is a living surface, not an archive that only grows.

The site should feel like warm paper meeting disciplined typography — a person publishing the texture of their thinking, not a startup pitching investors.

If this holds, publishing is just: edit an org file, save, run =build=, deploy.

## Essay: What phorge renders from org (2026-07-03)

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
- nested one
- nested two
- another, with children
- back to the top level
- first ordered item
- second ordered item
- a finished task
- a task still open
- the language phorge is written in
- 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.

one centered line

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.

a placeholder image

Raw HTML escape hatch

back-reference arrow.