You can use Manage Publication or even create package of the entire site on your instance and deploy it on other environments. The following doc may be helpful in publishing sites/pages:https://docs.adobe.com/content/help/en/experience-manager-65/authoring/authoring/publishing-pages.html The followi...

The following may be helpful:* https://docs.adobe.com/content/help/en/experience-manager-64/developing/extending-aem/customizing-content-fragments.html#examples* https://gist.github.com/dfparker2002/c4a15f9ab6ac0d54dc33cfeca502ca7a

Uninstalling SPs and CFPs is unsupported. However, if you must revert it and do not have a backup, try this:1. Backup your AEM instance2. Package up the /libs folder from another working environment and installing it to the post-CFP environment.  Note that you must also make sure to package and inst...

You can reach out to the person in your organization who has admin access in the Admin Console(Org Administrator), such that they can add you to the solution, or raise a case with Admin Console support team, if you still run into any such issues.

Check the ACLs on that node in crx.If there's no deny ACL for the user that you want to deny, add one(such as deny on jcr:All), and then verify whether that user still sees the option to use custom workflow. The following doc may be helpful:https://docs.adobe.com/content/help/en/experience-manager-6...

The following documents may be helpful:1) https://felix.apache.org/documentation/subprojects/apache-felix-maven-bundle-plugin-bnd.html2) https://docs.adobe.com/content/help/en/experience-manager-64/developing/devtools/ht-projects-maven.html#common-development-tasks-with-maven

I also remember something. They had to make some changes according to QueryBuilder API for 6.5 to get the desired results.

Try reindexing that index. It helped resolve the case for one of my customers. They had somewhat similar scenario of migration from 6.3 to 6.5 and issues in retrieving the correct number of records using the QueryBuilder API with their custom index.

@AEM_Dev_Newbie Try it in a different browser then... Don't use Chrome (83.0.4103.61) for package management activities... 

@BrianKasingliThe UI seems fine for me. Try opening your AEM in Incognito Window or other browser. You might be seeing weird icons due to Chrome's caching issues. The UI is appearing fine for me on the latest version of Chrome.