There is a acs-commons tool for managing oak index. Can check that also. https://adobe-consulting-services.github.io/acs-aem-commons/features/ensure-oak-index/index.html

If the request is passing through cdn and dispatcher, can check if cookie header is allowed

on spa there is not need of data sly use. Because front end is not Sightly there. On SPA you send all the props to react/angular side. And based on the props show hide logics are on angular/react.Generally on spa we expose all the props to react or call a servlet for backend data

yes, those extra properties are there because we are using acs commons ensure oak index.

yes same for author and publisher.and we don't change content fragments programmatically. Only the author changes the content fragments.

We are using a lot of content fragment on our aem 6.5 project. On backend we do search for content fragment based on path and datetime combination. Recently we have added a custom property oak index only for our content fragments. From the query performance tool we checked that query is picking prop...

Workflow will be the best option. From my experience event listener is sometimes missed, especially when bulk operations are performed. Another advantage of workflow is you can check which workflow is running, aborted, and finished. But for event listeners, you only have to check log. And if you wri...

Can you please give some more details on retirement? its too short to understand. What to you mean by camera row?

There is a long discussion and here https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/multifield-in-content-fragment-model/td-p/246514 Please check this link. And its not possible unless you develop something like it

Yes that's the expected behavior. But you can set a default value from cq_design_dialog. Then you have to combine value of cq_design_dialog and the dialog one. For example<?xml version="1.0" encoding="UTF-8"?> <jcr:root xmlns:sling="http://sling.apache.org/jcr/sling/1.0" xmlns:jcr="http://www.jcp.o...