Several times I’ve used wordpress, but nowadays exist differents platforms to created a blog, and I would like to know what are your preferences, recently I’ve looking for options and I found few options like: jekyll, hugo, gatsby, next.js, but them really worth to use one of that options before wordpress apparently the most popular?
IMHO, “popularity” in itself is not a very good reason to use anything in particular.
I would consider quite a few things. eg.
- can it easily do what I want it to do?
- how large is it’s support community?
- is it relatively mature, stable and secure?
- is it easy to customize where it lacks something I need?
Unfortunately I know of no easy way to judge what might be “best” until I try each to see how well it fits my particular use case. There is no such thing as a one size fits all “best”.
Thanks for your answer @Mittineague you are right, popularity is not a good reason to made a choice.
Static sites are the way to go imho. There’s no reason to have a heavy backend and DB for a static site. Plus, security just goes entirely out the window. I don’t think Next.js and Gatsby aren’t really for blogs (I love Gatsby though), but VuePress and Hexo are if you want to go the JS route. Jekyll and Hugo are good choices too.
I’m also a big fan of Netlify.com for hosting. It’s free and they will do the build for you.
Thanks for your reply, I made a little research about Hexo and VuePress and looks very good, thanks for your suggestions!
It depends on the nature of the site you’re proposing to build. If it’s fairly straightforward, WordPress is still the easiest to develop and deploy. Joomla and Drupal are alternatives that have merit. There are lots of plugins for WP, which means you’re able to express your design in many different ways.
I can’t see that Joomla and Drupal are a good choice for a blog.
Joomla, Drupal, Wordpress, etc., all have security issues and constantly have updates pushed. Plus they are WYSIWYG drag-n-drop, so… I don’t care how many templates they have, it all has that “cookie cutter” look and feel.
If you know how to code and can build one from scratch, any server-side solution (ie, ColdFusion, PHP, ASP, etc.) will work. And be sure to utilize all the security that the server-side offers, to guard against things like cross-site scripting and SQL injections.
I, myself, prefer ColdFusion. I’ve been coding CF since 2000, I love it, and Adobe (or Lucee, too) make use of the ESAPI (oWasp Enterprise Security API) for security. Robust, easy to learn, customizable. Just sayin’.
^ _ ^
That’s my rule of thumb for life in general, but with code I would actually take it into consideration. In fact I would actually go a little deeper and say that popularity and it’s “activity” are quite important because:
- Popularity usually means there’s lots of support (with really popular frameworks, Google will give you the answer before even opening up the search result!)
- It’s “activity” tells you that whatever bugs you see today will likely be fixed
- Really popular frameworks have rich plugin ecosystems, meaning you need to code less to get the same result
I ran into an issue recently where I wasted almost an entire week with a library because I didn’t consider it’s popularity. It was a very well developed web proxy, but unfortunately it wasn’t popular enough that I could ask questions or get timely responses when I came across a bug and had to abandon it.
I agree with this. Popularity can be a major factor, especially if you are working on a team. Nobody wants to use your home rolled version of something or the random library you found on github with 3 stars.
But when you’re comparing things that could all be considered popular, then it’s less of an issue.