Unless the header and footer is a dynamic content, it has to be managed at the template.couple of options1. As Scott mentioned use editable templates and let author make changes or 2. I would create a experience fragments using these components and include in the template. So you can make a change a...
Hi, If you need any variation to the existing component, you can overlay that component and create a new one and then use it.else you may have to write some listeners to handle these restrictions at different places which personally I don’t prefer as it increases the complexity of a component and a...
Hi Bobby,I see this as per AEM 6.4I have 3 collections as shown here in which only 'parent-child' is the public collection.So when you look at the JCR,there is a node called 'public' under /content/dam/collections and only that public collection is present under this node. So as long as you dont cre...
Hi Tapas,Adobe has quite a lot of helpx articles and as smacdonald2008 and arunp99088702 have rightly pointed out some of them. Let us know if you still didnt find your example and we can try to create one if you provide your use case.Thanks,Lokesh
Hi Adarsh,It depends on your design of the component. It cant be generic I believe and it should be more based on the use case of a component.Most likely as you have noted, this would be there for image/background components. So you can add a parsys element to the image component and can make that t...
Also, we should think of real need to have so many properties for a node! A right balance could be made between hierarchical and properties. If you can give more details of your usecase, we can suggest better!
Hi,I dont think there is any restrictions on the number of properties for a given node in Jackrabbit Oak. However, the number of nodes would contribute to the performance impact but the number of properties might not if its indexed.Thanks,Lokesh