Archive for the ‘web’ Category

h1

Adobe CQ5.6 First Impression

February 22, 2013

Adobe released it’s new version of the Communique suite (5.6) on Feb-8-2013. The release can be download from daycare or licensing.adobe.com for current customers. So what’s new in this release that will make you want to upgrade your project?

New in CQ5.6

1: It’s called AEM (Adobe Experience Manager) now

While I guess not that important, it’s going to be interesting if the name is going to stick – there were other occasions where Adobe tried to rename this product and at the end, we all keep calling it Adobe CQ (yes, we finally don’t call it Day CQ anymore).

2: Responsive Design Support

If you download the latest release and navigate to the geometrixx-media example webpage and switch over to preview mode, you’ll see a dropdown allowing you to easily and quickly change the device that you are using to view the site. Also, the geometrixx-media example is now a nice example of a responsive design website and a good starting point for your own projects since more and more people are going the route of designing tablet-first websites.

3: Adaptive Images Support

The inclusion (in the geometrixx-media code base) of an adaptive-image component is a great addition to the component libraries available from the get-go in CQ. The adaptive image component helps you minimize the size of a page if browsing with a smaller device (mobile phone) by downloading a version of the image that matches the screen size of the device instead of using the browser to scale the image. Also, those pesky retina displays will get a different version of the image served to them leaving  a better impression with your customer.

4: Launches

One of my favorite new features in CQ (sorry ADEP (oh now, it’s called AEM now)). You can now essentially branch your site structure and work on a future version of the site while still altering the current version of the site. The branch and the current version are kept in sync over the LiveCopy functionality. You can then launch your new content – the current copy of the content is updated at that time. There feature also makes use of the workflow package concept to allow you to publish all the pages you changed in one bulk transaction.

The sidekick allows you to switch between the current content or a branch and also has the ability to promote your branch.

Note: there are some issues with the out of the box components not working right in the branched mode. An example of this is if you go to the gemoetrixx example site and branch for example the ‘products’ section off you’ll see that the navigation is not working anymore. I heard some rumors that Adobe is addressing these issues.

5: Manuscripts/Articles

There is a new concept in 5.6 of content that does not live in the regular site hierarchy – you can author the manuscripts/articles with a wiki style editor and then include them anywhere on your site (great examples in the geometrixx-media site), select how many columns you want to use for the display of these articles and also add other content/images between every paragraph. It’s a great demonstration of authoring some sort of content outside of the regular site structure and reuse of that information in multiple places.

6: Publications

5.6 now allows you to create magazines and publish them through an Adobe service to your mobile or tablet devices and the App Store. Seems to be a great new feature and I’ll defiantly will spend more time on this one to learn how it actually works. It may be a nice feature to publish an internal or external magazine for a company.

7: New Code Editor in CRXDE|lite

CRXDE|lite got a new code editor – gone are the times of grayed out code, shadows, etc. Great to  see that this issue has been addressed.

Many more Features

The official release notes can be found here. It also includes a list of the new features:

http://dev.day.com/docs/en/cq/current/release_notes/overview.html

Advertisements
h1

Adobe CQ Problem Clinic on November 7 2012

October 4, 2012

If you live in Orange County/Los Angeles or the San Diego area and work with Adobe CQ then bring your laptop, your project and your problems with Adobe CQ. We will have a session where you can present the problem you are having and we’ll discuss solutions for the problems and try to find a way to solve them to make your CQ implementations a success.

Adobe support personnel will be at the meetup to help us get through the issues.

We are meeting Wednesday November 7  from 6:30pm to 9pm at the Lake Forest/El Toro Public Library.

For more information about the meetup group and this event go to http://www.meetup.com/OC-CQ-Sling-JCR-User-Group/events/85466292/

Hope to see you there.

h1

New VLT Tool Version for CQ

May 30, 2012

I logged into package share the other day and noticed the new vault tool version has been released. You can download it through package share at this link. A quick check of the documentation reveals the new sync feature has been included into this release. For the documentation of this addition check out how to use the vlttool – Sync.

h1

Undo/Redo in Adobe CQ5.5 – What You Need to Know

April 30, 2012

CQ5.5 comes with a new undo/redo feature for page editing. You are now able to undo/redo any change that you made to a page. It’s a great new feature that however also comes with a bit of a learning curve if you want to use it correctly in your CQ project.

Any new component you write needs to be tested for undo/redo. Once tested and your satisfied it works correctly, you need to add your component to the whitelist of undo/redo components, otherwise a nasty popup will show up everytime somebody hits ctrl-z to undo any changes. To add your component to the whitelist, go to

http://localhost:4502/crx/de/index.jsp#/crx.default/jcr%3aroot/libs/wcm/core/config.author/com.day.cq.wcm.undo.UndoConfig

You’ll find a property cq.wcm.undo.whitelist, add your component to this list to make the message go away. Unfortunately, this is the only place to set this setting and may cause problems in the future when you upgrade CQ since everything in /libs may be overwritten by a hotfix.

Undo/Redo information for any text is stored in the browser either on the window or in a cookie, however, if you change an image, the information is stored in /var/undo. This only works if you have sufficient rights to store data in this location, by default, this is only granted to administrators, so regular users may not be able to undo/redo changes on images withing CQ. Also note, this may fill up the repository quickly since a copy of the image is stored in that location.

Undo/Redo can also be dangerous if multiple people work on the same page at any given time. There is no mechanism to make sure multiple users do not step on each other when making changes. Now with undo/redo, you can make large changes quickly and you may therefore alter a page in a way that you did not intend if there are other modifications from other users. You can turn undo/redo off altogether by setting the cq.wcm.undo.enabled property to false.

