Neos (content management)

Neos

Original author(s)	Neos-Team und Contributors
Developer(s)	Neos-Team
Initial release	2013
Written in	PHP, SQL, JavaScript
Type	Content Management System
License	GPL
Website	https://neos.io

Neos is an Open-Source-Content-Application-Plattform based on the PHP Framework Neos Flow which is developed from the Neos-Team as well. By default Neos offers Content Management System functionality, but the flexible data model allows other use cases for instance as Headless CMS.

Compared to other CMS Neos focuses on usability and ease of use. Whenever possible the edited website is used as interface for the editing (Inline Editing). That way editors shall be enabled to focus on content instead of technology...^[1][2][3]

Contents can be managed in arbitrary dimensions like language, country, target-group etc. The content structure can be adjusted for each domain or project. Neos contains a media management module for files and images with categorization and filtering capabilities. External media sources can be connected via api to integrate Wikimedia, or other free or commercial libraries.^[4]

The content output is controlled by an integrated domain specific language called Fusion which is used to read content from the Content-Repository, create HTML-code and control caching. For HTML rendering Fusion can use the AFX syntax (derived from React JSX) or Fluid a template Engine used by TYPO3.

Neos uses Composer for package management and for installing extensions. In addition Neos supports many PSR Standards of the PHP Framework Interop Group.

Development and Community

The Neos project is open to anyone. Inside the project the Neos-Team is responsible for continuous maintenance and development ^[5]. Github is used as development platform^[6]. An important part of neos development are regular sprints where team members and contributors meet in person to work on Neos topics.^[2]

New versions are released quarterly. Neos uses Semantic-Versioning and thus breaking changes can only be released with a major version. Before new major versions a version with long term support (LTS) is released^[7].

Since 2017 the "Neos Conference" is held once a year^[8], where developers and users meet. In 2020 and 2021 the conference was held as an online event due to covid-19 limitations^[8]. In the years 2012 to 2016 the "Insipiring Conference" took place that which covered the same Neos and Flow topics and is nowadays seem as predecessor to the Neos Conference.

In 2017 the Neos-Foundation was founded as british CIC dedicated to promote the development of Neos and the Neos-Community^[9]

History and Origin

The Project started in 2006 and became traction in 2007 when Robert Lemke and Karsten Dambekalns began to work exclusively on what eventually became Neos^[10]. The original goal was to develop a completely modernized version 5.0 of TYPO3. TYPO3 5.0 was later renamed to "TYPO3 Phoenix" and then "TYPO3 Neos". Since the Neos and TYPO3 split up in 2015 the project is simply called Neos.

Originally being planned as a refactoring of the TYPO3 core to introduce modern MVC paradigms^[11] it soon became obvious that this would require changes that were not compatible with the existing codebase. So the decision was made to develop the new version of TYPO3 from scratch ^[10]

At first the Neos Flow PHP-Framework was developed as base for the CMS which was released in June 2009 as alpha-version named "FLOW3". Later this was renamed "TYPO3 Flow" and is today called "Neos Flow".

The first alpha-version of TYPO3 Neos was released in October 2012. The final Version 1.0 was released in December 2013.

In May 2015 the TYPO3 Association and the Neos-Team decided to go separate ways. Neos and TYPO3 CMS had became two distinct products with separate communities.^[12]

Important Versions

{{{2}}}

References

0.00 (0 votes)