May 5th 2017 naw.info FLOW3 Blog

Nützliche Helferlein für jeden TYPO3-Anwender

In diesem Monat wird es mal ganz kurz & praktisch: Ich habe unser „Bitmotion Team Content“ gebeten, mir die solche TYPO3-Kniffe zu nennen, die sehr hilfreich, aber kaum bekannt sind.

Hier kommen nun drei solche nützlichen Helferlein.

Alle diese Werkzeuge gibt es in TYPO3 schon sehr lange; die Abbildungen beziehen sich jeweils auf die aktuelle Version TYPO3 Version 8 LTS.


1. Effiziente Massenarbeit durch Assistenten

Als erstes wollen wir uns einmal das Modul mit dem unscheinbaren Namen „Funktionen“ anschauen. In diesem versteckt sich eine Sammlung von Assistenten („Wizards“), die je nach Aufgabenstellung enorm viele Klicks sparen können.

Für das Funktionen-Modul ist immer zunächst die gewünschte Seite auszuwählen, auf der der Assistent aktiv werden soll. Der klassische Anwendungsfall ist das Anlegen vieler neuer Seiten (siehe Screenshot), aber je nach installierten Erweiterungen kann es hier verschiedenste weitere Möglichkeiten geben.

Jeder Assistent kann auch Optionen mitbringen, hier etwa finden sich

  • Neue Seiten nach existierenden Unterseiten anlegen
  • Neue Seiten verbergen
  • Neue Seiten in Menüs verbergen

Pro-Tipp: Bei der Planung eines eigenen Erweiterungsmoduls sollte immer auch überdacht werden, ob „Massenaufgaben“ anfallen und auf welche Weise diese unterstützt werden können. Vielleicht ist ja ein eigener Assistent der Königsweg!


2. Suchen und Finden als Redakteur

Noch viel mehr unterschätzt ist die Volltextsuche im TYPO3-Backend – wer diese nicht nutzt, ist selbst Schuld!

Der einfachste Einstieg ist rechts oben über das Suchfeld mit Lupensymbol. Die Treffer werden „live“ eingeblendet. Aufgepasst – hier gibt es nun zwei Möglichkeiten:
A) Direkt auf den Treffer klicken = diesen öffnen,
B) Auf „Alle anzeigen“ klicken = Trefferliste öffnen.

Die Trefferliste (B) kann übrigens mehr Treffer enthalten als die Live-Vorschau (A).

Oberhalb der Trefferliste (B) hat man übrigens eine etwas erweiterte Sucheingabe. Diese kann man auch jederzeit direkt öffnen, indem man eine Seite auswählt und im Bearbeitungsfenster auf das Lupensymbol klickt:

Neben der Volltextsuche gibt es übrigens noch eine weitere – nämlich die „Filter“-Funktion über Seiten: Klickt man auf das Filter-Symbol, so kann man anfangen, den gesuchten Seitentitel einzugeben, und der Seitenbaum reduziert sich auf die passenden Treffer.

Pro-Tipp: Diese Suche funktioniert auch mit Eingabe der Seiten-ID!


3. Bookmarks machen das Leben leichter

Für alle, die einen verzweigten Seitenbaum zu verwalten haben, dabei aber häufig an dieselben Stellen navigieren müssen, hält TYPO3 Lesezeichen („Bookmarks“) bereit.

Dies ist nicht zu verwechseln mit den üblichen Browser-Bookmarks – denn hier haben Sie die Möglichkeit, gezielt einzelnen Dinge im Backend zu markieren, neben Seiten z.B. auch Systemordner (etwa für News-Artikel) und sogar einzelne Inhaltselemente.

Per Stern-Symbol lässt sich jedes Element zur Lesezeichenliste hinzufügen:

…und abrufen lässt sich die ganze Liste ebenfalls durch das Sternsymbol, diesmal das am oberen Rand des TYPO3-Backends:

Wie unschwer zu erkennen, erfolgt hier auch die Lesezeichen-Verwaltung – Bookmarks können nicht nur gelöscht, sondern auch umbenannt werden. In der Praxis ist dies vor allem bei Lesezeichen einzelner Inhaltselemente sinnvoll – was aber per se der seltenere Anwendungsfall ist.


Fazit

