Template Manager Question

[Tigerbay]

Hey guys, we’re looking to build a customer site with pro, which is going to be very ‘data heavy’ - we’ve been looking at how we can use cornerstone, whilst not duplicating a lot of the template itself, and so are looking at ACF or https://wp-types.com/ to provide the ‘relational data’, and cornerstone to then render that.

Is this a use case you see being compatible with template manager? Could we, for example create a template in pro that reads a value from the page with [acf field="{$field_name}"], and then use that template on multiple pages?

I tried to follow the post here https://theme.co/apex/forum/t/template-manager-discussion/12191 - and can’t see any mention of acf, and wondered if you’d considered documenting what you’re intending to build somewhere, as a way to get feedback? Perhaps a KB article similar to https://theme.co/apex/forum/t/setup-demo-content/56 - documenting how you’re intending it to wok?

[alexander]

Great idea! This would be a good addition to V2 elements. I’ll add it to our notes. The main challenge I can perceive at the moment is that fields may not be able to render correctly in the preview. That said I think it’s a valuable feature to have under consideration.

If we further integrated with ACF for V2 elements like this it wouldn’t be directly related to the template manager. Hypothetically you’d be able to add the ACF field name to content controls, then it would populate on that page you’re working with. The entire page (or header/footer with Pro) could then be saved as a template. When that template is re-used on other pages you’d already have those fields wired up, ready to be filled with the field values.