You can run AEM 6.5 on either Java 11 or Java 8. The merit of the post was to ensure that you're not trying to do the upgrade with Java 11, as that won't work.  The in-place upgrade needs to happen with Java 8.  Then, post-upgrade, you can determine whether to change to Java 11 or stay on Java 8.

This answer is absolutely wrong. DON'T delete /launchpad.

You can't change anything under /libs. Full stop. Immutability is enforced via a Composite Nodestore [1],/apps is a mounted nodestore/libs is another mounted nodestore that you can think of as a read-only 'golden master' Your repo init scripts can do anything under /appsBut you won't be able to do a...

RE. : Dispatcher version 4.1.0 with apache 2.2. Yikes... why so old?   

You need to capture the SAML Response from your Idp and inspect it to understand why it failed. Just capture the browser network traffic, save that traffic as a HAR file -- thenUse something like Google's HAR analyzer to inspect that traffic -- https://toolbox.googleapps.com/apps/har_analyzer/-- the...

No root cause? Authentication in via CRX DE was removed from the product and documented in the release notes.

Integrate AEM with GPT-3.  That's a massive opportunity. 

I believe the general limitation with moving launches is around the complexity in updating all the references to avoid orphaning nodes.A move operation is pretty heavy to begin with, it's not as arbitrary as one would think.    

@Theo_Pendle authored this article around render conditions that is highly relevant to your ask : https://levelup.gitconnected.com/aem-creating-custom-granite-render-conditions-28a21958f420 Cheers~Marc

You need to edit the Page Template Policies on the Layout Container to allow various Component Groups. See : https://docs.adobe.com/content/help/en/experience-manager-65/developing/platform/templates/page-templates-editable.html#page-policies