#107628Rethink wording and arrangement of modules and menu
Description
Comparing TYPO3 with other Enterprise CMSes (sanity, AEM, Agility, Kentico, Kontent.ai, Affino, Hubspot, Contentful) we should rethink our module menu structure and naming. Here is my proposal:
Dashboard Content (was "Web") -> Layout (was "Page") -> Preview (was "View") -> Records (was: "List") -> Forms -> Publish (was "Workspaces") - in Workspaces only -> Recycler -> Status (was "Info", was "Indexing", was "Check Links") Media (was "File") -> Media (was "Filelist") -> Storages (new module) Sites (was Site Management) -> Setup (was Sites, was "Settings") -> Redirects (needs to work on per-site basis now, or "all") -> TypoScript System -> Users (was Backend Users) -> Permissions -> Scheduler -> Page TSconfig (?) -> Content Security Policy -> Integrations (merge Reactions + Webhook) -> Reports -> Log Administration -> Extensions -> Maintenance -> Settings -> Upgrade -> Environment -> Configuration (was in System before) Help User -> Profile Settings
We need Filter the page tree on specific items / pre-configuration per module
Reviews 13
- main 91896[TASK] Rename "List" module to "Records"
- main 91657[TASK] Display the module short description in the module menu
- main 91796[TASK] Add single submodule promotion
- main 91674[TASK] Rename Backend Users module to Users
- main 91795[TASK] Rename “Site Management” to “Sites” and submodule “Sites” to “Setup”
- main 91792[TASK] Rename “Page” module to “Layout”
- main 91585[WIP][TASK] Move module menu locations, adjust labels
- main 91631[TASK] Rename top level module "Admin Tools" to "Admin"
- main 91633[TASK] Reorder the modules in Admin
- main 91610[TASK] Update install tool module identifiers
- main 91555[WIP][TASK] Unify link management modules
- main 91126[FEATURE] Rename top-level module "file" to "media"
- main 91083[FEATURE] Rename top-level module "web" to "content"
Subtasks 26
- Task #104017Improve short description of some backend modules
- Task #107708Rename top level module "web" into "content"
- Task #107762Rename top-level module "file" to "assets"
- Epic #108048Rename second-level module "view" to "preview"
- Task #108094Update install tool module identifiers
- Task #108104Move module menu locations and positions and rename labels (combined)
- Task #108105Rename lowlevel module "Configuration" to better fit its purpose
- Task #108108Rename Admin Tools to Admin
- Task #108109Reorder the modules in Admin
- Task #108112Reorder the modules in Content
- Task #108115Display the module short description in the module menu
- Task #108117Move the Status (Former Info) module into EXT:backend
- Task #108118Rename top level "Site Management" into "Sites" and "Sites" into "Setup"
- Task #108120Rename "Admin" to "Administration"
- Task #108121Rename "Backend Users" module to "Users"
- Task #108122Rename "Web > Page" to "Content > Layout"
- Task #108123Rename Module "Workspaces" to "Publish"
- Feature #108124Introduce Media > Storages module
- Task #108142Introduce User / Group Permissions Migration Wizard for renamed modules
- Task #108224Rename "File list" module
- Task #108230Rename workspace module identifier and document changes
- Task #108233Rename "Page" to "Layout"
- Task #108235Add submodule promotion
- Task #108247Use real submodules for lowlevel's search
- Task #108328Rename "List" to "Records"
- Task #108354Apply module renamings to comments, readmes and rst files
Files 2
History 46
Show 21 earlier messages
-
Garvin Hicking changed description <span data-processor="relativetime" data-value="2025-10-08T15:22:58+00:00" > 10/08/25, 15:22 </span>
-
Garvin Hicking commented <span data-processor="relativetime" data-value="2025-10-08T15:26:14+00:00" > 10/08/25, 15:26 </span>
-
Jasmina Ließmann commented <span data-processor="relativetime" data-value="2025-10-08T20:58:18+00:00" > 10/08/25, 20:58 </span>
I support this proposal! Thank you.
Garvin Hicking wrote in #note-2:
> Except “Styles / Output Settings” – I suppose you mean either “Styles” or “Output Settings”.
>
> In this case I would probably suggest to use “Site Sets”? This freshly established term might be relatable, and we could precent “Site Set Settings” then. Otherwise I think “Style” is too narrow, and “Output Settings” sounds more like setting up Oage Types or JSON or Headless views or so.I am undecided about a the name ‘Styles / Output Settings’ or ‘Site Settings’ (under “Sites”). I would probably go with ‘Output Settings’ for now and change it again if necessary.
In everyday use, I often find myself mistakenly looking for entries under ‘System’ that are actually under ‘Admin (Tools)’ and vice versa.
I could also imagine the following items under ‘Admin’:- Content Security Policy (keep in “Admin”)
- Log
- Reports
-
Lina Wolf commented <span data-processor="relativetime" data-value="2025-10-09T04:54:30+00:00" > 10/09/25, 04:54 </span>
Nice work!
I personally would like to rename List – list of what? Maybe “Records” or “Table Records” would be more precise?
-
Riccardo De Contardi commented <span data-processor="relativetime" data-value="2025-10-09T09:35:45+00:00" > 10/09/25, 09:35 </span>
Times ago Marcin Sągol (credits to him) proposed
“List” >> “Record lists”
“Info” >> “Overview” (which I tend to prefer instead of “Status”)—-
Renaming “workspaces” >> “publish” seems good :)
-
Oliver Bartsch changed tracker
FeatureEpic <span data-processor="relativetime" data-value="2025-10-15T14:38:15+00:00" > 10/15/25, 14:38 </span> -
Oliver Bartsch changed subtask #107708 <span data-processor="relativetime" data-value="2025-10-15T14:38:52+00:00" > 10/15/25, 14:38 </span>
-
Oliver Bartsch changed subtask #107762 <span data-processor="relativetime" data-value="2025-10-17T13:25:38+00:00" > 10/17/25, 13:25 </span>
-
Marcin Sągol commented and changed attached TYPO3 Backend navigation concept.pdf <span data-processor="relativetime" data-value="2025-10-17T15:00:01+00:00" > 10/17/25, 15:00 </span>
Hi, yes I had and idea to re-arrange and re-word some the backend modules menu.
Here is an exported concept from Figma. -
Benni Mack commented <span data-processor="relativetime" data-value="2025-10-17T15:02:47+00:00" > 10/17/25, 15:02 </span>
Marcin Sągol wrote in #note-9:
> Hi, yes I had and idea to re-arrange and re-word some the backend modules menu.
> Here is an exported concept from Figma.Thanks marcin, now is the time to put all of these ideas into motion! Your input helps a lot!
-
Benni Mack commented and changed attached modules-proposal-v1.png <span data-processor="relativetime" data-value="2025-11-04T21:39:00+00:00" > 11/04/25, 21:39 </span>
This is now a first combined version, grouped by the common personas / personell we know from TYPO3 universe.
-
Garvin Hicking commented <span data-processor="relativetime" data-value="2025-11-05T18:33:06+00:00" > 11/05/25, 18:33 </span>
I think we might take this chance to cut off the “Page TSConfig” item. All other menu items are getting really clear and less “magical”, but “Page TSConfig” is not very welcoming to people new to our system.
Would maybe just “Page setup” work out? Could even be a submodule of “Setup” then. Or “Page behaviour”? “Page configuration”?
I know everyone dealing with “muscle memory” will search for “Page TSConfig”, so… I haven’t checked, but would it be possible to have a custom sitepackage that allows to rename our backend menu items to please those people that want a “Page TSConfig” menu item back?
-
Benni Mack commented <span data-processor="relativetime" data-value="2025-11-06T05:52:00+00:00" > 11/06/25, 05:52 </span>
Garvin Hicking wrote in #note-12:
> I think we might take this chance to cut off the “Page TSConfig” item. All other menu items are getting really clear and less “magical”, but “Page TSConfig” is not very welcoming to people new to our system.
>
> Would maybe just “Page setup” work out? Could even be a submodule of “Setup” then. Or “Page behaviour”? “Page configuration”?
>
> I know everyone dealing with “muscle memory” will search for “Page TSConfig”, so… I haven’t checked, but would it be possible to have a custom sitepackage that allows to rename our backend menu items to please those people that want a “Page TSConfig” menu item back?Will talk with Lolli about it today (will see him today in person)
-
Garvin Hicking changed subtask #108048 <span data-processor="relativetime" data-value="2025-11-11T13:31:08+00:00" > 11/11/25, 13:31 </span>
-
Oliver Bartsch changed subtask #108094 <span data-processor="relativetime" data-value="2025-11-13T10:15:37+00:00" > 11/13/25, 10:15 </span>
-
Garvin Hicking changed subtask #108104 <span data-processor="relativetime" data-value="2025-11-13T17:11:32+00:00" > 11/13/25, 17:11 </span>
-
Lina Wolf changed subtask #108105 <span data-processor="relativetime" data-value="2025-11-13T17:34:47+00:00" > 11/13/25, 17:34 </span>
-
Lina Wolf changed subtask #108108 <span data-processor="relativetime" data-value="2025-11-13T19:44:26+00:00" > 11/13/25, 19:44 </span>
-
Lina Wolf changed subtask #108109 <span data-processor="relativetime" data-value="2025-11-13T20:39:48+00:00" > 11/13/25, 20:39 </span>
-
Lina Wolf changed subtask #108112 <span data-processor="relativetime" data-value="2025-11-13T21:45:15+00:00" > 11/13/25, 21:45 </span>
-
Lina Wolf changed subtask #108115 <span data-processor="relativetime" data-value="2025-11-14T04:24:03+00:00" > 11/14/25, 04:24 </span>
-
Lina Wolf changed subtask #108116 <span data-processor="relativetime" data-value="2025-11-14T04:42:49+00:00" > 11/14/25, 04:42 </span>
-
Lina Wolf changed subtask #108117 <span data-processor="relativetime" data-value="2025-11-14T04:52:42+00:00" > 11/14/25, 04:52 </span>
-
Lina Wolf changed subtask #108118 <span data-processor="relativetime" data-value="2025-11-14T05:40:04+00:00" > 11/14/25, 05:40 </span>
-
Lina Wolf changed Related to #104017 <span data-processor="relativetime" data-value="2025-11-14T07:18:46+00:00" > 11/14/25, 07:18 </span>
-
Lina Wolf changed subtask #104017 <span data-processor="relativetime" data-value="2025-11-14T07:19:04+00:00" > 11/14/25, 07:19 </span>
-
Mathias Brodala changed subtask #108120 <span data-processor="relativetime" data-value="2025-11-14T08:16:20+00:00" > 11/14/25, 08:16 </span>
-
Lina Wolf changed subtask #108121 <span data-processor="relativetime" data-value="2025-11-14T10:12:05+00:00" > 11/14/25, 10:12 </span>
-
Lina Wolf changed subtask #108122 <span data-processor="relativetime" data-value="2025-11-14T10:16:41+00:00" > 11/14/25, 10:16 </span>
-
Lina Wolf changed subtask #108123 <span data-processor="relativetime" data-value="2025-11-14T10:18:58+00:00" > 11/14/25, 10:18 </span>
-
Lina Wolf changed description assigned to Lina Wolf <span data-processor="relativetime" data-value="2025-11-14T10:38:55+00:00" > 11/14/25, 10:38 </span>
-
Lina Wolf changed subtask #108124 <span data-processor="relativetime" data-value="2025-11-14T10:39:46+00:00" > 11/14/25, 10:39 </span>
-
Lina Wolf changed subtask #108142 <span data-processor="relativetime" data-value="2025-11-16T04:50:18+00:00" > 11/16/25, 04:50 </span>
-
Benni Mack changed subtask #108224 <span data-processor="relativetime" data-value="2025-11-20T18:32:37+00:00" > 11/20/25, 18:32 </span>
-
Oliver Bartsch changed subtask #108230 <span data-processor="relativetime" data-value="2025-11-20T21:31:32+00:00" > 11/20/25, 21:31 </span>
-
Oliver Bartsch changed subtask #108233 <span data-processor="relativetime" data-value="2025-11-20T22:36:51+00:00" > 11/20/25, 22:36 </span>
-
Oliver Bartsch changed subtask #108235 <span data-processor="relativetime" data-value="2025-11-20T23:48:59+00:00" > 11/20/25, 23:48 </span>
-
Georg Ringer changed status
NewIn Progress <span data-processor="relativetime" data-value="2025-11-21T04:58:21+00:00" > 11/21/25, 04:58 </span> -
Lina Wolf changed subtask #108247 <span data-processor="relativetime" data-value="2025-11-22T15:10:30+00:00" > 11/22/25, 15:10 </span>
-
Oliver Bartsch changed subtask #108328 <span data-processor="relativetime" data-value="2025-11-26T15:20:53+00:00" > 11/26/25, 15:20 </span>
-
Lina Wolf changed subtask #108354 <span data-processor="relativetime" data-value="2025-11-28T10:35:52+00:00" > 11/28/25, 10:35 </span>
-
Lina Wolf changed description <span data-processor="relativetime" data-value="2025-11-28T10:38:41+00:00" > 11/28/25, 10:38 </span>
-
Oliver Hader changed target version <span data-processor="relativetime" data-value="2026-01-23T12:29:51+00:00" > 01/23/26, 12:29 </span>
-
Benni Mack changed target version <span data-processor="relativetime" data-value="2026-03-31T09:05:27+00:00" > 03/31/26, 09:05 </span>
-
Benni Mack changed
subtask #108116<span data-processor="relativetime" data-value="2026-04-21T11:27:20+00:00" > 04/21/26, 11:27 </span> -
Benni Mack changed status
In ProgressClosed <span data-processor="relativetime" data-value="2026-04-21T11:28:22+00:00" > 04/21/26, 11:28 </span>
Nice. I personally like all of this!
Except “Styles / Output Settings” – I suppose you mean either “Styles” or “Output Settings”.
In this case I would probably suggest to use “Site Sets”? This freshly established term might be relatable, and we could precent “Site Set Settings” then. Otherwise I think “Style” is too narrow, and “Output Settings” sounds more like setting up Oage Types or JSON or Headless views or so.