⭐️ Make "Fieldsets" work (to replace both 'blocks' and 'repeaters')

[bobdenotter]

No description provided.

[bobdenotter]

When implementing this, don't forget to make it work in _sub_fields.twig as well.

[sbonardt]

The name 'fieldset' for me is too much tied to a form to use it as a field type name. Other suggestions:

'field groups', 'field collections', or 'grouped fields'

[bobdenotter]

"Groups" is already used to refer to groups of fields shown on one 'tab' in the editors, so that's confusing too.

    fields:
        title:
            type: text
            group: Text

[sbonardt]

@bobdenotter So shouldn't "group" be renamed to "tab" then...? To keep things logical. Now you assign fields to a certain "group" to have them show up in a certain "tab". Assigning a field to a certain "tab" to have them in a certain "tab" in the UI sounds good to me. And then you can use "group" to group fields. Or "fieldgroup"

[bobdenotter]

A tab is "what it looks like", not "what it is". It feels kinda like <div class="red"> to do that.

[sbonardt]

If you want to name it what it is, then just rename "group" to "fieldset". But this is UI for the end user, and that person sees a "tab".

Any way, you get to use "group" for the group of fields

[bobdenotter]

I think i'm more in favor of your other suggestion: Name the replacement for Blocks and Repeaters "Collection", and leave 'group' as is.

[bennash]

My 2 cents: Collections and Groups sound like they refer to organized pieces of content, not the atomic parts. With Bolt CMS "Blocks" I often call them Content Blocks or Section Blocks. "Repeaters" is a common CMS term meaning just what they are. I've thought about this term for years when trying to explain it to my client editors. I don't have a great suggestion. How about "Combination Field" or "combo" for short?

…

On Fri, Nov 15, 2019 at 10:05 AM Bob den Otter ***@***.***> wrote: I think i'm more in favor of your other suggestion: Name the replacement for Blocks and Repeaters "Collection", and leave 'group' as is. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#176?email_source=notifications&email_token=AABLNAXLCWI6XWOQHIGRM4TQT3CCZA5CNFSM4GHFLKM2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEEF4RTI#issuecomment-554420429>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AABLNAST2AJQSZ7GSPEGZ7DQT3CCZANCNFSM4GHFLKMQ> .

[bobdenotter]

Closing, because the feature has been implemented.