[FEATURE]: Unify UI elements #402

New issue

Open

opened 2026-02-03 15:32:47 +01:00 by simon · 0 comments

simon commented

2026-02-03 15:32:47 +01:00

Owner

Description

While developing new features, we should start aligning and standardizing our UI patterns. Right now, different views use different approaches for navigation menus, modals, dropdowns, search inputs, inline editing, button sets, etc.

This is noticeable in the Group view, but it also affects Users, Roles, and other areas. We have multiple table-based views with similar functionality, but small differences in behavior and a noticeably different look and feel.

This should be treated as a planning task: we need to decide on a consistent set of UI patterns and potentially introduce reusable components. We should also evaluate whether there are existing DaisyUI/Tailwind plugins or component libraries that can help.

One concrete example: the Custom Fields UI uses relatively complex per-item menus (high click count) even though each entry only has 2–3 attributes—this could likely be improved via inline editing.

Acceptance criteria

Define and document a set of standard UI patterns (menus, modals, dropdowns, search, inline edit, table actions, buttons) to be used across views.
Identify candidates for reusable components (e.g., shared table/action patterns) and create a plan for adoption across Group/User/Role/etc. views.

External or internal Dependencies

## Description While developing new features, we should start aligning and standardizing our UI patterns. Right now, different views use different approaches for navigation menus, modals, dropdowns, search inputs, inline editing, button sets, etc. This is noticeable in the Group view, but it also affects Users, Roles, and other areas. We have multiple table-based views with similar functionality, but small differences in behavior and a noticeably different look and feel. This should be treated as a planning task: we need to decide on a consistent set of UI patterns and potentially introduce reusable components. We should also evaluate whether there are existing DaisyUI/Tailwind plugins or component libraries that can help. One concrete example: the Custom Fields UI uses relatively complex per-item menus (high click count) even though each entry only has 2–3 attributes—this could likely be improved via inline editing. ## Acceptance criteria * [ ] Define and document a set of standard UI patterns (menus, modals, dropdowns, search, inline edit, table actions, buttons) to be used across views. * [ ] Identify candidates for reusable components (e.g., shared table/action patterns) and create a plan for adoption across Group/User/Role/etc. views. ## External or internal Dependencies