my b. you are correct @msgavali111 keep the property name in content fragment model as `disclosures` since it is array of multiple disclosures. 

Please accept answer and close the question if its clarified.

You dont need to create, just reuse existing wcm core components. Here are your OOTB optionsImage component - allows to drag-n-drop DAM assets OR you can upload images from file upload and render https://www.aemcomponents.dev/content/core-components-examples/library/core-content/image.htmlFoundation...

This is a duplicate of your previous questionhttps://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/how-to-implement-below-use-case-related-to-content-fragments-in/td-p/674038 Please dont raise duplicate question, and preferably attempt few steps by reading documentation and reach...

What has been tried and what is the exact issue faced? Your requirement is bit incorrect. I ll shuffle your order to implement correctly.  Start by creating a Content Fragment Model, "Disclosure Model".Add a text field and change to Multiple field Create a Content fragment using this model and autho...

Then your answer is already provided. Write a servlet like this@component(service = { Servlet.class }) @SlingServletResourceTypes( resourceTypes="project/components/demo", methods=HttpConstants.METHOD_GET) @ServiceDescription("Demo Component ResourceType Servlet") public class DemoResourceTypeSe...

Correct @NitroHazeDev , its for AEMaaCS coz the problem we run into is unique for Cloud world. And Sling jobs is generic for author or publisher. But as adviced, write only in author.

Your direction sounds wrong. If you are writing HTL component like PageTitle component that must render page name, you dont need servlets, instead use Sling models to render the page name server side.  Idea is, the page originates at AEM serverside. While AEM prepares the page, you attempt to render...

Directions pointed below are correct. DONOT run jobs on publisher. Publisher is intended for delivery, background jobs on publisher might badly impact your website performance.  Ideally should run jobs at author and replicate to keep publishers in sync with author. 1 learning we found when writing s...

This is correct. to reuse same model across multiple components. This also promotes page performance as we leverage sling caching mechanism. Refer to this pattern in wcm core component. com.adobe.cq.wcm.core.components.models.Page model is called from multiple page components https://github.com/adob...