Please follow this- https://levelup.gitconnected.com/aem-extend-core-component-models-using-resource-type-association-and-delegation-b8855ed281e2 

Could u pls ur sling model as well?

Refer this- https://adobe-consulting-services.github.io/acs-aem-commons/features/ensure-oak-index/index.html

Refer below- Example flush servletThe following code implements a servlet that sends an invalidate request to Dispatcher. The servlet receives a request message that contains handle and page parameters. These parameters provide the value of the CQ-Handle header and the path of the page to recache, r...

It should work as its working perfectly fine for us across the environments.

Read the properties in component.html using sightly and keep them as hidden fields and then access in ur js file.

Refer this one- https://medium.com/@theopendle/aem-adding-a-button-to-a-touchui-toolbar-ae1d1dc1c530

Hi, Use these properties in dialog for path browser- sling:resourceType="/libs/granite/ui/components/coral/foundation/form/pathfield"filter="nosystem"  And then author can select the renditions but make sure u add relevant rules on dispatcher nor renditions wont be accessible. 

Happy to help

Yes you can no issues with that.