Hugo vs ProcessWire
When comparing Hugo vs ProcessWire, the Slant community recommends Hugo for most people. In the question“What is the fastest CMS for web content (news website with some static pages) ?” Hugo is ranked 1st while ProcessWire is ranked 5th. The most important reason people chose Hugo is:
Code can be viewed [on GitHub](http://github.com/spf13/hugo).
Specs
Ranked in these QuestionsQuestion Ranking
Pros
Pro Open-source and free
Code can be viewed on GitHub.
Pro Fast
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 Flexible
Pro Good documentation
Pro Many themes available
Pro Draft mode
Allows you to see changes in real time.
Pro Single binary - cross platform
Pro Single source publishing
Can create PDFs, eBooks, RSS-Feeds, language and market specific Websites from single content folder.
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 Very active community
Pro Easy to add new content types, data files, and taxonomies
Pro Nice and helpful growing community
You will always find one to respond politely in the forums. Sometimes even the creator Ryan Cramer himself.
Pro Custom Fields on steroids
ProcessWire is heavily based on custom fields. All objects (Pages) inside ProcessWire are based on extensible templates comprised of fields that can be easily defined. Many useful fields come prebuilt and they can be extended with modules.
Pro Easy to learn
Processwire is extremely easy to learn. Consider this:
echo $pages->get('title=Hello World')->title; // "Hello World"
echo $pages->get('title=Hello World')->parent->title; // "Home"
echo $pages->find('Template=Category')->count; // 126
echo $pages->find('Template=Category')->each('title'); // ['Audio', 'Video' …]
Selectors are so powerful but yet so easy.
Check out the cheatsheet.
Pro Powerful and easy API
The API is jQuery like;
// find some pages:
$pages->find('template=skyscraper, architect=john, sort=title')->limit(4);
// mutate
$pages->get('title=Hello You')->set('title', 'HelloWorld')->save();
$pages->get('title=Old')->trash(); // trash page
// check user…
$user->isLogedin();
echo $user->name; // guest
$session->login($name, $pass);
$session->logout();
// redirect
$session->redirect($url);
Pro Powerful selector engine
The way you fetch, access and manipulate objects (Pages) in ProcessWire is extremely powerful and easy. You can receive any page and its custom fields, filter, travers, add…
Pro Template Engine Agnostic
By default, ProcessWire comes with 0 assumption on how you handle the output. You have 100% freedom on how you want to develop the frontend. Want to plain output stuff, go ahead. Want to use any number of Templating Engine, do it. Just use as Headless-CMS, okay!
Pro Extensible
Either using the modules already available or writing your own module, using the jQuery-like API.
Pro Open source
Source available on GitHub.