Allen drei beschriebenen Tipps ist gemeinsam: Es geht hier nicht um spektakuläre Killer-Features, sondern um nützliche, aber wenig bekannte Hilfen für das echte Leben. Ich persönlich würde in der täglichen Arbeit auf nichts davon verzichten wollen!

Read full article

Feb 14th 2017 news.typo3.org: FLOW3

TYPO3 v8.6 released

What's new?

New image manipulation wizard

Image handling has been a strength of TYPO3 ever since. Next to integrator related features, version 7 brought a basic image manipulation wizard to the backend, allowing editors to crop images per usage.

This feature has been heavily extended in v8.6: Most importantly, the image manipulation wizard now allows multiple crop variants for a single image. This allows editors to show different image areas according to the display size in the frontend.

Editors can also select a focus area to provide a hint which area in the image is the most important and should always be visible.

Last but not least integrators can mark cover-areas which give editors a visual indication which areas of the images might be covered by other elements of the website.

This feature was sponsored by SYZYGY Deutschland GmbH.

Flexible Menu-based content elements

A lot of work has been put into “fluid_styled_content” and “css_styled_content”, the basis for rendering content of a web page. As a main goal, the two extensions are now much better aligned and reduce headaches for integrators if dealing with the two.

As a nice side effect, this revamp comes with a couple of visible UX improvements for editors when dealing with content elements: The “menu” elements like “List of pages” and “List of sections” are now true content elements and can be selected in the new element wizard directly without another step in between.

Improved link element and validation

To further improve the editing experience of forms in the backend a couple of great usability improvements were integrated: Link handling got a better preview that includes improvements like showing the page path instead of a cryptic internal link. Additionally, form validation errors are now displayed in the top right corner of the backend, allowing editors to directly jump to invalid fields.

The link dialog gained features to make it extensible, providing the ability to create links to all kinds of records. This functionality has previously been provided by the extension “linkhandler”. 

Language synchronization feature

The steady refactoring of crucial parts of the code base like the data, form and language handling allows to add new custom features easily on top of TYPO3. A new wizard has been implemented allowing translators to select if a single field of a localized record has a dedicated value or if it should inherit the value of its language parent. The data handling within the core ensures the field content is copied to the translated record in case of changes to the parent record.

Improved scheduler module

Multiple features were added to the scheduler, the task runner of TYPO3. It’s now possible to have fine grained control of tasks and task groups. Single and multiple tasks can now be scheduled to be executed on next cron run and the user interface for handling long lists of tasks has been improved.

Fluid Styled Content & CSS Styled Content refactoring

Innovation is as important to us as to protect your investment. With TYPO3 Fluid we introduced a new template language a couple of years for a simple reason: To reduce the cost of creating websites for Frontend developers. More intuitive and easy to maintain predefined templates enable developers to speed up integrations, that are more reliable and flexible than ever before.

CSS Styled Content (CSC) has been the preferred template rendering engine for TYPO3 for a long time, and is part of TYPO3 since version 4.0, dating back to 2006. CSC is extremely flexible but also hard to learn and understand even for highly trained TYPO3 integrators. With the release of TYPO3 CMS 7.6 we fully embraced TYPO3 Fluid also for the rendering of content elements.

Fluid Styled Content (FSC) was introduced as successor of CSC but the feature set diverged from the beginning. The lack of flexibility and incomplete feature set in comparison to CSC made it hard to migrate existing instances that have embraced all features and the enormous flexibility before.

With the release of TYPO3 8.6 we are now making migrations even easier and provide new possibilities for more cost-efficient integrations. CSC is now fully compatible with FSC and shares the same capabilities to make a transition as easy as possible. To focus even more on the development of FSC in the next major version of TYPO3, CSC is now deprecated and in maintenance mode.

For compatibility, CSC is now supporting “Text and Media” that was previously exclusive to FSC. On top of that, FSC has learned some tricks from CSC. Now Fluid Styled Content has support for all content elements prior existing only in CSC, this includes "Text", "Text and Images" and "Images". Also for example „Frames", "Space before" and "Space after" have been integrated and fine tuned for better maintainability and understandability for Editors and Integrators. We cannot wait to see what you are creating with these new options.

Further changes

As usual, we have a lot of small but nice changes in TYPO3:

The previously introduced Form Framework in 8.5, originally derived from the Flow Framework of Sebastian Kurfürst of the Neos project, has some better integrations for “Finishers” and optimized templates to be used out-of-the-box.

