Jon S.

Agree that you have to walk a line between ultra-flexible do-anything components filled with slots and overrides, vs narrowly scoped, single(ish) purpose layouts. Working on one where I think I over-indexed on the flexibility side at the expense of a bit of usability, caused some rework to simplify things for the end user. Knowing the aptitude - or interest - of the folks using the system is important!

Yeah, I'm still figuring out my way through all the conundrums Caleb mentioned - modular vs fixed, how much to rely on nested components, etc. But it's at least nice to know a few other folks are figuring it all out too

I don't have an example at the ready, but I'll drop this awesome post from Caleb Raney that mirrors a lot of how I'm thinking of a scalable component system! https://www.calebraney.com/post/component-first-development-in-webflow

Junnan M. use the Relume chrome extension, it has a tool for preventing this

Can't wait to try the sitemap import, think it'll be a great workflow improvement for some projects!