seems like the POST calls are filtered, please update your dispatcher configurations to allow the request and for your local environment you can disable the filter.

https://meet.google.com/bhz-eohe-mbg can you quickly join this bridge? @faeemazaz92 

Hey, I observed this issue earlier, back then the difference was due to core-components version on the POM file. Can you check the core-components version on the POM file?

Hey, seems like in the screenshot you are on preview mode, switch to edit mode on the right top corner to enable the side panel.

Hi @avi_infy ,   1. you need not worry about the max limit as there is a handler that takes 10 items(default) at a time and flushes the replication as a set. If I am not wrong it is a sling event job handler. 2. just point your publisher URI to your desired path and allow the author URL to take requ...

I would suggest triggering a workflow whenever an attempt is made to publish instances so as to avoid any accidental pushes.

very well explained.

if not with experience fragments, you'll have to deal with this in a complex way.At the moment I could think of creating a data node where you have all the content in the jcr:content properties – from your custom component read these properties from the node from your sling model and display them on...

yes. The best way to deal with this is with an experience fragment.More on experience fragment: https://experienceleague.adobe.com/docs/experience-manager-64/authoring/authoring/experience-fragments.html?lang=en