schliewe.systems
← cd ../blog
#meta#nextjs#mdx#ref-radar

How this site is built

Posts are MDX files in git. The intro paragraph wraps around a radar you can drag. Every repo a post mentions is a live card from ref-radar.

$ whoami Jack Schliewe · 16 November 2026 · 2 min read

This site and ref-radar look like one system on purpose. They share the bar at the top, the Search> box, which searches ref-radar, and two phosphor colors. Click [p7] in the bar to switch to amber.

FrameworkNext.js 15, every blog page built ahead of time
PostsMDX files in the repo, published with git push
TypeTempleOS's 8x8 font for headings, JetBrains Mono for text
RefsCards and the radar come from ref.lookit.space

Posts are files

Each post is one .mdx file. It exports its own title, date, tags and the refs it cites. There's no database and no admin panel to secure. The contents list on the left comes from the post's headings.

[ref] mdx gh:mdx-js/mdxCompiles Markdown with embedded JSX into components for React, Vue and other frameworks, built on the unified and remark ecosystem.JavaScript · MIT · reuse copy · stable · ★ 19,862

Citing prior art

I search ref-radar before I build anything. A post cites a ref by its id, and the card shows what the project does, its license, and whether you can reuse its code:

<Ref id="gh:shuding/nextra" />
[ref] nextra gh:shuding/nextraTurn Markdown and MDX into a site on top of Next.js and React, with example projects to copy from.TypeScript · MIT · reuse copy · stable · ★ 13,956

The paragraph that moves

Pretext lays out the home page's intro. It measures text without asking the browser for layout, which makes it fast enough to rerun on every pointer move. Each line gets its own width, so the text opens around the radar wherever you drag it.