Hiya,
Just a suggestion - currently with sections & blocks you can organize them quite nicely with headings, paragraphs and visible_if.
Metaobjects on the other hand have quite a basic UI, which can become cluttered very easily with no way to break-up fields or show them conditionally. So many recommendation is to bring metaobjects up to date with sections/blocks and allow headings/paragraphs (read only) and visible_if properties.
Edit: oh and default values would be nice 
Thanks!
Hello, and thank you for providing us feedback! We agree. It would be helpful for us to get some additional context.
Can you help me understand what you’d like to accomplish by providing a use case you have in mind, and soime examples of what an ideal world would look like?
This will help us validate that we are solving the same problems you are experiencing.
@James_Lunan Thanks for the quick response.
Certainly! An example that I’m working with at the moment is “Promotional Blocks”, these can be used in sections throughout the site, such as the collection grid, menu navigation, standard page sections and so on.
Now the client doesn’t want to have to enter this information multiple times (the same block could appear on the collection grid and product DPD), and it also needs to be “attached” to certain resources i.e. collections/products - so metaobjects are the best fit.
However.. there are a lot of fields and customization options (see image), normally I’d split these up into different sections i.e. Content, Layout and Appearance. The mobile versions of those settings also wouldn’t show unless the desktop ones have been filled in first. Depending on the layout, other options may hide/show too.
If you see my example below, it’s very difficult to find anything and there’s little context.
This is very helpful. We won’t get to this right away but it’s next on our list of larger front end fixes we would like to start.
