Issue Epic Closed

#107628Rethink wording and arrangement of modules and menu

Benni Mack 10/08/25, 14:56 updated 04/21/26, 11:28

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

Subtasks 26

Files 2

History 46

Show 21 earlier messages
  1. Garvin Hicking commented <span data-processor="relativetime" data-value="2025-10-08T15:26:14+00:00" > 10/08/25, 15:26 </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.

  2. 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
  3. 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?

  4. 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 :)

  5. 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.

  6. 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!

  7. 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.

  8. 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?

  9. 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)