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!