Take Export out of the account menu; Settings already owns it #86

Closed
opened 2026-09-07 13:56:01 +00:00 by tiagoagueda · 0 comments
Owner

Observation

export entry is, in my opinion, redundant, since it is available on the user settings next
to the delete account, delete the entry on the drop menu

What exists today

core:export is reachable four ways:

  1. Settings → Your data, a settings section of its own, with the download icon.
  2. The account menu under your name in the header.
  3. The dashboard's Shortcuts widget, if that widget is turned on.
  4. The delete-account page, which offers the archive before you go.

The second is the one this removes. Two permanent routes to the same page, one of them in a
menu of five items, is a menu people learn to stop reading.

What it leaves

Settings → Your data is the home. The account menu keeps Your details, Settings,
Server settings for administrators, and Sign out — a shorter menu in which every entry
goes somewhere different.

The delete-account route stays and matters most: leaving without your data should never
be the easy path, and the offer belongs at the moment somebody is about to lose it.

The Shortcuts widget keeps its link, deliberately. That widget is opt-in and arrangeable
since #44 — somebody who put export on their own dashboard asked for it there, which is not
the same as the application deciding to put it in everybody's header.

The download icon is not orphaned by this: it is the icon of the Your data section
itself.

What this is not

Not a reduction in how easily data can be taken out. That is one of the project's four
commitments and the number of ways to reach the page is not what upholds it — the export
being complete, documented and one button is. What changes is that the header stops
advertising a page the settings area already owns.

Classification

Enhancement, interface. Not breaking: no address changes and nothing is removed but a
duplicate link.

## Observation > export entry is, in my opinion, redundant, since it is available on the user settings next > to the delete account, delete the entry on the drop menu ## What exists today `core:export` is reachable four ways: 1. **Settings → Your data**, a settings section of its own, with the `download` icon. 2. The **account menu** under your name in the header. 3. The dashboard's **Shortcuts** widget, if that widget is turned on. 4. The **delete-account page**, which offers the archive before you go. The second is the one this removes. Two permanent routes to the same page, one of them in a menu of five items, is a menu people learn to stop reading. ## What it leaves *Settings → Your data* is the home. The account menu keeps *Your details*, *Settings*, *Server settings* for administrators, and *Sign out* — a shorter menu in which every entry goes somewhere different. The **delete-account route stays and matters most**: leaving without your data should never be the easy path, and the offer belongs at the moment somebody is about to lose it. The **Shortcuts widget keeps its link**, deliberately. That widget is opt-in and arrangeable since #44 — somebody who put export on their own dashboard asked for it there, which is not the same as the application deciding to put it in everybody's header. The `download` icon is not orphaned by this: it is the icon of the *Your data* section itself. ## What this is not Not a reduction in how easily data can be taken out. That is one of the project's four commitments and the number of ways to reach the page is not what upholds it — the export being complete, documented and one button is. What changes is that the header stops advertising a page the settings area already owns. ## Classification Enhancement, interface. Not breaking: no address changes and nothing is removed but a duplicate link.
tiagoagueda added this to the 0.3.0 milestone 2026-09-07 13:56:01 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
Postulo/postulo#86
No description provided.