So you’ve got a collection of markdown files. Maybe its a personal knowledge base, or a team wiki, or project documentation, or even a statically-generated website like tygertec.
There’s a lot to love about markdown :
Easy to edit Easy to learn Fairly easy to read Plain text format will be readable forever Easy to throw in a Git repo for change tracking In fact, I’m writing this blog post in markdown.
Premium course that teaches Hugo-essentials while migrating away from WordPress
Static site generators aren’t new, but something about the fresh simplicity of Hugo is turning heads. We’re in the early stages of the Gartner Hype Cycle , but expect to see media outlets abuzz with tales of Hugo “making waves” and “disrupting stuff”. Even de facto strongholds like WordPress have begun losing ground to the inexorable spread of the Static Invasion.
But between all the skirmishes, turf wars, and soap-box-soliloquies, how do you know if Hugo is the right match for your site, or if it’s even worth the hype? Here’s what you need to know, reader’s digest style. (from Migrating WordPress to Hugo, Step-by-Step )
I won’t kid you; the road to course creation is riddled with potholes, roadblocks, and sketchy checkpoints. It was hard. But the solution to each obstacle taught me new skills and valuable life lessons. I think it’s time to document those lessons.
Hugo isn’t even at version 1.0 yet, and it’s already of the one of best static site generators in the world. A switch from WordPress to Hugo can save you money, improve site performance, and harden site security. For the shiny gopher-shaped cherry on top, do I dare say it? — Hugo is fun.
With your current site stuck in WordPress, how do you get from point WP to point Hugo?