Admin: split language packages into a dedicated administration section #3

Open
opened 2026-07-11 03:43:46 +02:00 by zemion · 0 comments
Owner

Context

The current Administration area mixes language packages and defaults for newly created tenants into the general system settings surface.

Requested behavior

Move Language packages and Defaults for newly created tenants into a separate Administration menu item.

The new language-package surface should show module-version-specific language packages and make their lifecycle explicit:

  • installable packages
  • installed packages
  • activatable and deactivatable packages
  • uninstallable packages
  • module/version compatibility for each language package

Acceptance criteria

  • Administration has a dedicated menu entry for language packages/default tenant language behavior.
  • General system settings no longer carries the full language-package lifecycle UI.
  • The list distinguishes installed, available, active, inactive, incompatible, and uninstallable packages.
  • Package state is scoped to the module/version it belongs to.
  • The UI remains usable when no additional language packages are available.

Notes

This likely needs an API contract for discoverable language package metadata if the backend does not already expose it.

## Context The current Administration area mixes language packages and defaults for newly created tenants into the general system settings surface. ## Requested behavior Move **Language packages** and **Defaults for newly created tenants** into a separate Administration menu item. The new language-package surface should show module-version-specific language packages and make their lifecycle explicit: - installable packages - installed packages - activatable and deactivatable packages - uninstallable packages - module/version compatibility for each language package ## Acceptance criteria - Administration has a dedicated menu entry for language packages/default tenant language behavior. - General system settings no longer carries the full language-package lifecycle UI. - The list distinguishes installed, available, active, inactive, incompatible, and uninstallable packages. - Package state is scoped to the module/version it belongs to. - The UI remains usable when no additional language packages are available. ## Notes This likely needs an API contract for discoverable language package metadata if the backend does not already expose it.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: add-ideas/govoplan-admin#3
No description provided.