What would best practice be however? I assume best practice would be use
a JSP or Ecma to generate a dynamic JS file. Sightly is defined as being
an HTML templating system right, so if you aren't generating HTML
shouldn't you be using a different templating language?
The standard solution for this in CQ is to use Closed User Groups -
on your exact use case this may be the right approach. If you are using
dispatch you will have make some changes to dispatcher to make that work
There some pros and cons to how you go about doing this (and some issues
with the instructions). You can check out this prese...
Other asset types could work pretty much the same way - you'd have to
write your servlet and figure out how to map selectors to the page
specific renditions. Unlike the images you would not find as many helper
APIs since most people do reference their PDFs directly these days.
Still the underlying concept isn't any different. If you follow
/libs/foundation/components/parbase/img.GET.java as an example you
remove all the image specific stuff, you add the code to map selectors
to renditions (and c...
If you can get the regular expression right you could probably get the
rewrites working. Personally i have always found complex rewrites in
/etc/maps challenging to get working as expected. If you do get it
working you should be aware that your cache flushing may not work as
expected since the path in the cache won't match the path in repository.
The best solution would be to not refer to the renditions directly. As a
general rule the recommended best practice is to refer to DAM assets
through a servlet rather than directly. This gives you better control of
the URL and allows you better cache control in general. So for example
consider how the image rendering servlet in parbase works. It's image
URLs look like
The base servlet always returns the or...
I don't believe that there are grunt plugins for full spectrum of tasks
needed to build and deploy all aspects of an AEM project. If you read
excellent blog post Scott pointed to from Citytech you'll see that they
integration to running author instances). Where you'll still need to
look to Maven are the more Java related tasks like building and
compiling an OSGI bundle for example. There are a lot of tasks in
between those two item...
If you want a guarantee that your configuration is going to be globally
effective you really can't us the design mode to manage the
configuration. There are strategies you can take to reduce duplication
across templates but those are workarounds - design mode isn't intended
to hold global configurations it's intended to hold design
configurations specific to a particular location in the page or site.
With a requirement like this you'll have to create some central location
in your repository wher...
If you are referring to server visualization there isn't any AEM related
implementation details - the software is installed that same on a
virtualized server as it is on physical server. The other place in AEM
where you see the term virtual is around virtual components like the
column control components. This is a component that doesn't actual have
any code - it exists only to allow the author to drag a particular
configuration on the page. Not a lot of documentation about that - you
need to dig...