You should create a rollout task (script or java classes) to fix(otherwise your existing content will be broken) all changes according to certain criteria (for example all content under this path-/content/myapp/myfolder/- must add this new property -newProperty=false- to ensure all pages render prop...

In addition to feike_visser, you can check the documentation and spec: HTL Block Statements htl-spec/SPECIFICATION.md at master · Adobe-Marketing-Cloud/htl-spec · GitHub https://docs.adobe.com/content/ddc/en/gems/introduction-to-sightly/_jcr_content/par/download/file.res/Sightly%20Componen… Best Reg...

Can you check where pointing docroot? Can you also how is it implemented each component used, for example, you should check if you have any request no cacheable or not?You should also review the cache strategy for all js/css included in your clientlib.

you can check how to use  development tools for AEM project(create a node, debug, etc): Development Tools Some examples: Getting Started with AEM Sites Part 1 - Project Setup Getting Started with AEM Sites Part 2 - Creating a Base Page and Template  (you can see on this page a video creating node-te...

Between jsp and html first priority goes to jsp as by default a component is linked to jsp at the time of creation.Here you can see a very clear explanation about sling resolution, selector, extension with examples.http://www.aemcq5tutorials.com/tutorials/sling-resource-resolution-aem/

I recommend following some of the ideas suggested by Jörg Hoh for exception situation, otherwise, you should have to create something custom but it won't be easier.Best RegardsDiego

As @Veena_07 said, any publication generates a new version of the content, besides you, can also manually generate more version of the content. In term of restoring, you only have to pick the version that you need, and then publish the version selected otherwise the previous content will stay in pub...

An easy solution could be something like this(I have done several times):Automated nightly(scheduled) job to back -content / assets / source - (specific paths)  from one Author to another environment.  Basically, We created a Scripts which nightly runs "automated' from Jenkins; run package:  prepar...

as smacdonald2008 and feike_visser said, you have to make sure both instances are the same, hence your local environment must have SP1 (if that the case)make sure also in term of configuration all instances are same as well.

Did you add the new clientlib  with other one(thru: data-sly-use.clientlib) and also declare in your template(data-sly-call="${clientlib.all....) ?Otherwise, you won't be using the clientlib until included in your sightly.