The command-line handling of the TYPO3 Core has been optimized, making it easier for TYPO3 to run without creating a Backend user before.

The newly introduced CKEditor Rich Text Editor is now configurable through Yaml-based configuration presets, allowing to re-use configurations in multiple installations.

For a full list of changes, see our documentation for more information: https://docs.typo3.org/typo3cms/extensions/core/8-dev/Changelog/8.6/Index.html 

Download TYPO3 now

TYPO3 v8.6 is available on our download page or via composer (see composer.typo3.org). The minimum PHP version required to run TYPO3 v8 is PHP 7.0, so make sure your system is equipped with the proper PHP version.

What's next?

The final v8 release, which will be labelled as TYPO3 v8 LTS will be released on April 4th, 2017.

From now on, the team will concentrate on bug fixing, documentation and finishing a couple of loose ends. The goal is to release a first TYPO3 v8 LTS version as stable as possible, so administrators, integrators, developers and editors can rely on it as a stable product right from the beginning.

To achieve that, we need as much testing and feedback as possible of v8.6 now. Please participate in this process, upgrade your instances to v8.6 and help find and fix issues not tackled yet. Helping now will directly safe time and money when it comes to the roll out of TYPO3 v8 LTS to the huge user base.

Read full article

Apr 26th 2016 TYPO3 Blogger - FLOW3

Recap of Inspiring Conference 2016

inspiringconference2016

tl;dr

The 5th edition of the Inspiring Conference was the first edition after the split of the Neos Project from TYPO3 community last year and again a great and well organized conference with a good balance of technical talks, best practices and case studies. The Neos community has proven to be still very enthusiastic & really dedicated. In the last 12 months the Neos team has made it’s way into independence with great success.
But despite the great number of product visions the Neos project still lacks a resilient roadmap and timetable for the future and efforts to onboard new integrators to get a broader user base.
The Neos CMS Award could have been a great showcase but unfortunately wasted it’s possibilities due to the poorly chosen presentation environment.

Note: I’ve linked all currently available slides and will update this article when more links become available.

Keynote – Inspiringnote

The conference started with an Inspiringnote by Stefan Willkommer, CEO of the host company TechDivision. Being an experienced mountaineer he compared Neos with his ice axe, the all-in-one tool which is most important for him when climbing in the ice.

Afterwards Robert Lemke talked about the Past, Present and Future of Neos. Last year was marked by the split from the TYPO3 project, the build of an own infrastructure, the move to GitHub and the efforts to create a funding platform to attract new sponsors. A lot of new releases of Flow and Neos have been made, particularly noteworthy is the release of Neos 2.0 and 2.1.

The Neos team is proud that 1und1, a big german hosting provider, uses Neos CMS for managing content of their very own website. And Volkswagen created the After Sales Fleet Tool with Neos. Flow is used for example by DE-CIX and t3n.

Currently the Neos team works hard on establishing the new brand together with a completely new website and a brand-new package repository. Furthermore the launch of an own legal entity like a Neos Foundation, most probably as a community interest company (CIC) is on the agenda.

On the technical side, a rewrite of the Neos user interface with React is in the making. In the future Neos will receive quarterly releases. Flow will continue developing as a standalone product.

For a glimpse into the future of Neos Robert presented the vision of Neos as a content hub and a decoupled Neos to support a headless approach. Regarding new features, the Neos team is heavily dependent on monetary sponsoring.

Neos Product Vision

[Slides] In their talk, Christopher Hlubek and Tobias Gruber first pointed out that Neos was always about User Experience for both, developers and editors. Then they looked back, what Neos already has archived and what topics are currently important to the CMS business like Static Site Generators, Content APIs, a lot of APIs in general, Multi Channel, Content Integrations and Content Streams.
The target market for Neos are still ambitious web content project of all sizes. The vision hasn’t changed and UX still matters. For the future, Neos wants to refactor the UI with React and improve on inline editing, the content repository and content dimensions. The challenges Neos would like to take on are structured editing (e.g. bulk editing), CQRS and event sourcing, a content API and to decouple the components more.
The Flow framework should get improved DDD concepts and CQRS & event sourcing. It will stay independent and a part of the Neos project.
A clear roadmap and timeline for both projects is missing nevertheless.

Neos CMS Award

On the evening of the first conference day, the Neos CMS Award took place for the first time to award the best websites made with Flow and Neos:

Neos CMS Gold Award
H-Hotels – ‪‎Sitegeist

