Worked at an agency that had this for a while, and it was great while it lasted. Pretty quickly devolved into overflow time for client work, the micromanagement M-Th clashed with the freeform nature of F, and nobody knew what to do unless told. Cultural issue, but the idea is gold if it fits.

Can't go wrong with some defiant jazz! music.apple.com/us/playlist/...

Mast 2.0. First build with it, and the new build-mode features are what are getting me really into this mindset.

As an agency, for the last year, we've been probably 40% Mast, 40% CF, 20% old custom framework. Still evaluating but think we'll transition to Mast fully.

Yes! That's exactly what I've landed on. Passing only important props "up a level" to the parent component.

That, and a couple instances of baseline "section" components that have props not related to the content - style variants, container width, etc.

There's a hypothetical concept of a single component that's nearly infinitely flexible, that you could build 80% of a site with, making heavy use of components and props and variants. But I imagine most clients would prefer "I want this section, let me drag it in."

Working on a big component-first build now. One of the biggest planning challenges is finding the right line between flexibility and guardrails.

My first stab at a visual header was a "you can do anything" approach, hyper-flexible - but would have been difficult for a client to manage.

Ah I see, are you looking to have the p the same height across each card, even if the text content is longer?

Or is the goal to have each card the same height, based on the tallest in the grid (pretty much defined as which one has the longest content)?

I'm thinking on the wrap, grid-auto-rows: 1fr

Should make all rows the same height, if you use the repeat(3, auto) option (or maybe 3, 1fr)

This was so interesting, well researched, and well written!

Smart!

None I'm aware of, aside from creating new fields for manually importing. Of course those are very limited for the actual purpose of updated item data for schema etc.

Yasss make me obsolete

Works with just about any dropdown:
- CMS list source
- CMS element binding
- CMS styling
- CMS condition visibility
- Links (static or CMS, link, page, attachment, etc.)
- Works in settings panel or on-canvas dialog

This is the only way

And I didn't find out this worked until halfway through switching every light switch in the house

Haha no worries! Good feedback that it may not be the most clear, and I didn't provide any indication that it's down there. I just opened it up myself and it's a little hidden.

The collapse icon would be in the bottom left of each panel, not sure if the screenshot includes that. But if that's not there, you're not missing anything, something's going on I'd have to investigate.

There's edge cases where they don't appear. When creating a new collection, when the collection is empty, etc. I'd say it works in ~90% of scenarios for me, haven't been able to account for the others yet.

If you're opening an existing collection with items, I'd be love to see a screenshot/steps.

I will say, the "monocolor to brand color" hover effect sucks with X 😢