When comparing Blogger vs Hugo, the Slant community recommends Hugo for most people. In the question“What are the best solutions for a personal blog?” Hugo is ranked 7th while Blogger is ranked 19th. The most important reason people chose Hugo is:
Code can be viewed [on GitHub](http://github.com/spf13/hugo).
Ranked in these QuestionsQuestion Ranking
Pro No ads
You can turn on ads if you want, but you can also keep your Blogger blog ad-free. That is different from WordPress.com (free hosted WordPress) where there are ads, and you cannot do anything about it.
hosted by google
Pro Every Google account has one
If you have a Google account from any other of their services, such as Gmail, Youtube or Google+, you automatically have a Blogger account as well.
Pro Supports multiple authors
Multiple people can contribute to a single blog.
Pro Custom domain support
You can use either your own URL or a *.blogspot.com URL.
The Blogger API allows you to publish and manage your content via a custom client app
Pro Allows custom advertisements
Such as project wonderful, or just google adsense,. so you can make money from your blog.
Pro Android and iOS mobile apps
Allows viewing and editing content from your mobile device.
Pro Analytics integration
There's very basic analytics, but you can upgrade if needed.
Pro Open-source and free
Code can be viewed on GitHub.
Pro Single Binary - Cross Platform
Pro No dependencies
All other SSGs expect you to have a full toolchain setup for their language. Hugo is written in Go and distributed as an executable for unix, linux, windows and mac. Just download and run.
Pro Clean workflow
Create your new site, run the Hugo server, edit. Lather, rinse, repeat. Hugo stays out of the way.
Pro Good documentation
Pro Many themes available
Pro Draft mode
Allows you to see changes in real time.
Pro Very active community
Pro Easy to add new content types, data files, and taxonomies
Con Bad post editor
It is a WYSIWYG html editor, and it would be a bit better if it used <p> tags. Instead it uses divs and brs everywhere, which leads to inconsistent or just crappy typography and spacing.
Con Limited authorization system
Sadly the authorization system is fairly limited. Co authors can post and publish, without you getting a chance to pre-check their posts as an admin. e.g. you can't give them "create" and not give them "publish" permissions. They can only edit their own posts however.
Con Can be very slow
Loading times can be huge - results may vary on your use of template, but even a fairly lightweight template can load quite slow.
Con Not fully HTML4 or 5 compliant
And impossible to get it perfectly accepted by the W3C verifier no matter how much you tinker.