Neos CMS Silber Award
Explorer Fernreisen – ‎mindscreen / HiMedia‬

Neos CMS Bronze Award
EIZO – ‪Dotpulse‬

Excellence Award
Corporate Website – ‪‎Gesagt-Getan‬

Excellence Award
Core Kites – ‪networkteam‬

Excellence Award
günderberater.de – ‪Creativestyle‬

Unfortunately the event and the prize winners didn’t get the attention they deserved. The location and scope of the event were unsuitable. I would have wished for a much better presentation of the projects, some screenshots and more information about why they were chosen as winners.

Hacking Neos

[Slides] Sebastian Kurfürst and Christian Müller gave an overview about all the possibilities for planned and unplanned extension points in Flow and Neos.

Why monolith? Go headless! Using Neos as content API provider

[Slides] Dimitri Pisarev and Wilhelm Behncke presented multiple ways to decouple the website, application or any other consumer from the CMS.

Automation and External service Integration in Neos

[Slides] Dominique Feyer explained how to integrate external services in Neos and Flow and what challenges these news dependencies create regarding downtimes and budgets. His hints are very useful for any kind of web project.

Tasty Neos Recipes for every day

[Slides] Sebastian Helzle picked up on the talk of Aske Ertmann from last year and pointed out that the majority of the recipes from last year are still valid. Afterwards he presented a bunch of new useful recipes.

Long-Pager with Neos – so simple even your clients can do it

[Slides] Jonathan Uhlmann showed an approach how to create a long-pager and handle page sections, links, SEO and what the benefit of his approach are.

Neos Bloopers

[Slides] In his recap Christian Müller outlined a lot of stories about quotes and failed development attempts out of the history of the Flow and Neos project.

The Neos Brand

[Slides] Florian Heinze & Robert Lemke presented the long awaited new logo for Neos and described the process that lead to the new brand guide. At the end of the talk, they officially launched the new version of the Neos website.

Designing Content Types

Karsten Dambekalns described how a content-driven approach to building a website can be put into practice by creating a content strategy first and then implement it in Neos.

Emerging best practices about TypoScript / Content Rendering

[Slides] Sebastian Kurfürst described based of his experience in several projects how to structure TypoScript and to get the most out of the content cache.

Lightning Talks

This type of talk was introduced this year and gave seven speakers the possibility to quickly present a topic in not more than five minutes. This new talk concept was well received by the audience and will be continued next year.

Case Study: architectes.ch

[Slides] Dominique Feyer impressed with his show case about the website architectes.ch that contains more than 2000 reports, 12000 enterprises profiles, 30000 pictures and more than 12 years of archives. The main challenge was the clearing up of the content and then migrating it to Neos.

Pac-Man – Best practices for building Neos and Flow packages

[Slides] Florian Weiss & Dimitri Pisarev presented their approach to build Neos and Flow packages. There is no way to create the perfect package, but here are a lot of possibilities to optimize them.

One more thing

As established last year the „One more thing“ session is a panel discussion about ideas on the Neos team. This year Robert Lemke, Sebastian Kurfürst, Bastian Waidelich and Christopher Hlubek discussed on stage about CQRS & Event-Sourcing.

Der Beitrag Recap of Inspiring Conference 2016 erschien zuerst auf TYPO3 Blogger.

Read full article

Mar 13th 2016 news.typo3.org: FLOW3

Report on codesprint Karlsruhe 3.3-6.3.16

Some TYPO3 Core Developers and a whole bunch of interested contributors met for four days in Karlsruhe at Flagbit to pave the path for the first release of TYPO3 v8.

In total, 21 people managed to merge round about 80 patches to master, not counting bug fixes and improvements applied to the stable branches 7.6 and 6.2. With this amount of activity, we pressed the number of open and pending patches well below 200!

The focus was to improve the backend layout towards a more consistent and intuitive look and feel. Some patches in this regard have been merged, but more energy was put into peripheral aspects. The introduction package and the dependent bootstrap package are now ready for the v8.0 release. Unfortunately, it turned out realurl is not ready for this early sprint release. In order to ship a working introduction package anyway, realurl as a dependency has thus been dropped for the time being.

