Answers.Body: <p>You could put them in a supertable which supports nested matrix etc.
  All the info on supertable here: <a href="https://github.com/engram-design/SuperTable" rel="nofollow noreferrer">https://github.com/engram-design/SuperTable</a></p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-01-23T12:17:06.913Z
Answers.Text: I'm not sure that offers any improvement over putting them in a matrix field, and there would then be an extra third-party dependency.
Answers.UserDisplayName: Alex H
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-01-23T13:34:53.210Z
Answers.Text: Since he said "but all of the fields visually gel together in the UI in a somewhat indistinguishable list." my answer is quiet relevant. The supertable has the "row" option which gives a clear difference from a matrix. in layout.
Answers.UserDisplayName: Jan_dh
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-01-20T15:44:37.797Z
Answers.LastActivityDate: 2017-01-20T15:44:37.797Z
Answers.UserDisplayName: Jan_dh
Body: <p>Is there a mechanism for grouping related fields in an entry besides:</p>
  
  <ul>
  <li><p>a) putting them in a tab - which I generally reserve to group fields at a higher order (e.g content/data/meta)</p></li>
  <li><p>b) putting related fields inside a matrix block with a limit of 1, which feels like I'm adding a level of complexity to my content model.</p></li>
  </ul>
  
  <p>I have various modules in a page, so i've taken to labelling them with a common prefix for each module (as in 'Homepage Hero - Background Image', 'Homepage Hero - Subheading'), but all of the fields visually gel together in the UI in a somewhat indistinguishable list.</p>
  
  <p>I suppose changing my use of tabs would serve my purpose, but could look quite unruly on an entry with many elements.</p>
  
Tags: <entry><admin>
Title: Grouping related fields together
ThreadText: # Grouping related fields together
  
  (Asked by: username_0 on 2017-01-20)
  
  Is there a mechanism for grouping related fields in an entry besides:
  
  * a) putting them in a tab - which I generally reserve to group fields at a higher order (e.g content/data/meta)
  * b) putting related fields inside a matrix block with a limit of 1, which feels like I'm adding a level of complexity to my content model.
  
  I have various modules in a page, so i've taken to labelling them with a common prefix for each module (as in 'Homepage Hero - Background Image', 'Homepage Hero - Subheading'), but all of the fields visually gel together in the UI in a somewhat indistinguishable list.
  
  I suppose changing my use of tabs would serve my purpose, but could look quite unruly on an entry with many elements.
  
  **Tags:** entry, admin
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2017-01-20. Score: 1
  
  You could put them in a supertable which supports nested matrix etc.
  All the info on supertable here: <https://github.com/engram-design/SuperTable>
  
  > **Comments:**
  > **username_0**: I'm not sure that offers any improvement over putting them in a matrix field, and there would then be an extra third-party dependency.  
  > **username_1**: Since he said "but all of the fields visually gel together in the UI in a somewhat indistinguishable list." my answer is quiet relevant. The supertable has the "row" option which gives a clear difference from a matrix. in layout.  
  
  ---
  
  