WordPress to Hugo Update IV
One foot in front of the other.
As of right now, everything static is being hosted by Hugo. All the blogs posts, all the pages, and all the related media files. I even managed to get Hugo to automagically resize all the images to a reasonable size when the site is built. Getting that particular feature up and running with Hugo was surprisingly easy. The way I solved it is probably not pretty in terms of what the static site generator can do, but it works. There are still a few issues to handle, like properly left aligning images of a certain size, but I haven’t bothered with fixing that right now because it’s mostly a problem with some of the older post.
The next step is to move the semi-dynamic content from WordPress to Hugo. The most basic of these are the A Book A Month pages, and I’m trying to devise a good way of moving them to Hugo. Right now I’m leaning towards building Markdown files from the data in the database, then push the files to Git, and finally have the Jenkins pipeline build everything just like any other Markdown file. Alternatively, Hugo’s data templates might be an option, but I haven’t looked into that too closely yet.
During my work on moving from WordPress to Hugo, I’ve read through a lot of the stuff I’ve written over the year. And, man, I have written a lot of stuff over the years - some of it quite cringeworthy, to be honest. I invite you to take a dive into the archive and have a look for yourself.
And, yes, I hope to get all the lists paginated in the not-so-distant-future.
This post has no feedback yet.
Do you have any thoughts you want to share? A question, maybe? Or is something in this post just plainly wrong? Then please send an e-mail to
vegard at vegard dot net with your input. You can also use any of the other points of contact listed on the About page.