Migrating from GitHub Pages to our own VPS.
Taking the reins.
Date:It's been a while since I last published something, but we're inaugurating a new home, and that warrants a post (even if it's brief).
Why leave GitHub Pages behind?
To be frank, there are good reasons to use GitHub Pages. It's free and comes with a set of basic functionalities for static sites, for the vast majority of situations Jekyll is more than sufficient and allows for a frontend-focused development approach.
But one of the problems is just that, it only allows focusing on the front end.
Another issue is if you're not a big fan of Jekyll and its pipeline for testing site changes locally, it's a nightmare.
Advantages of your own server.
The main advantage of having a server is the possibility of being in charge of the backend, finally being able to manage automatic tasks, as well as being able to create and access our own APIs not just in a local environment.
Moreover, having access to the backend allows us to test other technologies more appropriate for a fullstack dev (hello htmx) and use a much more familiar environment (Did I mention I'm not a fan of Jekyll?).
Another reason is that the current pipeline for publishing a change on the page became an obstacle when organizing ideas for publication, to the point where just the idea of having to touch it acted as a deterrent.
What now?
With this new page, I plan to continue experimenting with much greater flexibility and to be able to publish updates about my other projects and developments.
For the rest of the year, I'm going to work on migrating some things from the GitHub page to here, especially projects, and reorganizing my portfolio items.
I have many things in mind that I hope can leave the inkwell.