Reorganisation of the Mail User Interface – Tools Slate and Tabs

1 Initial Problem

The Mail tool slate currently falls well short of its potential. At the same time, we have an environment in the main area with the previous tab structure that is not easy to understand - even if it may have been learnt over time.

2 Conceptual Summary

We would like to replace the tab structure. We also want to reorganise the basic tree structure of the mail spaces. We are strengthening the use of the Tools-Slate and focussing on the main content area.

The Tool-Slate "Mail"

(Almost) All Tabs and all Spaces of the previous Tree Structure in the Mailbox will be reorganised in the Tools-Slate.

• New Mail [Bulky Link] instead of 'Compose'-Tab
• Inbox [Bulky Link] instead of 'Inbox'-Tree-Node
• Drafts [Bulky Link] instead of 'Drafts'-Tree-Node
• Outbox [Bulky Link] instead of 'Outbox'-Tree-Node (scheduled for Trunk, planned for ILIAS 11, see here)
• Sent [Bulky Link] instead of 'Sent'-Tree-Node
• Trash [Bulky Link] instead of 'Inbox'-Tree-Node
• User Folders [Drilldown or Combined Slate with Folder-Tree // If no child elements exit, it should be a Bulky Link] instead of 'User Folders'-Tree-Node with potentially Sub-Nodes
• Attachement [Bulky Link] instead of 'Manage Attachments'-Tab
• Mail Options [Bulky Link] instead of 'Options'-Tab 

Additional remark: From a Process Point of View ''Trash' is places behind 'Draft', 'Outbox', 'Sent'

Tabs in Mail and Page Header

All tab structures are therefore dropped. 

Instead, we display the correct (!) icon and label in the page header.

 
 » » »

 
 » » »

Contacts should only be accessible via their own main menu entry. Currently, the content of contacts is offered again in a kind of substructure under Mail.

3 User Interface Modifications

3.1 List of Affected Views

3.2 User Interface Details

See Chapter 2 with detailed description ans Mockups

3.3 New User Interface Concepts

None. Using existing Elements of UI Framework.

3.4 Accessibility Implications

Nothing specific.

4 Additional Information

4.1 Involved Authorities

If this request is related to multiple components, please list both authorities for all related components.

4.2 Technical Aspects

@Michael: Anything important?

4.3 Privacy

No changes on any privacy aspects.

4.4 Security

No changes on any security aspects.

4.5 Contact

Person to be contacted in case of questions about the feature or for funding offers: Samoila, Oliver [oliver.samoila] 

4.6 Funding

Funding status and funding parties are listed in the block 'Status of Feature' in the right column of this page.

If you are interested to give funding for this feature, please get into contact with the person mentioned above as 'Contact'.

5 Discussion

Samoila, Oliver [oliver.samoila], 2025-05-12:

Thanks Richard for your comment.
I'm a bit confused as to which ‘element’ is in which and then interacts with the others and how. (Maybe just a language thing on my side. ;) Sorry.)
I would suggest that we discuss this at the JourFixe meeting.

What I had also considered – and this brings us to the pending (Project) Splitting-up Tools – is to have the mail as »the one tool« in use.
This would lead to the following structure – see MockUp. To clarify: there is no second tool in the context of Mail.

(I didn't want to open 'Pandora's box', but I think it would be great if we could make an impulse and first step in real in the direction of (Project) Splitting-up Tools).

What I don't think I would do is to always use a Drilldown to the ‚Mail' in the main menu entry ‘Communication’ and then display all the entries (‘New Mail’ ... ‘Inbox’ ... ‘Mail Options’).
This feels wrong in terms of the depth structure. It is somehow too much for a main menu entry.
And I also don't know what it does to the loading of the contents of user folders in context of main menu.

6 Implementation

Feature has been implemented by {Please add related profile link of this person}

6.1 Description and Screenshots

{ Description of the final implementation and screenshots if possible. }

6.2 Test Cases

Test cases completed at {date} by {user}

6.3 Privacy

Information in privacy.md of component: updated at {date} by {user} | no change required

6.4 Approval

Approved at {date} by {user}.