The "form" extension got quite some love with TYPO3 CMS version 7 already, especially from the great people at Tritum. Three of them joined us in Karlsruhe to further improve this part of TYPO3. As a remarkable milestone it should be mentioned that editors can now use predefined forms registered by an integrator. The form wizard is now directly integrated within the editing view and no standalone component any longer to further improve the editing experience.These features will be part of TYPO3 v8.

Another big chunk of work is worth mentioning: Since version 6.0, a continuing effort provides automated tests for the Core, automatically executed on every patch that is merged by the service of Travis CI. It started with unit tests in version 6.0, with 6.2 functional tests were introduced. With v8 we will see acceptance tests based on codeception and the selenium server entering the stage. The environment is ready and a small group of contributors is busy to provide tests and build up best practices for all of us to use and learn from. This new test suite will verify no new patches destroy the functionality of the backend on a rather high level.

Naturally, when passionate people gather, a lot of discussion arises. This sprint was no execption. Some highly technical and architectural decision have been tackled and decided upon. It is a pleasure on its own to watch our lead architects taking over the whiteboard and engage in heated discussion. 

The majority of sprint participants engaged into what we call casual patch handling. This means we go through the open reviews and pick everything that seems halfway ready. Then, for each of those issues, we strive to move it forward until it is ready to be merged. During this process a lot of new issues may turn up and are fixed on the go, too. This is the kind of work that keeps a group of devs busy at their laptops for 12 hours straight. It is the Flow, this visible process, the feeling of success. In average, we started coding at 10am and generally did not quit before 11pm. Meanwhile our hoster flagbit didn't let us starve. It has been a pleasure to spend those days in Karlsruhe.

After everybody is back home now, the stablisation phase for v8 started. Expect the release two weeks later, if no blockers turn up. In case you are interested in helping out, testing and reporting bugs on the first sprint release of v8, check out the master branch and test it to its limits. This sprint release will be stable and usable in production (if you feel lucky) and will be supported until the release of v8.1.

TYPO3 v8 - miles ahead.

Read full article

Jan 18th 2016 TYPO3 Blogger - FLOW3

Programm für die Inspiring Conference 2016 veröffentlicht

Inspiring Conference-LogoVom 21. – 23. April findet wieder die Inspiring Conference in Kolbermoor bei München statt. Dieses Jahr gibt es einen Workshop- und zwei Konferenztage. Wie schon in früheren Jahren darf man sich auf spannende Vorträge, eine tolle Location und spitzen Catering freuen. Außerdem findet diese Jahr erstmals mit dem Neos CMS Award eine Prämierung der besten Neos Projekte statt!

Heute wurde das Programm für die Konferenz veröffentlicht:

Ein-Tages-Workshops – 21.04.2016

  • Neos Introduction (Christian Müller)
  • Extending Neos and Flow with each other (Karsten Dambekalns)
  • Neos Advanced (Christopher Hlubek)

Konferenztag – 22.04.2016

  • Inspiringnote (Robert Lemke & Stefan Willkommer)
  • Hacking Neos (Sebastian Kurfürst & Christian Müller)
  • Why monolith? Go headless! Using Neos as content API provider (Rens Admiraal & Dimitri Pisarev)
  • Automation and External service Integration in Neos (Dominique Feyer)
  • Tasty Neos Recipes for every Day (Sebastian Helzle)
  • Long-Pager with Neos – so simple even your clients can do it (Jonathan Uhlmann)
  • Neos Bloopers (Christian Müller)
  • The Neos Brand (Florian Heinze & Robert Lemke)

2. Konferenztag – 23.04.2016

  • Neos Product Vision (Christopher Hlubek & Tobias Gruber)
  • Neos Rights Management (Karsten Dambekalns)
  • Emerging best practices about TypoScript / Content Rendering (Sebastian Kurfürst)
  • Lightning Talks (tbd.)
  • Case Study: architectes.ch (Dominique Feyer)
  • Pac-Man – best practices for building Neos and Flow packages (Florian Weiss & Dimitri Pisarev)
  • One more thing (Robert Lemke)

Der Ticketverkauf hat bereits begonnen!

Der Beitrag Programm für die Inspiring Conference 2016 veröffentlicht erschien zuerst auf TYPO3 Blogger.

Read full article

Jun 16th 2015 news.typo3.org: FLOW3

Announcing TYPO3 CMS 7.3 - More Stability, More Control

Since the release of TYPO3 CMS 7.2 back in April, the team focussed on certain topics under the hood to make the code base simpler and easier to maintain, while providing new standards for setting up new projects made with TYPO3. Read more about the previous releases here. Below you find more in-depth of the changes:

