The beauty of the web is there’s room in it for everyone.
I’ve always liked the idea that my “place” could be a simple website. Maybe share a little bit about myself, my job, and whatever else.
For a long time, I hosted a portfolio website on Squarespace. It got the job done alright. But I found Squarespace sites to be slow and clunky. They’re customizable, sort of. But it wasn’t enough.
My past website iterations also felt really scattered across different subscriptions and services. I wanted to centralize it all, and have as close to absolute control over the look and feel as I could. I also wanted to challenge myself by taking on more of the backend stuff.
So I finally got my shit together and made a website.
After searching around for a while, I found this template on GitHub and forked the repo. It’s called al-folio.
I wanted something with a clean look, plus a blog functionality. A proper CMS like Wordpress felt like overkill given that I probably won’t be posting all that much. I like how this particular blog lets me write entries in Markdown, which is super simple and lightweight. (Plug: I use a great open-source macOS app called MacDown.)
All the code is stored in my forked GitHub repo, which I push changes to via Visual Studio Code. From there, everything else is AWS.
I used to host my domain on Hover. But I knew from the outset I wanted to at least try to run everything through AWS. I wanted to teach myself how it all worked given that it’s more or less the industry standard. AWS is also supremely integrated and, importantly for a newbie like me, well-documented.
The scale at which I’m using AWS is microscopic. But I’ve learned a lot about it and I’m interested in checking out more services as I go.
I’m mostly using Amplify, Route 53 and S3
I stumbled upon Amplify almost accidentally.
The repo I forked is powered by Jekyll, and one of the big selling points was how easily one could deploy on GitHub Pages. But I was ride-or-die AWS. So I started searching for a similar kind of plug-and-play deployment option. Lo and behold, AWS Amplify offered exactly that.
All I had to do was link up my forked repo’s master branch to Amplify, make a few clicks, and the site was live.
But what about that custom domain?
Here’s where Route 53 entered the fold.
A few months ago, I did the yeoman’s work of swapping my registration from Hover to Route 53, which is the AWS Domain Name System (DNS) service. The process was a bit of a pain. But it paid off when the time came to deploy the Amplify app. The tight integrations across services meant an extra couple clicks was all it took to have the site up and running at my personal domain.
Other than that, I’m hoping to figure out how to use S3 image URLs in blog posts like this one. Right now I have to store them locally. But that’s the S3 explanation.
The bottom line
The website is up. I’m pleased. My total AWS bill is about $5/month — a solid savings compared to, say, Squarespace’s business plan ($18/month).
And the personal growth? Priceless.