Will the blog posts be composed on author instance by content authors?If yes, then sure you can use CF. You can create a CF model with whatever fields you require (e.g. title, body, etc.)https://www.youtube.com/watch?v=-Hn3UDJMc98 - tutorial on CF models.Better idea maybe to just create a component ...

Hello,  I went through lot of the XF documentation and I understand how to create it, etc. But I'm still not fully sure when and where it'll be a good idea to use it. Anyone have any examples of XF usage in their projects or has thoughts on use cases where XF would be a good solution to use? Thanks ...

Hello,  In our DTM implemention, we've got many custom Rule Conditions which contains jQuery / raw javascript code and also few _sattelite calls.  Will this be migrated as is if we migrate to launch using the "Upgrade to Launch" option? Or will any manual work b required here? Thanks.

Thanks. In this case (approach B) how do you find which data is lost and what'd be the best way to restore that?

This helps a lot thanks.

As given in all the documentation, the solution to TarMK corruption is to run the 'check' run-mode on oak-run jar and revert the repository to the last known good revision by making changes to journal.log.But doing this would wipe out some of the recent data from the repository. Is there a way to kn...

Thanks. This is what I was looking for thank you

Thanks Hamid. The documentation doesn't answer question raised in the original post. i.e. If a servlet is expected to return HTML content, should we (the site developer) be using AntiSamy API to filter out problematic content? Or is that already addressed somewhere in AEM request / response chain?

Is AEM completely xss secure. I know using HTL makes sure that you're protected from xss. But what about ajax calls? Responses returned from Servlets? In other words, are there areas or flows where it's up to the site developer to implement xss protection mechanisms?Thanks.

Thanks for the reply. But I'm still getting the same error even after this change.