write a phile#
A phile is one Markdown file in philes/. When it lands on main, the site rebuilds itself within a minute.
the short version#
git clone ssh://git@exploit.golf/vmfunc/exploit-blog.git
cd exploit-blog
$EDITOR philes/2026-11-21-my-first-phile.md
git add philes && git commit -m "phile: my first phile" && git push
No push access? Fork it on exploit.golf and open a pull request, or ask in #exploit.golf to be added as a collaborator.
the file#
Name it YYYY-MM-DD-some-slug.md. The date is the publication date and the slug becomes the address: zine.exploit.golf/p/some-slug/.
Start it with a small header:
---
title: forging passkeys for fun
author: yourname
tags: webauthn, crypto
summary: One line that shows up in the list and in link previews.
---
The phile itself, in Markdown.
| field | what it does |
|---|---|
title |
the headline. Without it the slug is used. |
author |
your exploit.golf username, so the byline links to your profile. Several authors: alice, bob. |
tags |
comma separated. Each tag gets its own page. |
summary |
optional one-liner. |
draft |
true keeps the file out of the site while you work on it. |
what Markdown can do here#
Headings, tables, footnotes, fenced code with a language name for colours, images, <details> blocks and plain HTML for the things Markdown cannot say. Scripts and embeds are stripped when the site is built.
Images and other files go in static/ and are linked as /static/your-file.png.
looking at it before you push#
pip install markdown pygments
python3 build.py . _site
python3 -m http.server -d _site 8000
The fonts and scanlines come from the server, so a local preview looks plainer than the real thing.