@rahul234dabas Use these documents [1] [2] for reference.   [1] https://experienceleague.adobe.com/docs/experience-manager-learn/getting-started-with-aem-headless/spa-editor/react/extend-component.html?lang=en  [2] https://experienceleague.adobe.com/docs/experience-manager-core-components/using/deve...

There are several ways to handle this, a few are Using Oak index - Add page number as index/sortable property in oak index. Now to list the child below the parent page, use a query with a sort parameter as the page number.In your sling model, simply iterate all children below the parent, and create ...

The default name is "administrators" only, you can change the name, but not id.

With reference component, content management was a challenge, as reused content is part of main hierarchy/pages. AEM has a better and cleaner approach to using Experience Fragments, which is a good replacement for reference components. 

as per jackrabbit documentation [1], "The admin user is always being created. The ID of this user is retrieved from the user configuration parameter PARAM_ADMIN_ID, which defaults to admin."   You can create users and add them to Administrator groups.   [1] https://jackrabbit.apache.org/oak/docs/sec...

Admin user is a superuser, who can perform any action in AEM, so even if you have added any restriction on an action in AEM, admin can also perform this action.

Hello @Sanjana12    Check Image core component [1] [2], which uses the image in component dialog.   [1] https://www.aemcomponents.dev/content/core-components-examples/library/core-content/image.html [2] https://github.com/adobe/aem-core-wcm-components/tree/main/content/src/content/jcr_root/apps/core...

As mentioned in my previous comment, It's advised to use core components as dependency and overlay them to use.  Forking is a decision you have to evaluate for your business use case, but consider the fact that you will not get any benefit from future releases of core components.

@sephytodd you can fork the core component repo and maintain it as your company's core component.  The only constraint in this approach will be that, you will not get any benefit from future releases of core components. So take a decision carefully about which approach you want to proceed with.