ProcessWire vs Wix
When comparing ProcessWire vs Wix, the Slant community recommends ProcessWire for most people. In the question“What are the best web content management systems?” ProcessWire is ranked 1st while Wix is ranked 12th. The most important reason people chose ProcessWire is:
You will always find one to respond politely in the forums. Sometimes even the creator Ryan Cramer himself.
Specs
Ranked in these QuestionsQuestion Ranking
Pros
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.
Pro Functionality can be extended with community plug-ins
Wix has an add-on store, called the App Market, that includes community developed bits of functionality (such as comments, calendars and integrations with third-party services) that you can add to your site. The store includes both free and paid add-ons.
Pro Straightforward drag & drop interface
There's a selection of elements you can choose from in the sidebar that you can drag and drop into the page and edit. There are common elements such as text, images and buttons as well as less common elements such as blog or online store. All elements can be adjusted to some extent to fit your needs. For example, you can change things like the font, weight and style of text and even crop, adjust colors and apply filters to images.
Pro Personalized templates
Wix comes with various kinds of templates based on the users genre and needs, ranging from personal, blog, club, portfolio to commercial.
Pro Wix Code lets you add custom code and backends to your WYSIWYG site when needed
This means you can add custom interactions and API's to your site when needed, but do most of the editing in a GUI. This helps you avoid the need to redo an entire site if you need custom interactions. Also dead easy to connect a database and have dynamic components based on CMS updates.
Pro Great support
Cons
Con Generated html is very bad
A lot of duplicated css, a lot of absolute positioning.
Con Hard to migrate away
There isn't an option to self-host the site, but neither should there be a need to.