m/paliad
1
0
Fork 0
Code Issues 146 Pull Requests 8 Actions 1 Packages Projects Releases Wiki Activity

Demote 'Daten Exportieren' tab into a project Settings group #76

New Issue
Open
opened 2026-05-25 11:23:25 +00:00 by mAi · 1 comment
mAi commented 2026-05-25 11:23:25 +00:00
Collaborator
Copy Link

m's report (2026-05-25 12:40)

The "Daten Exportieren" Tab in a project is styled differently and I dont like it. I suggested earlier to put this into some settings tab and group it - it does not need to be that prominent.

(Separate: a system-wide Backup Mode is being tracked as its own issue — Inventor design phase.)

Scope

The project-detail page currently surfaces "Daten Exportieren" as its own top-level tab. m wants it demoted into a Settings/Verwaltung tab that groups rare admin actions (archive, export, future destructive actions).

What to do

  1. Audit frontend/src/projects-detail.tsx (and frontend/src/client/projects-detail.ts) for the current Daten-Export tab.
  2. Create a Verwaltung (admin/settings) tab — DE primary, EN "Settings".
  3. Move the existing Daten Exportieren UI into the Verwaltung tab.
  4. Co-locate the "Projekt archivieren" action (already demoted into the Edit modal danger-zone per t-paliad-236) — surface a pointer/link from Verwaltung tab into the Edit-modal danger zone OR leave archive where it is and note the duplication. Coder decides whichever is cleaner.
  5. Normalise the styling — Verwaltung tab uses the standard tab body styling (no special accent, no oversized buttons).
  6. Sidebar/tab ordering: Verwaltung sits LAST in the project tab list (it's rare action territory).

Files most likely touched

  • frontend/src/projects-detail.tsx — add Verwaltung tab; remove Daten Export top-level tab
  • frontend/src/client/projects-detail.ts — tab routing + click handlers
  • frontend/src/styles/global.css — only if the current Daten Export inherits a one-off rule that needs unwinding
  • i18n: projects.detail.tabs.settings → "Verwaltung" / "Settings"

Hard rules

  • Don't remove the export functionality — only move + restyle.
  • Existing backend endpoints unchanged.
  • go build ./... && go test ./internal/... && cd frontend && bun run build clean.
  • Branch: mai/<worker>/daten-export-settings-tab.

Out of scope

  • The system-wide Backup Mode (separate issue).
  • Per-export-format polish (CSV / Excel / JSON differences).
  • Permissions changes — keep current visibility rules.

Reporting

mai report completed with branch + SHAs + the exact UX path: open project → Verwaltung tab (last) → Daten Exportieren section lives here, styled like every other tab.

## m's report (2026-05-25 12:40) > The "Daten Exportieren" Tab in a project is styled differently and I dont like it. I suggested earlier to put this into some settings tab and group it - it does not need to be that prominent. (Separate: a system-wide Backup Mode is being tracked as its own issue — Inventor design phase.) ## Scope The project-detail page currently surfaces "Daten Exportieren" as its own top-level tab. m wants it demoted into a Settings/Verwaltung tab that groups rare admin actions (archive, export, future destructive actions). ## What to do 1. Audit `frontend/src/projects-detail.tsx` (and `frontend/src/client/projects-detail.ts`) for the current Daten-Export tab. 2. Create a **Verwaltung** (admin/settings) tab — DE primary, EN "Settings". 3. Move the existing Daten Exportieren UI into the Verwaltung tab. 4. Co-locate the "Projekt archivieren" action (already demoted into the Edit modal danger-zone per t-paliad-236) — surface a pointer/link from Verwaltung tab into the Edit-modal danger zone OR leave archive where it is and note the duplication. Coder decides whichever is cleaner. 5. Normalise the styling — Verwaltung tab uses the standard tab body styling (no special accent, no oversized buttons). 6. Sidebar/tab ordering: Verwaltung sits LAST in the project tab list (it's rare action territory). ## Files most likely touched - `frontend/src/projects-detail.tsx` — add Verwaltung tab; remove Daten Export top-level tab - `frontend/src/client/projects-detail.ts` — tab routing + click handlers - `frontend/src/styles/global.css` — only if the current Daten Export inherits a one-off rule that needs unwinding - i18n: `projects.detail.tabs.settings` → "Verwaltung" / "Settings" ## Hard rules - Don't remove the export functionality — only move + restyle. - Existing backend endpoints unchanged. - `go build ./... && go test ./internal/... && cd frontend && bun run build` clean. - Branch: `mai/<worker>/daten-export-settings-tab`. ## Out of scope - The system-wide Backup Mode (separate issue). - Per-export-format polish (CSV / Excel / JSON differences). - Permissions changes — keep current visibility rules. ## Reporting `mai report completed` with branch + SHAs + the exact UX path: open project → Verwaltung tab (last) → Daten Exportieren section lives here, styled like every other tab.
mAi self-assigned this 2026-05-25 11:23:25 +00:00
mAi commented 2026-05-25 11:33:52 +00:00
Author
Collaborator
Copy Link

t-paliad-245 — Daten Export in Verwaltung-Tab verschoben

Branch: mai/artemis/gitster-demote-daten
Commit: 1714b78

UX-Pfad

Projekt öffnen → Tab-Leiste ganz rechts: Verwaltung (last) → Sektion Daten exportieren (gleicher Berechtigungs-Gate wie vorher: canExportProject() — global_admin oder responsibility ∈ {lead, member} im Team). Daneben Projekt archivieren als Hinweis-Sektion mit Button Bearbeiten öffnen → der scrollt direkt auf den project-delete-btn im Gefahrenbereich des Edit-Modals.

Kein doppeltes Archive-Mass — der eigentliche Archiv-Knopf bleibt einzig im Edit-Modal-Danger-Zone (t-paliad-236). Verwaltung-Tab macht ihn nur auffindbar.

Styling

  • Kein entity-tab-action-Button mehr in der Tab-Nav (war die Quelle der Stilabweichung).
  • Verwaltung-Panel = Standard entity-tab-panel. Innen zwei .settings-section Blöcke mit .entity-section-heading (wie im Team-Tab), .tool-subtitle Beschreibung, btn-secondary Trigger. Kein Lime-Accent, kein oversized Button.
  • Tab-Reihenfolge: Verlauf → Team → Projektbaum → Parteien → Fristen → Termine → Notizen → Checklisten → Schriftsätze → Verwaltung (verifiziert in dist/projects-detail.html).

Sichtbarkeitsregeln

  • Export-Sektion: nur sichtbar wenn canExportProject() (§4 server-side gate).
  • Archive-Sektion: nur sichtbar für global_admin (mirror von project-delete-wrap).
  • Verwaltung-Tab selbst: wird ausgeblendet, wenn keine der beiden Sektionen sichtbar ist (updateSettingsTabVisibility()). Leerer Tab wäre schlechtere UX als kein Tab.

Files

  • frontend/src/projects-detail.tsx — Export-Button aus Tab-Nav entfernt, Verwaltung-Tab + Panel hinzugefügt
  • frontend/src/client/projects-detail.ts — TabId + VALID_TABS um "settings" erweitert, wireExportButton zeigt jetzt die Sektion statt eines Tab-Knopfs, renderHeader flippt parallel project-settings-archive, neue Helper updateSettingsTabVisibility(), Archive-Pointer öffnet Edit-Modal
  • frontend/src/client/i18n.ts — DE+EN i18n Keys (projects.detail.tab.settings, projects.detail.settings.export.{heading,description}, projects.detail.settings.archive.{heading,description,cta})
  • frontend/src/i18n-keys.ts — auto-regenerated (build.ts)
  • frontend/src/styles/global.css — .settings-section block-spacing (kein Akzent)

Build/Test gate

go build ./...                  → clean
go test ./internal/...          → clean (alle Packages ok)
cd frontend && bun run build    → clean (2776 i18n keys, data-i18n scan clean)

Out of scope

  • System-wide Backup Mode (separate Issue).
  • Per-export-format polish (CSV / Excel / JSON Unterschiede).
  • Permissions-Änderungen (Gate exakt wie vorher).

— mAi/artemis

## t-paliad-245 — Daten Export in Verwaltung-Tab verschoben **Branch:** `mai/artemis/gitster-demote-daten` **Commit:** [`1714b78`](https://mgit.msbls.de/m/paliad/commit/1714b788d26937a8ba558835ba510dac8f974087) ### UX-Pfad Projekt öffnen → Tab-Leiste ganz rechts: **Verwaltung** (last) → Sektion **Daten exportieren** (gleicher Berechtigungs-Gate wie vorher: `canExportProject()` — `global_admin` oder `responsibility ∈ {lead, member}` im Team). Daneben **Projekt archivieren** als Hinweis-Sektion mit Button *Bearbeiten öffnen* → der scrollt direkt auf den `project-delete-btn` im Gefahrenbereich des Edit-Modals. Kein doppeltes Archive-Mass — der eigentliche Archiv-Knopf bleibt einzig im Edit-Modal-Danger-Zone (t-paliad-236). Verwaltung-Tab macht ihn nur auffindbar. ### Styling - Kein `entity-tab-action`-Button mehr in der Tab-Nav (war die Quelle der Stilabweichung). - Verwaltung-Panel = Standard `entity-tab-panel`. Innen zwei `.settings-section` Blöcke mit `.entity-section-heading` (wie im Team-Tab), `.tool-subtitle` Beschreibung, `btn-secondary` Trigger. Kein Lime-Accent, kein oversized Button. - Tab-Reihenfolge: Verlauf → Team → Projektbaum → Parteien → Fristen → Termine → Notizen → Checklisten → Schriftsätze → **Verwaltung** (verifiziert in `dist/projects-detail.html`). ### Sichtbarkeitsregeln - Export-Sektion: nur sichtbar wenn `canExportProject()` (§4 server-side gate). - Archive-Sektion: nur sichtbar für `global_admin` (mirror von `project-delete-wrap`). - **Verwaltung-Tab selbst:** wird ausgeblendet, wenn keine der beiden Sektionen sichtbar ist (`updateSettingsTabVisibility()`). Leerer Tab wäre schlechtere UX als kein Tab. ### Files - `frontend/src/projects-detail.tsx` — Export-Button aus Tab-Nav entfernt, Verwaltung-Tab + Panel hinzugefügt - `frontend/src/client/projects-detail.ts` — `TabId` + `VALID_TABS` um `"settings"` erweitert, `wireExportButton` zeigt jetzt die Sektion statt eines Tab-Knopfs, `renderHeader` flippt parallel `project-settings-archive`, neue Helper `updateSettingsTabVisibility()`, Archive-Pointer öffnet Edit-Modal - `frontend/src/client/i18n.ts` — DE+EN i18n Keys (`projects.detail.tab.settings`, `projects.detail.settings.export.{heading,description}`, `projects.detail.settings.archive.{heading,description,cta}`) - `frontend/src/i18n-keys.ts` — auto-regenerated (build.ts) - `frontend/src/styles/global.css` — `.settings-section` block-spacing (kein Akzent) ### Build/Test gate ``` go build ./... → clean go test ./internal/... → clean (alle Packages ok) cd frontend && bun run build → clean (2776 i18n keys, data-i18n scan clean) ``` ### Out of scope - System-wide Backup Mode (separate Issue). - Per-export-format polish (CSV / Excel / JSON Unterschiede). - Permissions-Änderungen (Gate exakt wie vorher). — mAi/artemis
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
deferred
Parked — not pursuing now, may un-park later
done
Work completed by an agent; awaiting m to close
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
mAi m
No Assignees mAi
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: m/paliad#76
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?