Matrix field alternative (or easier field grouping)

Question

Just started working with Craft, and it's been great! One question I have is regarding the 'correct' way to create a group of fields, rather than using Matrix or Table.

To better illustrate, see the below screenshot of a Matrix, which is setup as a Global for people to add their contact information.

Obviously, it's not really being used for the purpose of repeating content, but at least it groups fields together nicely. It does have the greyed-out button when setting Max Blocks to 1.

The other alternative would be to create each Field separately for the 3 fields above, and add those to the Field Layout. This is kind of a fair amount of work, and leaves you with a massive cluster of Fields (I'm aware you can Group them).

Anyway - hope I've explained myself! Just wanted to bounce ideas around, and at least make sure I'm on the right track!

Answer 1

Depending on the amount of data required (and if it makes logical sense to have the data separate from the entry) I'd probably set this up as a "Contact details" section itself, using the individual matrix fields from your example.

Then if some other entry type needs it, set up an entries field in that entry type, limited to entries in the "contact details" section and limited to the number of contact detail entries you want to show, probably 1 going by your example.

This way you can still have your details grouped (as a separate entry) but it's more compact as a single field rather than a matrix in the fields of the entry you're using the contact details in.

The trade-off is that you need to enter your contact details entry before you try to add it to your "x" entry field.

If it makes no logical sense to have the fields as entirely different sections and your fields are getting cumbersome I think the best way is to put them in a different tab to at least remove the clutter.

Answer 2

As other answers here say, unfortunately creating tabs is currently the only way to "group" contextually related fields (or create "fieldsets", as it were).

What you could do, is use either FieldNotes or Entry Instructions to create messages/headers in your edit tab, visually separating one "group" of fields from another.

Answer 3

Just in case anyone is interested, I've decided to make a plugin for this. It's pretty basic, but its exactly what I was after. It's essentially a regular Table with a Label option to provide some read-only text.

https://github.com/engram-design/SetTable

Answer 4

Using tabs is the only way to do this at the moment. As Lindsey says, using a Matrix field adds a table to the database and will slow down your load times.

I'd prefer, like you, to be able to group fields to improve usability for the client, but there's no way to do this at the moment apart from tabs.