Who
I run Omarchy. Asahi. Hyprland. Quickshell draws the bar. Naarchy sits in the camera hole. The creative suite became omadesign. The public Omarchy site was still a static tree I had forked as omarchy-site.
I ship other properties in TypeScript and TanStack. When the site I point people at does not match the stack I build in, I feel the seam every time I open a PR.
This rewrite is for the operator who already lives on Omarchy and wants install, manual, news, and foundation raise inside a TanStack Start app. Also for anyone evaluating Start on a real content-heavy surface.
I did not invent Omarchy. DHH and Omacom did. I rebuilt the site shell.
What
Repo on GitHub: michaelmonetized/omarchy-site-tanstack-start Live vercel.app deploy named after the repo.
Stack is TanStack Start plus Router and React 19.
Also Tailwind v4 and the shadcn UI kit.
Root title stays the Omarchy brand line.
Home plays Quattro first-boot, holds empty sky, then etches the mark. Below that: foundation raise chart, patrons, menu, themes, Hyprland, Quickshell, plugins.
Manual: 52 chapters as typed modules. News: 16 posts. Install for PC, Intel Mac, and Apple Silicon community builds. ISO constant is 4.0.2. Import helpers pull HTML from the sibling static site checkout.
Deploy config turns off git auto-deploy for main and master. Ship is deliberate.
Where
It runs on the Vercel preview URL. OS truth remains omarchy.org and omacom/omarchy. Import sibling on this machine: Projects/omarchy-site. App clone: Projects/omarchy-site-tanstack-start at d98a362.
Audience sits next to Omarchy and Asahi people and next to builders already on TanStack Router.
When
2026-08-31. init scaffold.
2026-09-01. Landing, layout, shell. Full manual chapters. Rest of site including PC and Mac install. Hero mark and empty sky etch.
2026-09-02. Square patrons, 13M raise, Quickshell on home. Three commits on Safari etch. CTAs to install, manual, repo. Nav pinned right.
2026-09-03. README plays the desktop walkthrough. Fifteen commits. About three days from scaffold to the URL that still answers.
Why
I needed the Omarchy public face in the same toolchain I use for everything else I ship. Static HTML is fine for the upstream project. My working copy wanted file routes, typed content modules, and a deploy I control.
So I imported the manual and news, wired the raise chart, fixed the etch until Safari stopped lying about the canvas, and left auto-deploy off. The OS stays theirs. The Start app is mine to break and rebuild.
ISO still downloads from omarchy.org. Plugins still live at omarchyplugins.com. This repo is the site rewrite as of September 3, 2026.