Rebuild for Astro’s v5 Content Collections update

Astro has been evolving fast, and eventually that momentum caught up with my site. The jump to Astro v5, especially the Content Collections overhaul wasn’t something I could patch around with a few quick fixes. The changes were deep enough that the most sensible option was a full rebuild, not because the old structure was broken, but because the new system finally made a cleaner architecture possible.

Reworking the Content Layer

The biggest challenge was rebuilding the logic that powers the site’s content layer. Content Collections are fantastic, but the shift in how they structure and expose data meant rewriting the code that feed everything from the table of contents to recent posts, categories, and tags.

It meant reshaping the entire flow of how content becomes usable data. Getting the collections to output clean, predictable arrays took the most time, but the payoff is huge. The new setup is far more maintainable, far more explicit, and far easier to reason about when adding new content types.

Goodbye Preline, Hello DaisyUI

Since I was already elbows‑deep in the rebuild, I took the opportunity to address another long‑standing annoyance, Preline’s JavaScript integration.

Preline is great in isolation, but its JS based component model has always clashed with Astro’s JavaScript philosophy. Importing Preline’s scripts felt like forcing two different design philosophies to coexist, and debugging those interactions was never pleasant.

So I switched to DaisyUI, and the difference was immediate.

DaisyUI ships 0 KB of JavaScript, relying entirely on semantic, Tailwind‑style classes. It feels like a natural extension of TailwindCSS rather than a separate framework bolted on top. No hydration issues. No script imports. No “why is this component behaving differently in Astro?” moments.

To round out the visual consistency, I added Tailwind CSS Typography. After ironing out a few quirks with overriding prose defaults, the site settled into a cleaner, more content‑focused aesthetic that feels much more aligned with Astro’s philosophy.

Rebuilding the Layouts

Switching UI libraries meant revisiting every layout and component. I rebuilt each one using DaisyUI’s class‑based patterns while keeping as much of the original structure as possible. The process was surprisingly smooth, DaisyUI’s approach makes it easy to drop in components without fighting a framework‑style API.

Where Preline often required “component + JS + configuration,” DaisyUI was simply “add the right classes and move on.” It made the rebuild feel less like a chore and more like an opportunity to tidy up code that had grown messy over time.

The Result

I’m genuinely happy with how the rebuild turned out. The site is cleaner, more consistent, and noticeably easier to maintain. The new Content Collections setup is predictable and flexible, DaisyUI integrates beautifully with Astro, and the whole project feels more future‑proof.

Astro v5 pushed me into a rebuild, but the end result is a site that’s better structured, easier to extend, and far more enjoyable to work with.