OOTB a page deletion on an AEM author also unpublishing the page. You can easily build your solution by using workflows:Request for Deactivation - /etc/workflow/models/request_for_deactivationRequest for Deletion - /etc/workflow/models/request_for_deletion

What version of AEM do you use? Do you see in a log file an output similar to "*WARN* Traversed 1000 nodes with filter Filter.."?

You should not create pages under /etc. All pages should exist only under /content.

Mojave OS is not officially sported for AEM 6.2 - Technical Requirements The meaning of the error is that the repository is not available, and Authentication Service is just a first service that is going to be called. You should try to run offline compaction along with a full re-indexing.  Also, mak...

Classic UI is still supported in AEM 6.4.Keep in mind that most of the new features have been designed only for TouchUI and those do not exist in Classic UI.

Try to force CSS and JS recompile on your publish AEM instance:How to force a recompilation of all Sling scripts jsps, java, and sightly in AEM 6.4

Can you verify that an "oauth" node exists under dam-update-service user?You can also try to recreate a cloud service configuration. To delete an existing one, you can remove a relevant node under /etc/cloudservices/smarttagging/

Please try steps from How to force a recompilation of all Sling scripts jsps, java, and sightly in AEM 6.4 to fix the issue.

You can use CRXDe to replicate the index. See an example:

It depends on a persistent store and topology.You can have multiple authors if you are using MongoMK. Here you can have multiple author's instances connected to the same Mongo DB replica set. Such a topology is recommended for a high number of concurrent (>100) author's connections.For TarMK you can...