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

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.

Yes you can if you are not going to use vanity url's in your project.If you try to use vanity url they will throw 404 until unless you haven't allowed those urls explicitly in farm files.

Try these steps- 1 # on a empty folder, as adminrun below and see-$ mvn -B archetype:generate  -D archetypeGroupId=com.adobe.aem  -D archetypeArtifactId=aem-project-archetype  -D archetypeVersion=30  -D appTitle="My Site"  -D appId="mysite"  -D groupId="com.mysite"