New Design, New Architecture
More than a decade after I launched this site on WordPress.com, I’ve moved away from the world’s most popular CMS.
My site now runs on Eleventy, hosted with Netlify.
While that may be the most newsworthy item in this incarnation, it’s not the most important. I made this change because I felt the need to get out of my comfort zone. After working with WordPress for most of my career, I don’t use it at my current job. That excited and terrified me at the same time. A new stack here would help me learn something different and force me to broaden my tool selection. That’s not to say I’m not thankful for WordPress. I forged a lot of my web skills because of it.
A Long Road
My choice, Eleventy, works with Markdown. I wanted to embrace it with this move because I’ve started to write more with IA Writer. Eleventy doesn’t force you into one way of working either, supporting many different template engines. It requires little configuration to work, but you can configure much of it too. Lastly, its community emphasizes accessibility and performance, something I believe in at my core.
I set out to create a more bright, enthusiastic design, but went for an old standard. Black, white and high contrast. It’s like other designs I’ve created here and gravitated toward in the past. Cooper Hewitt by Jester Jenkins stands out as the headline font, providing some punch. You can see a dash of color on hover and focus when interacting with links and buttons. I like it. Simple, fast, bold.
I took the slow and steady approach, hoping this will be my site’s architecture for the next decade.
- I used a WordPress plugin to export everything, and get front matter in shape.
- I decided to drop comments, but may bring them back in the future.
- I deleted a handful of irrelevant posts. These photo gallery or single photo posts I tried on the site didn’t stick.
- I went through all my content, including images, and tidied things up.
- I kept the build pipeline simple, letting Eleventy do the work of minifying it.
I have a punch list to keep working through for the future. Things like a print stylesheet, offline support and site search. Without everything that WordPress gave me, I learned more. For example, I now know more about
srcset than I ever did. I wrote that code myself this time. Not having the vast theme and plugin directories as a fallback has slowed me down. That’s a good thing. I ask more questions of myself. I’ve also missed conveniences too. I spent way too much time figuring out how to best support pretty quotes.