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"

AEM 5.6 does not support JVM 8.x as per the official document.To download the documentation u should have access to software distribution that admin can help you.

Upgrade the core jar to 2.17- I could see below code in 2.15 jar- public class EnhancedRendition extends ResourceWrapper implements Rendition {private static final Logger LOG = LoggerFactory.getLogger(EnhancedRendition.class);private Rendition rendition;private Dimension dimension;private boolean di...

Use below api's- https://www.adobe.io/experience-manager/reference-materials/6-5/javadoc/com/adobe/cq/launches/api/package-summary.html <!-- https://mvnrepository.com/artifact/com.adobe.cq/cq-launches-api --><dependency><groupId>com.adobe.cq</groupId><artifactId>cq-launches-api</artifactId><version>...

For me this number"The query read or traversed more than 10000 nodes. To avoid affecting other tasks, processing was stopped" doesn't seems to be that large and u can try increasing the limit- http://localhost:4502/system/console/jmx/org.apache.jackrabbit.oak%3Aname%3Dsettings%2Ctype%3DQueryEngineSe...

Could u pls check these threads- https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/the-query-read-more-than-500000-nodes-in-memory/m-p/294303 https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/the-query-read-or-traversed-more-than-100000-nodes-to-avoid/...

I am not very sure but as per the doc it works only on AEM as a cloud service- https://experienceleague.adobe.com/docs/experience-manager-learn/getting-started-with-aem-headless/graphql/multi-step/setup.html?lang=en But still i am not very sure.

It is working as expected- https://aemcomponents.dev/content/core-components-examples/library/page-authoring/content-fragment-list.html If you want the variations you need to extend the content fragment list component and update the model as per ur requirement