A few days ago, I relaunched this blog using the static site generator, Hugo. The transition was fairly smooth, but I had a bit of pain getting my content out of my old site. I had somehow locked myself out of my old server on DigitalOcean (still not sure how, and the DO support guys were equally baffled; the theory is that I permabanned myself with fail2ban. Whoops.) Luckily, I still had access to the console from the web-based VNC tool they have, so I was able to get a backup of my blog’s database.
Once upon a time, this blog was a WordPress blog. I like WordPress. I like it a lot. It’s a pretty cool piece of software that has a huge community behind it. It’s really easy to set up and use, and making plugins and templates is a breeze (once you get used to it). But now, this site is built by Hugo - a static site generator created in Go. So why switch?
I have been working on a custom WordPress plugin at work that utilizes AngularJS. After some playing around with it, I was excited to stretch my legs and use Angular in production. I come from a background heavily influenced by PHP and jQuery, so getting into Angular has been a challenge because it’s an entirely different way of thinking. It’s a fun, rewarding challenge, but I’ve found myself having to relearn how to do simple tasks.
I threw together a little repo to build Node+Express webapps. Check it out on GitHub; read below for the story. It’s very simple and comes in three flavors: Master branch: installs Express and a few of its middlewares. It sets up a public directory with placeholders for CSS, JS, and image files. It sets up a couple basic routes, has a simple starter controller, and an extendable config file with a few prepopulated options.
I’m building a site for work, and we’re coming with ideas to improve the user’s experience on mobile. The idea came up to build one of those headers that appears when you start to scroll up. I like these, because it frees up part of your already-limited viewing space from having a nav stuck to the top of the screen, but it also means you don’t have to go all the way back to the top of the page if you want to access the site nav.
Wufoo is a neat little service that lets you create and manage webforms. This is not a paid guerilla advertisement, by the way. I don’t want to have to deal with form processing, and found out about Wufoo after a little bit of research. One of the selling points for me is that they have an API, so while they handle the grunt work of saving form data, I can have complete control over the look of my forms.