This post is not about migrating your WordPress site to Hugo, it’s about transitioning from your WordPress mindset to Hugo’s!
By cautiously comparing Hugo’s concept and vocabulary to some you’re already familiar with, we might be able to smooth out this learning curve for you!
So let’s bring up the the_post(), the_loop and the Template Hierarchy in order to better understand Hugo’s own construct!
In the first part of this Hugo’s Multilingual series, we covered how to manage our content translations and use those in our templates.
But what about translating strings for our project or our theme?
In this second part, we’ll see how Hugo, using its familiar data structure and configuration file, allows us to localize strings in any number of languages with minimum hassle.