I don’t have a direct question about a TYPO3 topic. Rather I want to share the input that was created during the TYPO3Camp Mitteldeutschland (#t3cmd). Moderators of the session were Alexander Degelmann and me. There were about 40 participants in the room. For 45 minutes we collected the following aspects in a solution-oriented and unexcited way. We categorized the requirements by backend (BE), frontend (FE) and business intelligence (BI).
We also collected quotes from the community. These can help us to grasp the current situation and viewpoint of the participants.
I would like to follow up on the topic and discuss it with the contributors. I would like to publish a post on this to communicate the point of view of TYPO3 to the people. Also, I would like to learn if there are other ways to incorporate community feedback into the roadmap. Optimally, there are already efforts, forge issues, code, or initiatives on the topics. I would be happy to mediate here.
Enough babbling, here are the collected requirements:
- Preview of content elements/ records without publishing: as an editor I would like to be able to view a corresponding element in the frontend without publishing it. This should work without workspaces. This should be possible for a specific element. The AdminPanel is not flexible enough. I can’t preview only one specific element. If there are many hidden elements on a page, it is confusing.
- Workspaces: as an editor I want to be able to use stable (i.e. free of bugs) workspaces. Workspaces are very important. Many participants in the room said they want to use workspaces and it is a brilliant enterprise feature. Workspaces are not sufficiently stable.
- Translation UI: as an editor I want to be able to translate all elements of my website using a UI.
- Workspaces for Translation UI: as an editor I would like to be able to put the elements translated with the Translation UI through an approval process as well. Currently workspaces and the l10n manager do not work together.
- Deepl Integration: as an editor I would like to use a Deepl integration in the backend to translate content.
- Save forms: as editor I want to make sure that submitted forms are saved in the backend.
- Import: as an integrator/ developer I want to be able to import content from other sources (ERP, CRM, other TYPO3 instances) easily, quickly and reliably. A UI (like for example with PIMCore) accompanies me in this process. An API is also available. This paves the way to DXP.
- uuid: as a developer I want to work with uuids. This makes imports and migrations so much easier.
- Records: as an editor I do not understand the “List” module. I don’t want to switch to another module for editing records.
- Headless: as a developer I want to use headless functions out of the box. This paves the way to DXP.
- Fast modeling: as a developer I don’t want to define my model in several places (TCA, get(), set(), SQL). TYPO3 should do as much work as possible for me. But I want to be able to intervene if I need different definitions e.g. concerning SQL data types.
- Windows 98: as an editor I expect a modern look and feel. It should not feel like Windows 98. 50% of the participants in the room feel that way. Pipedrive and the Google Apps are a good benchmark.
- Responsiveness: as an editor I expect a fast interface. It should feel like an app and do few/ no reloads.
- Reduced interface: as an editor I want a very reduced interface/ a light version. This is done for example by Jetbrains with the YouTrack Light Interface. The interface could be rebuilt from scratch and be a modern, responsive alternative to the current interface.
- Process modeling: as an integrator and developer I would like to be able to model processes via a UI. Similar to what PIMCore offers, for example. I would like to be able to connect various APIs. In this way, data should flow between numerous systems. This paves the way to the DXP.
- We have lost focus on the USPs of TYPO3. The USPs are not sufficiently maintained; they are not stable enough.
- TYPO3 is one CMS of many. From the customers’ point of view, TYPO3 is absolutely replaceable.
- TYPO3 is no longer an enterprise CMS, but “only” a CMS.
- Our customers are willing to pay for “Enterprise”. Does there have to be a “Professional/ Enterprise” edition of TYPO3? Like Shopware and Magento do?
- Where does TYPO3 currently stand? What is it? A CMS? A WMS? A DXP?
- We want to evolve from CMS to DXP.
- The time of our developers is very limited. TYPO3 needs to offer more interfaces and be open so that modeling is easier and faster. Things have to happen fast. Our resources are tight.
- TYPO3 is not meant to be a solution for everything. It is clear that the core has to be open via appropriate APIs, but does not ship all of the desired functions directly.
- We advertise too little with the good things we’ve got.