Moving the portfolio onto PocketBase without wrecking the existing app
The main job was adding new portfolio collections and admin workflows without touching the collections that were already running in production.
Why move the portfolio
The portfolio had outgrown a pile of local data files, but the real constraint was not speed or convenience. The existing PocketBase app was already in use, so the migration only counted as a win if it added a portfolio layer without breaking the data that was already in production.
What changed
Instead of forcing categories, projects, docs, and blog posts through one overloaded admin page, each content type got its own collection and editing flow. That kept the write paths separate and made the data model easier to reason about.
What mattered
The migration work was mostly about boundaries. New collections, new routes, and new admin actions had to fit into the same app without turning the existing system into collateral damage.
Result
The portfolio now reads from PocketBase the same way the rest of the app does, but the upgrade path stayed controlled. That was the entire point.