CQ5 Application/Project

Get Started. It's Free
or sign up with your email address
Rocket clouds
CQ5 Application/Project by Mind Map: CQ5 Application/Project

1. Store CQ5 elements

1.1. Templates

1.1.1. -Used to create a page

1.1.2. -Defines which components can be used within the scope

1.1.3. -Same structure as page, but without content

1.1.4. -Present you with the collection of available components to use

1.2. Componenets

1.2.1. -Use and allow access to widgets

1.2.2. Component Context

1.2.2.1. Add <%@include file-"/lib/foundation/global.jsp%> to JSP

1.2.2.1.1. Best Practice: Create your own equivalent of global.jsp under /apps and include this.

1.2.2.1.2. Ways to access content

1.2.2.2. Scripting Objects

1.2.2.2.1. ComponentContext

1.2.2.2.2. Component

1.2.2.2.3. CurrentDesign

1.2.2.2.4. CurrentPage

1.2.2.2.5. CurrentNode

1.2.2.2.6. CurrentStyle

1.2.2.2.7. Designer

1.2.2.2.8. EditContext

1.2.2.2.9. PageManager

1.2.2.2.10. PagePeroperties

1.2.2.2.11. Peroperties

1.2.2.2.12. Resource

1.2.2.2.13. ResourceDesign

1.2.2.2.14. ResourcePage

1.3. OSGi bundles

1.4. Static files

2. Recommended Structure

2.1. /apps

2.1.1. /<application name>

2.1.1.1. components

2.1.1.1.1. pages

2.1.1.2. templates

2.1.1.2.1. <template name>

2.1.1.3. src

2.1.1.4. install

3. Web Applications

3.1. Modularization & Reuse

3.1.1. Compile Time

3.1.1.1. JSP include: <%@ include file="myScript.jsp" %>

3.1.1.1.1. Include a complete file into the current file

3.1.2. Run Time

3.1.2.1. CQ include: <cq:include script="myScript.jsp"/>

3.1.2.1.1. Include by script name using its attribute

3.1.2.2. Sling include: <sling:include resource="%=par%"/>

3.1.2.2.1. Script resolution using selectors and extensions

3.2. Initialize the WCM

3.2.1. <cq:include script=”/libs/wcm/core/components/init/init.jsp”/>

3.2.1.1. Dialogs

3.2.1.2. Widgets

3.2.1.3. WCM CSS& JS

3.2.1.4. SideKick

3.3. Component Hierarchy and Inheritance

3.3.1. Resource Type Hierarchy

3.3.1.1. using the property sling:resourceSuperType

3.3.1.1.1. enables the Component to inherit from a “base” Component

3.3.2. Container Hierarchy

3.3.2.1. used to populate configuration settings to the child component

3.3.2.1.1. cq:editConfig and cq:childEditConfig are propagated

3.3.2.2. used in a paragraph system scenario

3.3.3. Include Hierarchy

3.3.3.1. imposed at runtime by the sequence of includes

3.4. The Design(er)

3.4.1. allows you to enforce a consistent look and feel across your Web site

3.4.2. share global content

3.4.3. access to common CSS files, defining the formats of specific areas/Components, and images that you use for features

3.5. not page-rendering components

3.5.1. Component

3.5.1.1. properties

3.5.1.2. Child node to control rendering

3.5.1.2.1. cq:editConfig

3.5.1.2.2. cq:childEditConfig

3.5.1.2.3. dialog

3.5.1.2.4. design_dialog

3.5.1.3. Logging Messages

3.5.1.3.1. Enabling the Debugger

3.5.1.4. ExtJs

3.5.1.4.1. widget library used by CQ5

3.5.1.4.2. create Rich Internet Applications (RIA) through the use of AJAX.

3.6. Paragraph System

3.6.1. The paragraph system is the main content area of a web page

4. Workflow

4.1. Steps

4.1.1. Participant (User/Group)

4.1.2. Process (Script, Java method call)

4.1.3. Container (Sub Workflow)

4.1.4. OR Split/Join

4.1.5. AND Split/Join

4.2. Transition

4.2.1. Defines the link between two consecutive steps.

4.2.2. It is possible to apply rules to the Transition.

4.3. WorkItem

4.3.1. is the “there is a task identifier”

4.3.2. is put into the respective inbox

4.4. Payload

4.4.1. References the resource that has to be advanced through a workflow

4.5. Lifecycle

4.5.1. Possible actions

4.5.1.1. Terminate

4.5.1.2. Suspend

4.5.1.3. Resume

4.5.1.4. Restart

4.6. Inbox