Improved Performance and Stability

Package Manager

The base logic for handling installed extensions and composer packages was backported originally from TYPO3 Flow and used since version 6.2, however most of the logic was never used in the TYPO3 CMS environment. This area was fully cleaned up and slimmed down, requiring less complicated code and less server memory in every Frontend and Backend request, but also act as a more robust solution than ever before.

Composer Class Loader

Loading PHP classes from the filesystem was originally done by a custom functionality introduced in TYPO3 6.2. Earlier this year, the standard functionality from Composer was integrated, but the TYPO3 functionality still acted as fallback for installations not set up through the command line with composer. This has now been streamlined and the “old” class loading functionality was migrated and unified to be using composer, which is only triggered on installation of an extension and is cached separately.

Templating Engine Fluid

Lots of standard view helpers of the rendering engine Fluid were changed to improve performance. This has a positive effect in the backend and leads to significant performance improvements in Extbase extensions. This is a gift to users of the system and developers at the same time since all changes are fully transparent and need no code change in extensions that use Fluid - rendering is just quicker out of the box. In general, working inside the TYPO3 backend feels faster.

More Control

Backend forms

Managing structured content is one of the main goals of TYPO3. Every editor knows the Page module and the List module to access and manipulate content. The main form-based editing was modernized visually while main underlying code structure is years old without being touched on a structural level.

For 7.3, a large work package by Christian Kuhn in the past months has seen first changes which are now part of TYPO3. This mainly affects extension developers who are introducing their own database fields editable by the TYPO3 Backend. Extension developers can now set up and modify the fields to be displayed way easier in their extensions. For more details, see the Documentation part of the new API.

More flexible Fluid templates

Fluid templates can be used for page renderings on a website, and for any content element - triggered by TypoScript and known to integrators. So-called “Data Processors” can now be used to modify any data that Fluid should handle. Read more about this feature in-depth in the documentation.

Even More

Inline Editing in the Page Module

Backend Inline Editing

The page title can now be edited inline in the Page module and the List module - a first glimpse of more to come in this area.

Command Line Improvements

The widely-acknowledged Symfony Console component is now part of the Command Line Controller from Extbase, allowing more streamlined and flexible output. This is a first step into streamlining the command-line based handling of TYPO3.

Backend Login API

The Backend Login has been changed visually in TYPO3 CMS 7.2, but now the underlying API has been modified to couple external login systems like OpenID in a more flexible way.

In-Depth Material & Download

The full list of changes is perfectly summarized in our What's new slides. The new version can be downloaded on the Download page or via get.typo3.org. Also see the Wiki page for the technical details when upgrading.

Outlook

The team is already working on TYPO3 CMS 7.4, which will finally see the default Content Element Rendering completely based on Fluid, and an even better experience in the TYPO3 Backend Interface. The next release is planned for August 4th, 2015, with a final LTS version to be released in fall 2015.

Read full article

May 18th 2015 news.typo3.org: FLOW3

TYPO3 project focuses on TYPO3 CMS, Neos to start its own community

The TYPO3 Association and the Neos team have begun negotiations about separating the Neos project from the TYPO3 Association. Work on Neos and its underlying PHP framework Flow started in 2006, originally intended as the successor of TYPO3 CMS. It has been continuously developed since then and is attracting a growing number of users and contributors.

Knowledge gained in the process led to understanding that TYPO3 CMS and Neos are conceptually distinct products. Honoring this diversity, the TYPO3 Association, TYPO3 team and the Neos team have come to believe that separating the project on an organizational level will help the Neos project to be able to focus on its own product strategy and an infrastructure that will be dedicated to its own needs and opportunities. 

Transitioning Neos into its own technical and legal infrastructure is planned as a cooperative process to avoid friction and waste of resources. The TYPO3 team and the Neos team believe that both communities will continue in areas of shared technology and through friendships we have developed over the years.

The TYPO3 Association and the Neos team are currently discussing the details for the transition period. As the TYPO3 Association wants to further develop into a more democratic and transparent organization, it will be asking its members soon to vote on how much support the Association should give the Neos Team in the transition period and beyond.

We are confident that the separation will strengthen both Neos and TYPO3 and are looking forward to seeing each of the communities prosper.

Neos-Team, TYPO3-Team & TYPO3 Association

Read full article