Below is the equivalent of cq:noDecoration in a JSP script (CQ component):

  1. import:
    <%@page import="com.day.cq.wcm.api.components.IncludeOptions"%>
  2. Somewhere in the JSP file/codes, insert this code:
    // BLOCK OF CODES (i.e. IF statement, etc)
    IncludeOptions.getOptions(request, true).forceSameContext(Boolean.TRUE);
    // BLOCK OF CODES (i.e. END IF statement, etc)

This is a small Adobe CQ's OSGi component for parsing URL Query String withing CQ template.

Read more: CQ OSGi Component - URL Query String Parser

It is relatively painful to deal with tabs, accordion, or carousel component. Especially when we want to enhance content author experience. Here’s a use case to illustrate to you what I meant:

  • We need to build a tabs component.
  • We want author to manage tabs’ content on the page (not via child page or a separate page).
  • We want author to drag and drop any component into any tab’s content they wish.

Read more: Hide/Show parsys on the fly with JavaScript

This article will shows you how to: one write ExtJS plugin and calls it in CQ dialog and two generating rootPath with ExtJS plugin.

We know that with xtype pathfield, we can set rootPath value to any location we want. The drawback is that it is static. If we set rootPath to /content, we fall into providing “no so good author experience” as content author needs to click through pages list to get to the desired page.

Read more: CQ Dialog - Generate dynamic rootPath with ExtJS Plugin

I'm working on a front-end project with some relatively complex UI requirements for author dialog. The author UI requires field dependency. A set of fields is shown or hidden based on a certain selection author makes. After getting a working codes finalized, I thought that it is worth sharing with the community.

Read more: How to Manage Field Dependencies in a CQ Dialog