Content
View differences
Updated by Alexander Coles 7 months ago
**Discussed at** [**UX/UI Open Door on 30.10.2025**](https://community.openproject.org/projects/gmbh/meetings/7224) **in the context of bug** **#68679** <mention class="mention" data-id="68679" data-type="work_package" data-text="#68679"><strong>#68679</strong></mention> **.**
Primer provides an API for "nested forms" - groups of form fields that can be associated with radio button and checkbox controls. Having additional fields be displayed when a checkbox is checked is a very common UI idiom generally - and one that is used extensively in OpenProject.
Checkbox Nested Forms docs:
* [API docs](https://primer.style/product/getting-started/rails/components/checkbox/#nested-forms)
* [Lookbook docs with example](https://primer.style/view-components/lookbook/pages/forms/inputs/check_box)
Nested Forms are indented by default. An example of how this might look on our _Admin > Authentication > Login and registration_ page:
<img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/805445/content">
However, we're not currently indenting fields in this way on other forms in OpenProject core - neither Primerized nor legacy forms. This may be because developers were unaware of the nested form API. However it may also have been a deliberate choice - in order to avoid the default styling (indentation) that nested forms use.
**Open Questions**:
Question**: Should we adhere to the Primer design/implementation for sake of consistency?
design/implementation? (if so, we should create a follow up Code Maintenance ticket to harmonise the look and feel of forms that use this Pattern - and replacing custom implementations with "proper" use of the nested form API).
**Arguments?**
**Should we use indentation to convey the association between controls?** (vs inset boxes, etc.) Or does it have the potential to distract users?
Primer provides an API for "nested forms" - groups of form fields that can be associated with radio button and checkbox controls. Having additional fields be displayed when a checkbox is checked is a very common UI idiom generally - and one that is used extensively in OpenProject.
Checkbox Nested Forms docs:
* [API docs](https://primer.style/product/getting-started/rails/components/checkbox/#nested-forms)
* [Lookbook docs with example](https://primer.style/view-components/lookbook/pages/forms/inputs/check_box)
Nested Forms are indented by default. An example of how this might look on our _Admin > Authentication > Login and registration_ page:
<img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/805445/content">
However, we're not currently indenting fields in this way on other forms in OpenProject core - neither Primerized nor legacy forms. This may be because developers were unaware of the nested form API. However it may also have been a deliberate choice - in order to avoid the default styling (indentation) that nested forms use.
**Open Questions**:
**Arguments?**
**Should we use indentation to convey the association between controls?** (vs inset boxes, etc.) Or does it have the potential to distract users?