When defining inputs for models, it can get overwhelming to manage a long list of individual inputs—especially when multiple inputs are related to the same section of the model.
For example, if you're building a hero section, you might define inputs like:
hero_text
hero_image
hero_description
However, this approach makes the input list cluttered and harder to manage. Instead, a better approach would be to group related inputs under a common parent, such as hero
.
With this approach, instead of separate input names, you'd define a group called hero
, and within it, you'd have:
text
image
description
This way, the UI can visually organize these inputs under the hero section, making it clear that they belong together.
✅ Cleaner UI – Instead of a long flat list of inputs, related inputs are nested within sections.
✅ Better Organization – Easier to understand and manage, especially when dealing with complex models.
✅ Scalability – You can add more grouped sections without making the input list overwhelming.