📜 Post with us on Reddit
📝 Create a new article
🏭 Create a company page
🇬🇧 - in English
🇫🇷 - en Français (FR)
🇵🇹 - em Português (PT)
🇩🇪 - in Deutsch (DE)
🇯🇵 - 日本語で (JA)
Sponsored articles

You can edit almost every page by Creating an account. Otherwise, see the FAQ.

Neos (Content Management System)

From EverybodyWiki Bios & Wiki


Neos
Developer(s)Neos-Team & Contributors
Initial release2017
Stable release
5.0 / 2019-09-20
Repositorygithub.com/neos/
Written inPHP, SQL and JavaScript
Engine
    Operating systemCross-platform_software
    Available in10+ languages[1]
    List of languages
    English, German, Danish, Dutch, Finnish, French, Khmer, Latvian, Polish, Russian,
    TypeContent_management_system
    LicenseGPL
    Websitewww.neos.io

    Search Neos (Content Management System) on Amazon.

    Neos is an Open-Source CMS (Content Management System) and Content Application Platform based on Flow. Neos offers content management functions and combines them with other systems (e.g. Ecommerce platforms, Online shops, Data warehouses, etc.) to provide a comprehensive User Experience for editors, developers and users.

    History of Development[edit]

    In 2006, a project began with the goal of releasing the TYPO3 version 5.0, a complete, modernized new development of TYPO3. The project was started by core developer Robert Lemke and after a few months supported by Karsten Dambekalns. Since 2007 Lemke and Dambekalns have been working full-time on the further development.[2][3]

    The TYPO3 version 5.0 was later renamed to TYPO3 Phoenix. The project was originally intended as refactoring the core of the then existing TYPO3 version 4 and the introduction of new features and standards.[4] The overall goal: to create a future-proof basis for further TYPO3 versions after version 4.

    The core of the new version should be built completely according to modern MVC principles. It quickly became clear, however, that this new concept would require extensive changes, which would ultimately endanger the stability of TYPO3. Therefore, it was decided to completely separate the new version of TYPO3 from the old codebase, which was rooted in the beginnings of TYPO3 and was partly not object-oriented.[5]

    In addition to the new version of TYPO3, these efforts also resulted in the creation of the software framework TYPO3 Flow, which was published in June 2009 with the first Alpha version under the name FLOW3. TYPO3 Flow is from today's point of view the foundation of TYPO3 Neos.[6]

    At the beginning of October 2012, the developers of TYPO3 agreed to introduce a new naming concept for the TYPO3 versions and related projects. The 4.x version branch, previously simply called TYPO3, has now been renamed TYPO3 CMS. The completely new TYPO3 version is now called TYPO3 Neos. In addition, the framework FLOW3 is called TYPO3 Flow.

    The uniform designation made it possible to clearly name and order the historical development for the future. The name TYPO3 is clearly recognizable as an umbrella brand and serves as an orientation for all projects and versions of TYPO3.

    In October 2012 the TYPO3 Association published a first alpha version of TYPO3 Neos.[7] The final version 1.0 was released on December 10, 2013.

    The advantage of TYPO3 Neos is that the user can edit content in a "live" view of the website and not, as usual, a uniform interface for editing the content in the backend provided. Due to the structure of the framework, it is no longer possible to integrate plug-ins as content elements, as is the case with other TYPO3 systems, since the CMS extensions are inserted by code via the new "TYPO Script 2.0".

    TYPO3 Neos-Plugins are full TYPO3 Flow-Applications,[8] which are integrated as plugins. Pages and their contents are structured as a hierarchical tree (see Document Object Model). Content elements are easily configurable and extensible, so that in comparison to TYPO3 CMS for many applications no own plugins are necessary anymore, but the configuration of own content elements [9] is sufficient.

    TYPO3 Neos follows the approach of completely separating configuration and data. Data lands in the database, for the configuration Neos creates a TYPO3 Flow package of the type "Sites" for each appearance and stores the configuration in it. This allows the page configuration to be managed with version management software and easily reused, while other tools are used for the database. This circumstance led to confusion among early Neos interested parties because Neos had already reached a high functional level, but in the backend area, the majority of the functionality was not visible.

    In 2015 the TYPO3 Association and the Neos team announced that Neos will no longer be developed under the umbrella of the Association. Neos and TYPO3 CMS have matured into two different products, each with its own user base. This separation should also make a diversified product strategy possible for Neos; a migration of existing TYPO3 CMS projects, such as was planned in the past but never implemented, is no longer planned.[10]

    Since January 2017 Neos, with the release 3.0, has also been ported technically completely into its own PHP namespace. This completes the separation of Neos and TYPO3 CMS. The project has established its own infrastructure and community and is currently concentrating (as of March 2017) on the development of a new frontend editor based on React and on architectural concepts for the Neos Content Repository based on the EventSourcing pattern.[11]

    Major Versions[edit]

    Legend: Old version, no support Older version, still supported Current stable version Latest preview version Future release
    Package-Name Version Sub-
    version[12]     		Release General Improvements up to Security relevant Improvements up to Important Changes
    TYPO3 Neos 1.x Old version, no longer supported: 1.0 10th December 2013[13] Originally planned as TYPO3 version 5.0, now as a separate project under a new name. The system is given a fundamentally new architecture based on the specially developed TYPO3 Flow framework, whereby modern concepts (e.g. MVC) are taken into account throughout.
    Old version, no longer supported: 1.1.0 19th June 2014[14] Improvement of stability, improvement of performance through flexibilization and acceleration of the content cache, fundamentals for multidimensional content such as localization, internationalization, translations or variants.
    Old version, no longer supported: 1.2.0 10th December 2014[15] 1st April 2017 Backend support for multidimensional content, extended rights system.
    Neos 2.x Old version, no longer supported: 2.0 12th August 2015[16] 1st August 2017 First release as an independent project separate from TYPO3 development. Improved user management, cloud support for media assets, translated user interface, integration of Google Analytics and bug fixes.
    Old version, no longer supported: 2.1 22nd December 2015[17] 1st Dezember 2016 1st December 2017
    Old version, no longer supported: 2.2 4th May 2016[18] 1st April 2017 1st April 2018
    Old version, no longer supported: 2.3 (LTS) 22nd August 2016[19] 1st August 2018 1st August 2019 First LTS-Version.
    3.x Old version, no longer supported: 3.0 30th January 2017[20] 1st December 2017 1st December 2018 Complete separation from the TYPO3 PHP namespace; alpha version of the new React-Backd-UI.
    Older version, yet still supported: 3.3 (LTS) 20th December 2017[21] 1st December 2019 1st December 2020 Release of the revised ReactJS user interface
    4.x Older version, yet still supported: 4.0 26. April 2018[22] 1st December 2019 1st December 2019 React UI, Emojis!, External Asset Sources, FontAwesome update to 5.0
    Older version, yet still supported: 4.1 29. August 2018[23] 1st December 2019 1st December 2019 Neos UI improvements (CKEditor 5 integration, node tree presets, configurable keyboard shortcuts, and much more), performance improvements, PSR-7 compatibility
    Older version, yet still supported: 4.2 3. Dezember 2018[24] 1st December 2019 1st December 2019 SEO Package 2.1.0, Asset Management Enhancements, Improved Deployment Resilience, Font Awesome Update to Version 5.5, Fusion and AFX Enhancements
    Older version, yet still supported: 4.3 (LTS) 15. April 2019[25] April 2021 April 2022 Improved Asset Handling, Fusion Improvements, Eel Improvements, Neos UI 3.3, Neos Demo Package 5.0, SEO Package 3.0
    5.x Current stable version: 5.0 20th September 2019[26] April 2021 April 2022 Updated Neos UI 5.0, all-new Redirect Handler 3.0, full PSR-7 compatibility

    References[edit]

    1. ↑ "Neos translation statistics". CrowdIn.
    2. ↑ Lippert, Robert. "Robert Lemke im Interview zu FLOW3". Developer (in Deutsch). Retrieved 2019-10-15.
    3. ↑ typovision.de
    4. ↑ Robert Lemke (2011-06-03). "T3DD06 TYPO3 5.0 Brainstorming Results".
    5. ↑ Lippert, Robert. "Robert Lemke im Interview zu FLOW3". Developer (in Deutsch). Retrieved 2019-10-15.
    6. ↑ "Roadmap". typo3.org. Retrieved 2019-10-15.
    7. ↑ "Aus TYPO3 5.0 Phoenix wird „TYPO3 Neos" » t3n News". web.archive.org. 2012-10-07. Retrieved 2019-10-15.
    8. ↑ "Creating a TYPO3 Neos plugin". web.archive.org. 2014-01-19. Retrieved 2019-10-15.
    9. ↑ "Creating Custom Content Elements". web.archive.org. 2014-02-17. Retrieved 2019-10-15.
    10. ↑ "TYPO3 project focuses on TYPO3 CMS, Neos to start its own community". typo3.org. Retrieved 2019-10-15.
    11. ↑ "Neos 3.0 and Flow 4.0 Released". Neos CMS - Open Source Content Application Framework. 2017-01-30. Retrieved 2019-10-15.
    12. ↑ Neos Release Roadmap
    13. ↑ "TYPO3 Neos 1.0 released". Neos CMS - Open Source Content Application Framework. 2016-04-18. Retrieved 2019-10-15.
    14. ↑ "TYPO3 Neos 1.1 released". Neos CMS - Open Source Content Application Framework. 2016-04-18. Retrieved 2019-10-15.
    15. ↑ "TYPO3 Neos 1.2 released". Neos CMS - Open Source Content Application Framework. 2014-12-11. Retrieved 2019-10-15.
    16. ↑ "Neos 2.0 released". Neos CMS - Open Source Content Application Framework. 2015-08-12. Retrieved 2019-10-15.
    17. ↑ "Neos 2.1 released". Neos CMS - Open Source Content Application Framework. 2015-12-22. Retrieved 2019-10-15.
    18. ↑ "Neos 2.2 and Flow 3.2 released". Neos CMS - Open Source Content Application Framework. 2016-05-04. Retrieved 2019-10-15.
    19. ↑ "Neos 2.3 LTS and Flow 3.3 LTS released". Neos CMS - Open Source Content Application Framework. 2016-08-22. Retrieved 2019-10-15.
    20. ↑ "Neos 3.0 and Flow 4.0 Released". Neos CMS - Open Source Content Application Framework. 2017-01-30. Retrieved 2019-10-15.
    21. ↑ "Neos 3.3 LTS and Flow 4.3 LTS Released". Neos CMS - Open Source Content Application Framework. 2017-12-20. Retrieved 2019-10-15.
    22. ↑ "Neos 4.0 and Flow 5.0 released". Neos CMS - Open Source Content Application Framework. 2018-04-24. Retrieved 2019-10-15.
    23. ↑ "Neos 4.1 and Flow 5.1 released". Neos CMS - Open Source Content Application Framework. 2018-08-29. Retrieved 2019-10-15.
    24. ↑ "Neos 4.2 »Snowdrop« and Flow 5.2 released". Neos CMS - Open Source Content Application Framework. 2018-12-03. Retrieved 2019-10-15.
    25. ↑ "Neos 4.3 LTS »Gryphon« and Flow 5.3 LTS released". Neos CMS - Open Source Content Application Framework. 2019-04-15. Retrieved 2019-10-15.
    26. ↑ "Neos 5.0 »Jabberwock« and Flow 6.0 released". Neos CMS - Open Source Content Application Framework. 2019-09-20. Retrieved 2019-10-15.

    External links[edit]


    This article "Neos (Content Management System)" is from Wikipedia. The list of its authors can be seen in its historical and/or the page Edithistory:Neos (Content Management System). Articles copied from Draft Namespace on Wikipedia could be seen on the Draft Namespace of Wikipedia and not main one.


    Retrieved from "https://en.everybodywiki.com/index.php?title=Neos_(Content_Management_System)&oldid=2215643"
    License CC BY-SA 3.0
    Powered by MediaWiki
    Powered by Semantic MediaWiki