Category
Modern web development practices, tools, and frameworks
34 posts
A developer's guide to choosing a headless CMS for Next.js in 2026 — SaaS vs self-hosted, a full comparison table, and the real publish-to-rebuild webhook loop.
An honest Hugo vs WordPress comparison across eight dimensions — publishing model, performance, security, editing, theming, maintenance, cost, and team workflows — with a verdict per use case.
An honest comparison of Decap CMS and TinaCMS: config-driven simplicity vs GraphQL visual editing, what each costs, and when git-based content stops scaling.
Astro and Next.js made opposite bets about JavaScript. For blogs, docs, and marketing sites, here's which bet pays off — dimension by dimension, with a verdict per use case.
We deployed both, broke both, and paid both sets of bills. Here's where Ghost wins, where WordPress wins, and how to pick based on what your blog actually needs.
A developer-focused comparison of 7 Wix alternatives — UnfoldCMS, WordPress, Webflow, Astro, Ghost, Framer, and Next.js — scored on code access, data export, hosting control, and performance headroom.
Teams leave Webflow over pricing, CMS item limits, and lock-in. We compare 7 alternatives — UnfoldCMS, WordPress, Ghost, Framer, Astro + headless, Squarespace, Statamic — on the four things that matter.
llms.txt is a proposed markdown index at your site root that tells AI systems which pages matter. This post covers the llmstxt.org spec, llms.txt vs llms-full.txt, the unproven-adoption debate, and how UnfoldCMS auto-generates both files.
A developer's guide to CMS webhooks: why headless front-ends go stale without rebuild triggers, how to verify HMAC-SHA256 signatures in Node, and the deploy-hook, cache-purge, and search-reindex patterns that keep static sites fresh.
Ten tactical shadcn/ui patterns that survived 12 months and 205 admin pages in production. Form schemas, DataTable columns as data, theme switching via CSS variables, Sheet+Dialog composition, server-side state, variant discipline, type-safe URLs, server-action pattern. Copy-pasteable, real code.
shadcn ships 6-7 releases per month. Our CMS runs 51 components, 18 modified. The bi-weekly audit workflow that keeps our fork in sync with upstream without breaking — pin commits, track modifications, audit cadence, when to fork hard.
Two years and 205 admin pages later: why shadcn/ui beat Radix Themes for a production CMS admin. The comparison most blog posts get wrong, the trade-offs we hit, when Radix Themes is the better pick.