Archive for October, 2011

October 25, 2011

How to add components to the sidekick without updating the design dialog.

To add components to the sidekick for use with a parsys component without updating the design dialog, the following steps can be taken.

1. Locate your “par” component in the design for your site.

2. If a property “components” of type String[] doesn’t exist, add it.

3. If the property already exists, update the value to add the path to your component to the list.

4. That should be it.



10:27 AM Permalink
October 24, 2011

Where is that user-posted-data stored?

CQ users might come across the question of where the data is stored when you have a custom component which accepts user inputs. Let’s use the following as an example:


If I have the above form inside a paragraph system and the radio group is set like the following:

Then once the user submits the form, the data is generated into CRX at the /content/usergenerated folder. For the example above, it is stored at:

And of course, the data would look something like:

12:05 PM Permalink

Content(ment) Management.

I have been working as a Content Management professional for almost four years and have worked with over ten clients primarily on the Vignette product stack and a few short ones on the FatWire product stacks.

I still remember my first project in early 2008 at a very disgruntled client. They had been using the product for a while and the implementation had gone horrendously bad with one company, so they decided to show them the door and have us come and do the work. Although, they had kicked out the previous company, they forgot to kick out their grievances. As a fresh graduate, this was quite a shocker for me, I kept thinking how can someone be spending hundreds and thousands of dollars and still be so unhappy with the end result.

Since then I have worked with many other clients, none of whom have been really happy with their CMS implementations. Everyone just learns to get used to it, and, find ways to get things working. Whether its the correct (read supported) way or not.

After my first couple of projects, I always thought that life would be so much easier for us technical consultants and cheaper for clients if there was an offering where the content would be stored in a central location and there were ways to build applications around that to achieve exactly what the clients wanted. I always believed having a standardized approach around content management was the way to go.

You can now imagine why being hired by Adobe as a CQ consultant is like a dream come true for me. I can’t wait for my life to be “easier” as a Content Management professional.

12:02 PM Permalink

How to create a simple footer navigation(toolbar) component

In a technical discussion two days ago, I was questioned on how to create a footer navigation component like the following:

The simplest answer and the ideal solution to the above is to use the OOTB Toolbar component. The Toolbar component can be added to a page using the following:

<cq:include path="toolbar" resourceType="foundation/components/toolbar" />

Nothing else. It’s that easy! And once the above is added, the page would yield a component where you can configure the following:

Editing the foundation toolbar component

Editing the foundation toolbar component

For more info please refer to the Default Components documentation.

11:25 AM Permalink
October 21, 2011

Hello World

Hello there! Well I always wanted to set up a blog for work all these years, and I finally got to do so here at Adobe.

First of all, a little background about myself:

  • I have been in the content management systems (CMS) field since 2004.
  • My previous life was with the suite of Vignette / OpenText applications.
  • I have substantial experience in Vignette Portal and CMS (VCM) implementations across different industries – Media, Retail, Pharmaceutical, Travel, Government.
  • I am relatively new to CQ / CRX / Apache Sling / Apache Felix / OSGi / JSR-170 / JSR-283….
Thus the purpose of this blog! I hope to share my journey in learning and applying the technologies mentioned in the last bullet point above. And with my previous field experiences, I also would like to take a close scrutiny of the strengths and/or weaknesses of CQ/CRX in comparison with other CMS products. Hopefully whatever I document here will eventually become something useful and beneficial to the CQ development community, or anyone who’s planning to jump on the CQ-wagon.
9:56 AM Permalink