Issue Feature Closed

#98265Favourites for content elements

Martina Wieser 09/06/22, 06:42 updated 11/13/26, 14:55

Description

Every time I create new content elements in Typo3, which is not part of the standard, an intermediate step has to be taken by clicking on a tab.
If you often work with Typo3, you know where to find something, but it takes time. Someone who rarely works with Typo3 has to click through completely before he finds what he is looking for.

So I had the idea that you could create “Favourites” as the first tab. Each editor should be able to select his or her favourite content elements in the settings, which are then displayed in the first position. Preferably even with a user-defined order.
This would make working with Typo3 even more user-friendly.

Reviews 0

No change resolves or names this issue in its commit message, and no comment links one.

History 11

  1. Benni Mack commented <span data-processor="relativetime" data-value="2022-09-07T17:52:05+00:00" > 09/07/22, 17:52 </span>

    Hey Martina,

    I like the idea, what about a “recently used” Content Types? This way, we can automate this.

  2. Riccardo De Contardi commented <span data-processor="relativetime" data-value="2023-06-20T09:38:24+00:00" > 06/20/23, 09:38 </span>

    Benni Mack wrote in #note-2:
    > Hey Martina,
    >
    > I like the idea, what about a “recently used” Content Types? This way, we can automate this.

    I favor the idea of a “recently used” list.

    Plus a “pin” icon to let the user make them permanent for him/her (that would cover the “favorite” functionality)

    What would happen with the extension EXT:content_defender ? the list should also consider the CE restrictions for the colpos.

  3. Georg Ringer commented and changed status New Closed <span data-processor="relativetime" data-value="2026-11-13T14:55:48+00:00" > 11/13/26, 14:55 </span>

    There have been several changes in this area:

    There hasn’t been done anything else because IMHO it requires a real good concept which contains various usecases including a simple editor and editors working with thousands of pages. Furthermore it is not yet even clear if such feature is really needed.

    Therefore closing the issue as part of a forge cleanup. However it can always be picked up in future anytime!