TechSnazzy started years ago as a business name, something I could put on a website and use to sound a little more official while I was building things and figuring out this industry and contracting. That business is done now, and the name has kind of outlived its purpose. What’s left is just me, so I decided it was time for a website and an online identity that actually reflects that instead of a business that no longer exists.

That’s how SeanTechGuy came about. It’s simpler, it’s personal, and it’s a much better fit for what this site actually is at this point: a place where I write about the stuff I’m learning and working on, not a storefront.

What actually had to change

Making the switch wasn’t just a matter of updating a logo or renaming a folder. The site itself has lived on GitHub Pages for a long time, with a custom domain sitting in front of it, DNS managed through Cloudflare, and the domain registered through Namecheap. All of those pieces needed to be touched in some way to move the public facing identity from techsnazzy.com over to seantechguy.com without losing anything in the process.

At a high level, this meant getting the new domain pointed at the same GitHub Pages hosting the old one used, updating the hosting configuration to recognize the new domain as the official one, and making sure a valid certificate was issued so the site would still load securely under the new name. None of that touches the site’s content or code, it’s purely about which address the site answers to.

The other half of the work was making sure the old domain didn’t just go dark. Anyone who still has techsnazzy.com bookmarked, linked, or indexed in a search engine gets automatically forwarded over to the matching page on seantechguy.com rather than hitting a dead link. That redirect setup lives entirely in DNS and routing rules, so it happens quietly in the background without anyone needing to do anything differently.

One thing I was careful about the whole way through: my email address tied to the old domain didn’t change and wasn’t touched at any point during this. Moving a website’s DNS around can get messy if you’re not paying attention to what else is sitting in that same DNS zone, so this was as much about knowing what not to touch as it was about making the actual changes.

Where things stand now

seantechguy.com is live and is now the site’s real home. techsnazzy.com still works exactly the same as before, it just quietly redirects anyone who lands there over to the new domain. Nothing about the content changed, just the name on the front door, and honestly it feels like a better fit for where I’m at now than TechSnazzy ever did.

A quick note on how this was written

Yes, I used Claude to write this post. Don’t judge me too hard for it. The idea, the outline, and every bit of the actual work described above came entirely from me, Claude just helped turn it into something readable. That’s basically how I use it these days: I do the thinking and the doing, then it takes my rough notes and turns them into a polished writeup faster and better than I’d get around to doing myself. I’m alright with that division of labor.