No, it is not mentioned in release note. Just wanted to confirm on this static template since AEM is going to depreciate classic UI, maybe starting from AEM 6.5.

Is this mentioned in adobe documentation ? if yes, can you please share it?

We are planning to migrate from AEM 6.4 to AEM 6.5 with in-place upgrade. what are the key areas that we would need to give a focus during migration. Is there any guidance from adobe ?

I heard that static template is going to be depreciated and it will be no longer available in AEM 6.5 and it will compatible only with editable template. is that true? Basically I would want to know whether static template will be compatible in AEM 6.5 and also when Adobe is planning to deprecate it...

Can this be done without a servlet ? there is no complex in backend. just want to prefix some hard coded value /hardcodevalue/{dialogvalue}

No, I am not string the value in different location. same place with hard coded prefix value.

We want to get the input from page dialog(multifield) and add some prefix string(hardcode) before store the value in node. like /hardcodevalue/{dialogvalue} and store the value in node. Can we use any listeners to do this or what is the approach that should follow? please share any reference.

Yes, change allowedPaths value from /content(/.*)? to /content(yourProjectarea)? 

I have the similar requirement. Can you tell how have you done with afteredit or cq:listners?

Yeah but this /vanity_urls filter is not the filtering the vanity URLs that get stored in /temp/vanity_urls file. I could see the vanityURLS in {dispurl}/libs/granite/dispatcher/content/vanityUrls.html What happens here is, if I hit the vanity URL like - {dispURL}/vanity1, then rewrite rule comes in...