If you’re users don’t like the flashy style of CQ to show you what has been undone on a page, you can set the cq.wcm.undo.markermode property to select instead. This will just select the component that has been undone instead.

For more information about the undo/redo service please consult http://dev.day.com/docs/en/cq/current/administering/config_undo.html

h1

Developing the style and templates/components in parallel for Adobe CQ5

April 10, 2012

In order to speed up development of a site within CQ5, it helps adopting the following process:

  •  Devise templates and components for the site based on mockups
  •  Implement a standard HTML for all templates and components
  •  Develop the components necessary
  •  Develop CSS/JS necessary to support the components

Using this approach, the front end team can develop the CSS/JS necessary for the site in parallel with the developers implementing the components and templates for CQ5. Instead of using a waterfall model where the front end team develops the basic HTML structure first and then provides the code to the CQ5 developers, this approach makes sure the CSS/JS works well within Adobe CQ.

To further minimize the risk of browser incompatibilities and to make sure the site will also look good on mobile devices from the start, it helps adopting a basic CSS/JS framework, commonly known as grid systems.

Some grid systems to consider are:

The grid systems have a well known html structure and features such as reflow that help on smaller screens. Developing your components with a grid system in mind will also make sure the developed components can be reused in the future with a different stylesheet and make your CQ5 projects faster to implement and easier to adopt to a new site style and new features provided by the grid system.

The Adobe CQ5.5 version uses 960gs for the default geometrixx site, however, choosing twitter bootstrap will provide you with more out of the box functionality commonly found on today’s website.

update: we released a bootstrap templating integration for Adobe CQ 5.5 today. See the following link for more information

h1

Updated init script for CQ5.5

March 13, 2012

Jorg Hoh over at cqdump.wordpress.com has a nice article on how to write an init script for cq5.4 – since CQ5.5 changed a bit on how it starts/stops cq, I figured I’ll post a new version of his script that’s cq5.5 compatible

#!/bin/sh
### BEGIN INIT INFO
# Provides: cq55
# Required-Start:
# Required-Stop:
# Default-Start: 2 3 4 5
# Default-Stop: 0 1 6
# Short-Description: Start, stop adobe cq5.5
# Description: Start, stop adobe cq5.5
### END INIT INFO

CQ5_ROOT=CQROOT
CQ5_USER=CQUSER

########
SERVER=${CQ5_ROOT}/crx-quickstart
START=${SERVER}/bin/start
STOP=${SERVER}/bin/stop
STATUS="${SERVER}/bin/status"

case "$1" in
start)
su - ${CQ5_USER} ${START}
;;
stop)
su - ${CQ5_USER} ${STOP}
;;
status)
su - ${CQ5_USER} ${STATUS}
;;
*)
echo "Unknown argument $1"
;;
esac

Replace CQROOT with the folder where you installed CQ, CQUSER with the user that you want to run CQ as. I also added a header for init script management into the script file. This will allow you to use update=rc.d on ubuntu or chkconfig on centos:

ubuntu:
sudo update-rc.d -f cq55 remove


centos:
sudo chkconfig --del cq55

let me know what you think, any feedback is greatly appreciated

h1

Adobe CQ5.5, first impressions

March 10, 2012

Adobe recently released a new version of it’s content management suite, now called CQ5.5 again – there was an effort to rebrand it last year to WEM but that seemed not to go over that well and was quite confusing.

The new version of CQ comes with a much better integration into the Adobe digital marketing suite (Omniture, Test & Target, Scene 7, etc) and there seems to be quite some work that has been done under the hood.

This slideshow requires JavaScript.

CQ5.5 now comes as two distributions, a WAR file that can be deployed into any JEE servlet container as well as a standalone version that runs in the apache felix OSGi container – CQ used to be distributed as 2 war files with an embedded servlet container and to get to run it in any other container there was quite some work involved.

Unfortunately, the new release also has some downsides especially for system administrators. Lots has changed and it seems some of the features that were there before got lost. For example, you used to be able to just rename the jar file and drive the type of server (author instance or publish instance) as well as the port CQ would run on from the name (cq-publish-4503.jar would make it run on port 4503 as a public instance). Now, this feature only works if you start the jar file directly (java -jar cq-publish-4503.jar) but the installed service scripts, such as start and stop to control the server from an init.d script for example are now hardcoded to run an author on port 4502 (the default instance).

It seems the best way to install CQ5.5 at the moment is to do the following:

java -jar cq5-5.5.0.20120220-generic.jar -unpack

this will just unpack CQ into a subfolder crx-quickstart. Once that’s complete, start modifying the files in crx-quickstart/bin. You want to change the port, the run mode (type of instance you’re running) and the memory settings.

The following few lines will change the settings for you (replace $NEWPORT, $RUNMODE and $MAXMEM with your desired configuration settings:

NEWPORT=4503
RUNMODE=publish
MAXMEM=1600

sed -i.old "s/4502/$NEWPORT/" crx-quickstart/bin/*
sed -i.old "s/author/$RUNMODE/" crx-quickstart/bin/*
sed -i.old "s/-Xmx1024/-Xmx$MAXMEM/" crx-quickstart/bin/start*

Your basic start., stop and quickstart scripts should be modified, starting and stopping CQ can now be done by executing these commands on linux or mac

./crx-quickstart/bin/start
./crx-quickstart/bin/stop

on windows, you can just use

crx-quickstart\bin\start.bat
crx-quickstart\bin\stop.bat

Note of advice: make sure you use Java6 and not Java7, there are still some problems with CQ on Java7 it seems.

Also visit updated-init-script for cq5.5 for an init script that works with cq5.5