[6.x] Addon settings field layout not ideal for Replicator

[martyf]

Bug description

With the revised field layouts, the Replicator fieldtype has some less-than-ideal layout quirks.

There's an excess of white space, and some fields have odd layouts (see #12730).

Referring back to #12125 and Ideas 1376, improving flexibility with how fields gets presented should be considered.

Ideally there should be a balance (or dev control) between how layouts behave. For Feedamic 3 in Statamic 5, there are custom routes registered that make the view appear like any other Publish Form in the CP - like when editing an Entry. For Feedamic 3 in Statamic 6, those routes aren't registered and it uses Statamic 6's built-in Addon Settings support.

The issue though is that Statamic treats Addon Settings like authoring a Blueprint/Fieldset - and not authoring an Entry. I feel the layout for Addon Settings should be more like an Entry (i.e. what CP users see day to day), and less like a dev view.

For some addons, this view may be great. For others - such as Feedamic which has an advanced array of configuration - it is problematic.

Going back to those earlier ideas, I queried if it were possible to allow the dev to choose layout behaviours to suit the fields in use: this way there's greater flexibility for advanced settings, but also streamlining for simple addon settings too. Or even perhaps container breakpoints to make things stack better in such a narrow space.

See example with Feedamic settings in Statamic 6 Alpha 13:

How to reproduce

1. Install Statamic 6 Alpha 13
2. Install Feedamic (https://docs.mity.com.au/feedamic/3/installation)
3. Go to "Addons" then "Feedamic" to see the layout

Logs

Environment

Environment
Application Name: Statamic
Laravel Version: 11.46.1
PHP Version: 8.4.13
Composer Version: 2.8.11
Environment: local
Debug Mode: ENABLED
URL: statamic6.test
Maintenance Mode: OFF
Timezone: Australia/Adelaide
Locale: en

Cache
Config: NOT CACHED
Events: NOT CACHED
Routes: NOT CACHED
Views: CACHED

Drivers
Broadcasting: log
Cache: file
Database: sqlite
Logs: stack / single
Mail: log
Queue: sync
Session: file

Statamic
Addons: 12
Sites: 1
Stache Watcher: Enabled (auto)
Static Caching: Disabled
Version: 6.0.0-alpha.13 PRO

Statamic Addons
martyfriedel/les-mills-class-types: dev-feature/statamic-6
mitydigital/feedamic: dev-main
mitydigital/iconamic: dev-main
mitydigital/sitemapamic: dev-main
mitydigital/statamic-form-submission-cleaner: dev-main
mitydigital/statamic-logger: dev-main
mitydigital/statamic-scheduled-cache-invalidator: dev-main
mitydigital/statamic-sticky-notes: dev-main
mitydigital/statamic-stripe-checkout-fieldtype: dev-main
mitydigital/statamic-tinymce-cloud: dev-main
mitydigital/statamic-variable-number-fieldtype: dev-main
mitydigital/supportamic: dev-main

Installation

Fresh statamic/statamic site via CLI

Additional details

No response

[jaygeorge]

Hey Marty, just to let you know #12813 should at least fix the layout here

[duncanmcclean]

Can you try adding full_width_setting: true to your replicator field? It'll give the replicator 100% width, rather than 50% so it doesn't look as bad.

We can still look at potentially adding a config/content setting for addon settings blueprints if its needed. 👍

[martyf]

Better - but highlights issues with the spacing of fields still.

Given the "Label" is 50% in width, the "field" is 50%, meaning the Group fieldtype is split in to two 50% columns too:

It's that big I can't even fit it on a single screen, and my "full screen" tool to capture an entire page gets stuck in an infinite loop with v6.

The new layout is just too generalist and takes up far too much space. I appreciate it is hard to work towards something that works for every use-case, however the currently approach is creating unnecessary issues.

The 50% column on the left creates far too much unnecessary space for larger or more complex forms, leaving the right column to be far too squished for more complex fieldtypes.

Specifically the "Routes" section: there's space under the text inputs, huge space under the label on the left column. There's also weird space above "Title" at the top.

For comparison, here is the layout in v5:

[jasonvarga]

The fields inside a replicator shouldn't be using the "config" field layout. That seems like a bug.

[duncanmcclean]

From the next alpha, the "config" field layout will only be used for top-level fields, not things like Replicator Sets or Group field.

Hopefully this combined with full_width_setting improves things for you! If you're still having issues, let us know and we'll see what we can do! 🙂

[robdekort]

The full_width_settings helps a lot but the layout of a grid is still a bit weird.

[duncanmcclean]

The full_width_settings helps a lot but the layout of a grid is still a bit weird.

It'll be fixed in the next release: #13964