The project
What was wrong
DoggByte is one developer with a growing set of products, and his website had to keep up. It never stayed put. He started on free hosting, moved to cheap hosting, and each move meant starting over, rebuilding a site he had already built.
He is not a server administrator, and he did not want to become one. Self-hosting turned into a chore of its own, one more job competing with the software he actually wanted to write.
What we did
We took care of the whole website. He edits his content, commits it to his own repository, and that is the end of his involvement: we set up a CI/CD pipeline so every commit redeploys the site automatically.
The site itself is fully accessible and offers light and dark modes, so it reads comfortably for everyone who arrives to look at his work and products.
What happened
Updating the site now feels like the rest of his work: change a file, commit, and it is live. The content is his and so is the repository, which means he is never locked into a platform that has to be rebuilt from scratch when circumstances change.
We host the site and handle the updates and patching, so the server side is no longer his problem.
