This smells like you are trying to do something with tagging that is not appropriate. Metatags are supposed to be applied to a given resource, independent of one another, to help describe that resource. The order those tags were applied should not be relevant when describing the tagged resource.Or did I misunderstand what you want?

Go ahead and try it, but my guess is that it will not work. I know if you put a space between the comma delimited list items, it will not work. And, unfortunately the almost silent failure is that the property just simply isn't set in CRX. You'll need to pay close attention to whether your XML file was appropriately deployed as nodes/properties.Are you aware of component groups? The best practice is to place your components in groups, then specify which groups are allowed in the design. That all...

Check the init.jsp file that gets referenced in the foundation page component's head.jsp. That is where any changes in the JS that launches the sidekick would probably occur. I'm not specifically aware of any, but I wouldn't be surprised if there were some. I believe that file resides in /libs/cq/wcm/core/components/init/ or something like that.Interesting timing, because I just started a thread about a different challenge I'm having with adding additional sidekick items.

It just happens, I do. I'll link to my blog post describing the approach in more detail. But, the main gist is that you use the Apache web server to "hide" the fact that AEM (technically Sling) requires an extension on every request. In Apache you 301 redirect every version of a url (ends in .html or ends in no slash) to the version that ends with a slash. Then you use a pass-through rewrite rule that adds replaces that trailing / with a ".html" as it passes the request back through the dispatch...

I would use Collections.sort() and a custom comparator that sorts based on the Resource name (or whatever sorting logic you want). It wouldn't be appropriate, in my opinion, for Sling to sort those resources for you. It should be returning that list of resources in their natural order within the repository. This order may be the result of the order in which they were added, most recent at the bottom. They may have a specific order, as do some nodes in the JCR if their parent specifies that they ...

I significantly doubt if what you're asking is easy or even possible.However, you could use an alternative approach if you're using Maven to build your projects. We've used a setup where the Maven build compiles the LESS files into CSS, before putting them into CRX as part of the clientlib. So our clientlib is defined to use CSS files that don't technically exist until compilation, then Maven creates them. Both the LESS and CSS files are deployed to CRX, but the LESS files are really only there ...

I've not dug into the 5.6 version of the blog component yet, but I have quite a bit of experience with the pre-5.6 version. To be honest, it's a feature that I've had some struggles with extending or customizing, but they seem to be making improvements version to version. For this reason, I would recommend using whatever is most recent.Make sure to ensure that your licensing supports use of this component, though. Sometimes that can get a little tricky.