Video Summary - I Rebuilt My Entire Website in Astro… Was It Worth It?

Summary of technological concepts, features, and analysis (Astro vs. Hugo migration)

Hugo was excellent as a minimal static site generator, but the speaker had started “bastardizing/frankensteining” Hugo into a more of a creator hub with features that didn’t align with Hugo’s ideal model.
Primary migration motivations:
- Extra functionality / advanced integration needs that required changes beyond Hugo’s usual workflow
- Desire to bring over Hugo’s publishing flow (Markdown → post creation using an archetype/page outline), but implemented differently in Astro

The rebuild was executed as a large PR:
- ~2,000+ generated files
- 813 pages
- Kept a lot of aliases for compatibility/URL continuity
- Cutover reportedly went smoothly initially, with no major issues found
Remaining gaps after the migration:
- Search was still being improved (a functional placeholder existed)
- Downloads/purchase access integration was being improved

Downloads / purchases access
- Previously: users emailed the speaker and were directed through an account/profile UI (“little man” flow)
- New path: /downloads → “access purchases” → enter email → shows orders → download
Forms + Discord support integration
- Added tighter forms integration connected to Discord
- Goal: better support routing and increased traffic for users needing help
Live stream content balance
- Prior issues: live stream audience behavior sometimes caused poor PR quality and overhead
- Plan: a healthier cadence—around monthly
- Added chat replay/watchable stream history accessible from the site

After migration, the speaker ran a structured review loop:
- Planned code cutover
- Used multiple AI agents iteratively to critique and reach a “good functional state”
Scale/cost notes:
- PR contained ~50,000 lines
- ~7,400 deletions
- Cost referenced as: “100% of my $100 plan for a whole week”
Outcome:
- Not “perfect,” but good enough to merge and clean up later
Critiques of AI output:
- Tended to add rounded corners everywhere
- Introduced spacing/layout issues that required manual correction

Astro improved CSS organization:
- Moved from many CSS partials to one master CSS
- Easier manual editing and future feature additions
Visual quality improved
Astro also made it easier to hand styling work off to a developer for enhancements

Lighthouse results:
- Lighthouse scores were tracked as changes were made to verify improvements
CI integration:
- Added directly into the repository
- Included monitoring concepts tied to site features (example mentioned: live streams)
Code scanning:
- Added CodeQL
- Rationale: Astro can involve more “real” runtime environment concerns (Node/NPM, packages, and security vulnerabilities)
- Hugo was treated as more minimal/static, with a smaller risk surface
Cloudflare analytics issues:
- Console errors with Cloudflare analytics were noted
- The speaker estimated they may have missed “hundreds of thousands” of visits due to tracking/analytics problems
- Despite that, they didn’t prioritize user tracking

The speaker explicitly noted the migration did not magically make the site faster.
Ad/monetization analysis:
- AdSense revenue dropped around the conversion period (estimated 20–30% cut)
- Likely cause: Astro’s rendering strategy can defer/hydrate scripts after the request, so ads may load later—users may leave before ads appear
- AdBlock/Brave usage further reduced ad views (many viewers block ads)

Framing of the migration:
- A challenging, high-effort project
- Not recommended unless you truly need the advanced features/creator-hub capabilities
Recommendation positioning:
- If you just need a blog (text + images), Hugo is still the better fit (simple, minimal)
- Astro is praised as “chef’s kiss” / highly capable, but requires security + quality checks due to heavier tooling

Primary speaker: Chris Titus (from the video “I Rebuilt My Entire Website in Astro… Was It Worth It?”; author of ChrisTitus.com)
Sponsor/source mentioned: Blacksmith (replacement for GitHub runners)