I'm trying to create an editable template that contains just the core tab component with 2 tabs that are pre-defined by the template authors. I don't want the page authors to be able to change the title or add/remove tabs but they should be able to add content to them. This is what I tried which I t...

This works, thank you! It seems like a lot to ask authors to do though - i wish there was a way to set default policies for components.

I'm trying to define the allowed components on the core tab component and can't find an answer on how to do it cleanly. I know we can specify which container components are available to add here -But that policy applies to both which components you can add as containers and which components you can ...

Seems so obvious now that you've pointed it out. That works perfectly, thank you!

Hello,   We're using a tagfield (cq/gui/components/coral/common/form/tagfield) in a dialog and need to make the field required, but only if it's visible. To do this we've written custom validation using foundation-validation but it doesn't appear to be triggered for the tagfield type. Is this becaus...

Thanks Aditya,   Yes that is the general idea of what I'm trying to do but ideally I'd want the layout containers to still span across the entire page, just changing the size of the components within those containers. So if i had two layout containers stacked on the page with different grid sizes, i...

Hello,   I'm trying to allow authors to drag multiple layout containers onto a page and allow each one to have a customizable grid size. We've been using editable templates so far but from what i'm seeing with testing/reading in the documentation it doesn't sound like that's possible unless we use s...

Thanks for that, sorry if i was not clear. The issue we're experiencing is with the Timeline functionality within sites.html. It is unable to load the timeline because some internal logic is trying to parse the events and expects one of the pre-defined event types.

We have functionality that inserts a custom audit log type whenever a certain property is updated - auditLogger.add(new AuditLogEntry( "com/day/cq/wcm/core/page", new Date(), newEvent.getUserID(), pageNodePath, "PageRestricted", entryProperties )); This was added back in classic and has ...

Thank you - I assumed not and that they must have been confused but had to do my due diligence.