You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm experimenting with this myself and found it a huge improvement for labeling page sections. Right now they're just a bunch of groups between header and footer parts in the Blueprint. The biggest downside is that the're no labels.
I find the category names from Relume library for Webflow quite useful for labeling custom template parts in a more descriptive way, and then use patterns as the actual component variants of the template part.
To build a page I'd then add a bunch of empty labeled template parts, and then when I'm happy with the sequence I'd click into a template part and try different pattern variants.
Are there reasons against this approach?
The text was updated successfully, but these errors were encountered:
I don't think there's a reason against it per se, it's just not built into core that way (at least not yet!). I think we can achieve something similar with patterns. There's some work being done on being able to label layers.
Patterns are going to be a huge place for core improvement in the coming months and years. They are going to play a big part in the evolution of WordPress.
AI could potentially also play a good part in creating pattern variations. "Act as a designer and show me 10 product grid variations.." haha.
WP and the block editor has a huge potential as nocode MVP platform for indie hackers too, especially if they implement the dynamic stuff. It's difficult to stay pacient knowing all this potential ;)
Hi,
I'm experimenting with this myself and found it a huge improvement for labeling page sections. Right now they're just a bunch of groups between header and footer parts in the Blueprint. The biggest downside is that the're no labels.
I find the category names from Relume library for Webflow quite useful for labeling custom template parts in a more descriptive way, and then use patterns as the actual component variants of the template part.
To build a page I'd then add a bunch of empty labeled template parts, and then when I'm happy with the sequence I'd click into a template part and try different pattern variants.
Are there reasons against this approach?
The text was updated successfully, but these errors were encountered: