When comparing Fossil SCM 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 5th while Fossil SCM is ranked 26th. 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 All in one
While most other platforms allow either online blogging, or development offline and hosting on some other platform, fossil allows you to develop locally, host it locally, view it locally, and you can substitue locally with remote if you want to.
It's just one file. Fossil.
It is. It is also free as in libre, as in the license is similar (or equivilant) to BSD-2
Pro Simple to use
Fossil doesn't depend on a specific language to be present on the target or development system. Just write, commit, and done.
Pro Open-source and free
Code can be viewed on GitHub.
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 Many themes available
Pro Very active community
Pro Single binary - cross platform
Pro Clean workflow
Create your new site, run the Hugo server, edit. Lather, rinse, repeat. Hugo stays out of the way.
Pro Great multipurpose development platform
We are using Hugo as the base-framework for a full blown knowledge management system, idea-management and inhouse brainstorming tool. Hugo source-code is well structures and comes with top components out of the box, that makes every solution built on this framework incredible fast and scalable accross platforms and corporate silos! Hugo - when being used as a framework is a game-changer that puts Sharepoint, Wordpress and Co. back to the shelf.
Pro Single source publishing
Can create PDFs, eBooks, RSS-Feeds, language and market specific Websites from single content folder.
Pro Good documentation
Pro Draft mode
Allows you to see changes in real time.
Pro Easy to add new content types, data files, and taxonomies
Con You have to do everything manually and know what you're doing
It is similar to the "Writing your own solution" option