James Leong | Web Developer

Hmm.. have been working with CMS for all these years.. but never seemed to have heard of this supposed CMS jargons, i.e. frying and baking…

http://dev.day.com/content/docs/en/cq/current/exploring/concepts.html

In CMS jargon, "baked" refers to the concept of committing data to static files at publish-time, while "fried" refers to the concept of processing data for final presentation at request-time.

Well, kind of rounding up my playing with SAN and ZFS until my new hardware arrives from the States.

First thing I did was to download the CRX jar file.  From there I kind of got to the Web UI for the CRX repository.

First Steps

Screencast to get started

http://dev.day.com/ddc/blog/2008/04/firststeps1/docroot/firststeps1.html

Objectives to achieve

a.  Posting to a JCR Path, i.e. /content/firststeps

b.  Reading with Sling

c.  Posting with a * (implies item list)

d. Special input properties, i.e. created, createdBy, lastModified, lastModifiedBy

e.  Accessing a collection of nodes

f.  Listing through javascript template, jst file.

Well couldn’t quite get point f to work… but anyhows.. here are some simple html files to save the next guy from typing all over again…    they should have provided for a file download link for the source…

http://james.com.sg/wp-content/uploads/2011/04/FirstSteps.zip

After typing in all the example… then I realise that FirstSteps is kind of installed with CRX and is available at:

http://localhost:7402/apps/firststeps/0_hello.html

Sigh..

CQ WebDAV URL

http://localhost:7402/crx/repository/crx.default

Avenues of working with CRX

Screencast:

http://www.day.com/day/en/products/crx.html

Avenues of Working

• Subversion (
  • http://code.google.com/p/crxzon/ – Checkout both the App (OSGI Bundle) and Products)
  • CRXDE Lite

Products checkout is over 6Mb.  Will have to stare at the blank screen for a long time as there is no ajax status message.

Interesting to note that… the labelling of all the product attributes is through a xml file at the root of the subversion tree, i.e.

Different Renditions

CRX allows different renditions to be hooked to the content type, i.e.

• Txt, View  – By Default
• Html – Needs to point to a sling:resourceType

Packaging

Allows selective packaging of both content and application codes into an easily deployable zip file.

Sample Application Blog

http://dev.day.com/content/docs/en/crx/current/developing/developers_getting_started.html