You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some fields may be more or less relevant on a per-client basis. Rather than displaying all fields for all clients...
which could lead into a trap of needing to add new fields for all clients every time 1 or more clients ask for it
which could lead to spending time coordinating with various clients what changes they ALL want vs what change is only desired by a specific client...
which could then lead to unnecessary forks of the project.
...Maybe we could build functionality that either gives an admin the ability to add their own fields OR puts EVERY optional field behind a feature flag that can be enabled/disabled on a per-client basis.
The text was updated successfully, but these errors were encountered:
@LarsKemmann - while this is an idea that would inevitably improve the UI (not to mention yield other benefits), the type of work involved is largely not UI-related (unless there ends up being some sort of admin dashboard that needs to be created for configuring these settings). As such, I'm only applying the "backend" label to this idea for the time being & depending on if/how you'd like to move this forward, you may want to consider moving this particular idea to a different project instead of "UX/UI" improvements
Some fields may be more or less relevant on a per-client basis. Rather than displaying all fields for all clients...
...Maybe we could build functionality that either gives an admin the ability to add their own fields OR puts EVERY optional field behind a feature flag that can be enabled/disabled on a per-client basis.
The text was updated successfully, but these errors were encountered: