I finally pushed a set of changes that make my online portfolio feel like a real application instead of just a static showcase. The front end is now fully connected to my deployed backend, and everything is wired together the way I would expect in a professional environment.

This was a big milestone for me. Not because it was difficult, but because it represents a shift in how I am building personal projects.

What Changed

  • The portfolio is now backed by a live, deployed backend
  • Front end data is no longer mocked or hardcoded
  • API responses are driving the UI end to end
  • I started building out an admin portal to manage content through a proper UI

Being able to update the database through a front end interface instead of manual changes feels like a huge step forward.

Admin Portal Progress

The admin portal is still early, but the foundation is there. Forms, layouts, and structure are starting to take shape, and I can already see how this will scale as I add more features.

This part of the project really highlights the overlap between my professional work and my personal growth. Clean UI, predictable flows, and maintainable logic matter just as much here as they do anywhere else.

CI/CD Is Live

One of the best changes I made was fully automating the project with CI/CD.

  • Builds and deployments are automatic
  • Changes are validated before going live
  • I spend less time babysitting deployments
  • The whole workflow feels far more professional

This alone makes the project easier to maintain and more enjoyable to work on.

Why This Matters

Turning this into a full stack, automated project makes it more than just a portfolio. It is now a living system that reflects how I actually build software. Clean architecture, real data, real workflows, and real responsibility.

There is still plenty to build, but this was a big checkpoint. Everything from here on out feels like forward momentum.