Neos vs WordPress
The question "Why Neos instead of WordPress?" ist quite common. On this page you can find some details on how these two CMS are comparable and where their differences are.
Text von Seb
Some Major releases change something big. When your whole app relies on that one thing, then of course you might have more effort.Extensibility is awesome. You can override all kinds of things without losing upgradeability. The PHP, Fusion and UI parts can all be extended and adjusted to your needs. Some parts are still a bit harder to do, but we are working on improving those with each release.
I was often able to implement small quality of life improvements for editors in 15-30 minutes and deliver it to their system.The initial time needed to build your first 1-2 Neos sites is higher than Wordpress I would say, but shouldn’t be different than other CMS that are also being used for applications. (But I would call every website with interactivity or API connections basically an application)If your desire is to build several blogs and onepagers with great usability for the editor it could be very efficient to build a good selection of base packages/plugins which you can then use to build more sites much faster.
Many agencies which I have talked to or helped as consultant are doing this.
So I would say you either build a large site in which the learning cost of Neos is negligible or you build many sites to distribute the cost.If you already do React its cool as you can also extend the backend. Initially its also some learning effort, but then you can also implement unique solutions for the customers that perfectly fit into Neos and the customers will often assume Neos is just like that.Juzo.com seems to be straightforward. Several page types and some teasers, sliders and references. Looks like a page I would also happily do with Neos. Do you know who built it? Then you could just get some pointers from them.
I cannot give good estimates just from an URL.Feel free to ask more questions, we are always happy to discuss the Pros and Cons of Neos and other systems.
Implementation, Installation and Configuration
An important first step in choosing a CMS is looking into its requirements. Without a matching hosting environment and the possibility to connect other services a CMS might be not be able to fit a projects needs.
|License||GNU GPLv2+||GNU GPLv3+|
|Supported Webserver||Apache & Nginx||Apache & Nginx are recommended, others will work as well|
|Supported Databases||MySQL, MariaDB||MySQL, MariaDB, PostgreSQL|
|Scripting Language||PHP >= 7.3.0||PHP >= 7.1.0|
|Template Language||PHP, others through extensions||Fluid, Fusion AFX, others through extensions|
|Extensions und Add-ons||✔||✔ via Composer. See our extension listing for compatible releases|
|Reporting-Functionality (e.g. Data-Mining)||only with extension||Google Analytics, Matomo and others through extensions|
|APIs||only with extension||See "Powerful Interfaces": https://www.neos.io/features/feature-list.html|
|Integration of custom scripts||✔||✔|
|Consideration of current web standards||✔||✔|
„I recommend Neos when you want to build a site that you have to maintain for many years. Upgrades work smoothly, security updates are available, it offers great extensibility and there is an awesome community.“
When more than one editor works in a system it's often necessary to define roles and workflows to make sure only the content goes live that should go live.
|Inheritance of user rights||✔||✔|
|Restriction of user rights||✔||✔|
|Multi-stage release control||✔||✔|
Handling and Content Creation
The editing is the most important part of a CMS. Without editing there is not content to manage. That's why a CMS should make it easy to add and manage content including text and other media types.
|WYSIWYG – Editor||✔||✔ you actually can work in your frontend layout|
|Multimedia-Elements (Videos, Audio or others)||only with extensions||✔|
|Multiple languages||only with extensions||✔ including any number of content dimensions|
|Search||✔||✔ (other search engines like ElasticSearch via extensions)|
Search Engine Optimization (SEO) and Responsive Design
SEO is an integral part of a websites success. A CMS should make it easy for editors to analyse their content and optimise it quickly.
|Human readable URLs||✔||✔|
|Manual modification of title, description, canonical and other fields||✔||✔|
|Responsive web design possible||✔||✔|
|OpenGraph and Twittercard definitions||only with extensions||✔|
|Schema.org microdata (JSON-LD)||only with extensions||✔|
|Redirect management||only with extensions||✔|
|Custom error pages||only with extensions||✔|
SEO extension highlights from our community
The Neos community often comes up with new ways to increase your websites success. Here you can find some of the latest highlights:
Security and Service
TODO: Some text & video tutorial maybe?
„Neos projects have a low overall lifetime cost when you keep it up-to-date.“