acker.cloud
The professional site and resume: enterprise integration work, leadership writing, and a technical wiki, written in Notion and shipped as a fully static Next.js site.
CREATED MAY 30, 2025 · UPDATED SEP 17, 2026
PROBLEM
A resume that is a PDF is a resume nobody reads and nobody can link to. The professional record and the technical writing lived in different places, and neither had a URL worth putting on anything.
HYPOTHESIS
Notion as the editor and Super.so as the renderer gets a real site with no build step and no deploy — and the part worth owning, the design, can still be version-controlled as injected snippets.
ARCHITECTURE
Notion is still the editor, but no longer the renderer. `npm run sync` pulls the portfolio and wiki into a typed snapshot, zod validates it, and every route is prerendered as static HTML, so the Notion token is needed at sync time and never at build or runtime. Vanilla CSS on custom properties, a contrast gate that blocks the build, and client islands only where interaction needs one.
The first version rented the renderer too: Super.so served Notion pages with hand-written snippets injected from the brand repository. That was replaced on 2026-08-28.
STACK
RESULT
Live, rebuilt from Super.so onto its own static Next.js site in August 2026. Since then it has absorbed the standalone resume site as /resume, opened a public beta page for collect., and written up Stagger at /stagger in Stagger's own palette.
LEARNINGS
- Owning the stylesheet and renting the CMS is a better trade than owning both.
- A site you can edit from your phone is a site that stays current.
- Renting the renderer stopped paying once the design wanted things the injected-snippet slots could not hold. Keeping Notion as the editor and owning everything after the sync kept the phone editing and lost the ceiling.