What we write. What we ship.
Architecture decisions, implementation details, and honest lessons from shipping small web apps. The studio's service-business content lives on the studio site — linked below.
How I ship a static Astro app on Cloudflare
The exact boundary I use between prerendered pages, browser-side calculations, Worker routes, assets, cache headers, and release checks.
Read →Canonical strategy across a three-domain product family
How I divide intent, redirects, sitemaps, internal links, and entity references across .online, .com, and VertaFlow without making three sites compete.
Read →What a useful calculator page needs to earn search visibility
A calculator needs more than inputs and a result: clear intent, visible math, useful defaults, explanations, examples, FAQs, and an honest ownership model.
Read →Why I built VertaFlow instead of buying HubSpot
I run a one-person studio in Rome, NY. I was stitching a CRM out of Zapier, spreadsheets, and three SaaS subscriptions I barely used. Here's what broke, and what the CRM had to do to fix it.
Read →Astro vs Next.js: when I reach for each
Static-first for marketing pages, Next.js for anything that needs auth or dynamic data. The actual decision tree I use on real client builds — and why it runs on Cloudflare's edge either way.
Read →From the studio
Website buying guides, Local Visibility, service-area strategy, and client-facing case studies stay on designedbyanthony.com so the domains do not compete.
Browse the studio content library →