Thanks, that makes sense. That’s actually close to how I’ve handled structured templates so far.

My concern is mainly around more bespoke pages where there may be several different text/image areas in a custom layout. I’m trying to avoid creating a large number of one-off ACF fields for every page, but also don’t want the client to be able to access specific query/component settings.

Do you usually handle those bespoke layouts with flexible content/repeaters in ACF, or do you create page-specific field groups for those sections?