Customizing and Extending CQ DAM

4/5/2016
Customizing and Extending CQ DAM - docs.adobe.com
Adobe (www.adobe.comhttp://www.adobe.com/go/gnav_adobe_logo_en_us)
Products (www.adobe.comhttp://www.adobe.com/go/gnav_products_en_us) Solutions (www.adobe.comhttp://www.adobe.com/go/gnav_solutions_en_us) Learning
(www.adobe.comhttp://www.adobe.com/go/gnav_learning_en_us) Help (www.adobe.comhttp://www.adobe.com/go/gnav_help_en_us) Downloads
(www.adobe.comhttp://www.adobe.com/go/gnav_downloads_en_us) Company (www.adobe.comhttp://www.adobe.com/go/gnav_company_en_us)
Store (www.adobe.comhttp://www.adobe.com/go/gnav_store_en_us)
Adobe Store (www.adobe.comhttp://www.adobe.com/go/gnavtray_store_en_us) for home and home ofce
Education Store (www.adobe.comhttp://www.adobe.com/go/gnavtray_store_education_en_us) for students, educators, and staff
Business Store (www.adobe.comhttp://www.adobe.com/go/gnavtray_store_business_en_us) for small and medium businesses
Other ways to buy (www.adobe.comhttp://www.adobe.com/go/gnavtray_store_otherwaystobuy_en_us)
Overview (www.adobe.com/docs/en.html) /AEM 5.6.1 (www.adobe.com/docs/en/cq/5-6-1.html) /Working with Digital

Assets in DAM (www.adobe.com/docs/en/cq/5-6-1/dam.html) /
Customizing and Extending CQ DAM

You are reading the AEM 5.6.1 version of Customizing and Extending CQ DAM.
This version has reached End of core support. For further details see our technical support periods
(www.adobe.comhttps://www.adobe.com/support/products/enterprise/eol/eol_matrix.html#cq) .
This documentation is also available for the following versions: Adobe Experience Manager 6.1
(www.adobe.com/docs/en/aem/6-1/develop/extending/assets.html) AEM 6.0 (www.adobe.com/docs/en/aem/60/develop/extending/assets.html) AEM 5.6 (www.adobe.com/docs/en/cq/56/dam/customizing_and_extendingcq5dam.html) CQ 5.5 (www.adobe.com/docs/en/cq/55/dam/customizing_and_extendingcq5dam.html) CQ 5.4 (www.adobe.com/docs/en/cq/54/dam/customizing_and_extendingcq5dam.html) CQ 5.3 (www.adobe.com/docs/en/cq/53/dam/customizing_and_extendingcq5dam.html)
The Asset Share and Asset Editor are the primary points of access that users of a CQ website will use to nd, view, and
manipulate the digital assets in your repository.
As a CQ developer, you can customize and extend the Asset Share and Asset Editor in a number of ways, presenting
users with a specically tailored interface and set of functionality.
The following aspects of the functionality can be customized or enhanced:
Look and Feel
Predicates
Lenses
Actions
Editors
Renditions
Asset Processing
Customizing the Look and Feel

The following aspects of the look and feel of the Asset Share and Asset Editor are customizable:
Logo: You can add your own organization's logo to the interface.
Colors and Fonts: You can change the colors and fonts used in the interface.
HTML Code: For more thorough customization you can change the underlying HTML code that denes the
interfaces.
Customizing Asset Share

The Asset Share page is used to search for assets based on their metadata. You can customize the search, search
results, and what actions users can take.
Creating an Asset Share Template

Geometrixx Sample Page: /content/geometrixx/en/press.html
Sample Template: /apps/geometrixx/templates/assetshare
Sample Page Component: /apps/geometrixx/components/assetshare
Conguring Clientlib
DAM components use an extension of the WCM edit clientlib. The clientlibs are usually loaded in init.jsp.
Compared to the default clientlib loading (in core's init.jsp), a DAM template must have the following:
The template must include the cq.dam.edit clientlib (instead of cq.wcm.edit).
The clientlib must also be included in disabled WCM mode (for example, loaded on publish) to be able to render
the predicates, actions, and lenses.
In most cases, copying the existing sample init.jsp (/apps/geometrixx/components/assetshare/init.jsp) should meet
these needs.
Additional Style Sheets
https://docs.adobe.com/docs/en/cq/5-6-1/dam/customizing_and_extendingcq5dam.html
1/8
4/5/2016

Some of the DAM components use the CQ widgets library. To be rendered properly in the content context, an
additional style sheet has to be loaded. The tag action component requires one more.
1
<linkhref="/etc/designs/geometrixx/ui.widgets.css"rel="stylesheet"type="text/css"
Code samples are intended for illustration purposes only.
Geometrixx Style Sheet

The sample page components require all selectors to start with .assetshare of static.css
(/etc/designs/geometrixx/static.css). Best practice: Copy all .assetshare selectors to your style sheet and adjust the
rules as desired.
Query Builder
The Geometrixx sample page includes the default DAM query builder component
(/libs/dam/components/assetshare/querybuilder) with two columns (in
/apps/geometrixx/components/assetshare/body.jsp):
left column for predicates and actions
right column for the lens deck that displays the current lens
top bar with search eld, paging, and lens switcher
To achieve one of the following, you have to create (and include) your own component:
dierent layout
dierent default values for the Query Builder, for example, limit (It is possible to set the values available in the
Query Builder Properties dialog box. The default values are only applied as long as no values have been set.)
The best practice is to copy the existing component to your project folder in /apps and adjust it.
Customizing Search
CQ DAM comes with a set of predened predicates that can be used to customize an Asset Share page. Customizing
an Asset Share in this way is covered in Creating and Conguring an Asset Share Page
(www.adobe.com/docs/en/cq/5-6-1/dam/creating_and_conguringdamnderandasseteditorpages.html#par_title) .
In addition to using pre-existing predicates, CQ developers can also create their own predicates using the Query
Builder API (www.adobe.com/docs/en/cq/5-6-1/dam/customizing_and_extendingcq5dam/query_builder.html) .
Adding custom predicates

Creating custom predicates requires basic knowledge about the CQ widgets framework
(www.adobe.com/docs/en/cq/5-6-1/widgets-api/index.html) .
The best practice is to copy an existing predicate and adjust it. Sample predicates are located in
/libs/cq/search/components/predicates.
Example: Build a simple property predicate

To build a property predicate:
1. Create a component folder in your projects directory, for example
/apps/geometrixx/components/titlepredicate.
2. Add content.xml:
1
2
3
4
5
6
7
<?xmlversion="1.0"encoding="UTF8"?>
<jcr:rootxmlns:sling="http://sling.apache.org/jcr/sling/1.0(www.adobe.comhttp://sling.apache.org/jcr/sling/1.0)
jcr:primaryType="cq:Component"
jcr:title="TitlePredicate"
sling:resourceSuperType="foundation/components/parbase"
allowedParents="[*/parsys]"
componentGroup="Search"/>
3. Add titlepredicate.jsp.
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
<%
Sampletitlepredicatecomponent
%><%@pageimport="java.util.Calendar"%><%
%><%@includefile="/libs/foundation/global.jsp"%><%
StringelemId="cqpredicate"+Long.toString(Calendar.getInstance().getTimeInMillis())
%><divclass="predicatebox">
<divclass="title">Title</div>
<%Thewrapperfortheformelements.Allitemswillbeappendtothiswrapper.
<divid="<%=elemId%>"class="content"></div>
</div><scripttype="text/javascript">
2/8
4/5/2016

19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
CQ.Ext.onLoad(function(){
varpredicateName="property"
varpropertyName="jcr:content/metadata/dc:title"
varelemId="<%=elemId%>"
//GetthepagewideavailableQueryBuilder.
varqb=CQ.search.Util.getQueryBuilder()
//createIdaddsacountertothepredicatenameusefulincasethispredicate
//isinsertedmultipletimesonthesamepage.
varid=qb.createId(predicateName)
//Hiddenfieldthatdefinesthepropertytosearchforinourcasethis
//isthe"dc:title"metadata.Thename"property"(or"1_property","2_property"etc.)
//indicatestheservertousethepropertypredicate
//(com.day.cq.search.eval.JcrPropertyPredicateEvaluator).
qb.addField({
"xtype":"hidden",
"renderTo":elemId,
"name":id,
"value":propertyName
})
//Thevisibletextfield.Thenamehastobeliketheoneofthehiddenfieldabove
//plusthe".value"suffix.
qb.addField({
"xtype":"textfield",
"renderTo":elemId,
"name":id+".value"
})
//Dependingonthepredicateadditionalparametersallowtoconfigurethe
//predicate.Hereweaddanoperationparametertocreatea"like"query.
//Againnotethenamesettotheidandasuffix.
qb.addField({
"xtype":"hidden",
"renderTo":elemId,
"name":id+".operation",
"value":"like"
})
})
</script>
4. To make the component available, you need to be able to edit it. To make a component editable, in CRXDE, add
a node cq:editCong of primary type cq:EditCong. So that you can remove paragraphs, add a multi-value
property cq:actions with a single value of DELETE.
5. Navigate to your browser, and on your sample page (for example, press.html) switch to design mode and enable
your new component for the predicate paragraph system (for example, left).
6. In Edit mode, the new component is now available in the sidekick (found in the Search group). Insert the
component in the Predicates column and type a search word, for example, Diamond and click the magnifying
glass to start the search.
NOTE
When searching, be sure to type in the term exactly, including the correct case.
Example: Build a simple group predicate

To build a group predicate:
1. Create a component folder in your projects directory, for example
/apps/geometrixx/components/picspredicate.
2. Add content.xml:
1
2
3
4
5
6
7
jcr:title="ImageFormats"
componentGroup="Search"/>
3. Add titlepredicate.jsp:
1
2
3
4
5
6
<%
Samplegrouppredicatecomponent
%><%@pageimport="java.util.Calendar"%><%
3/8
4/5/2016

6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
StringelemId="cqpredicate"+Long.toString(Calendar.getInstance().getTimeInMillis())
%><divclass="predicatebox">
<divclass="title">ImageFormats</div>
<%Thewrapperfortheformelements.Allitemswillbeappendtothiswrapper.
<divid="<%=elemId%>"class="content"></div>
</div><scripttype="text/javascript">
CQ.Ext.onLoad(function(){
varpredicateName="property"
varpropertyName="jcr:content/metadata/dc:format"
varelemId="<%=elemId%>"
//GetthepagewideavailableQueryBuilder.
varqb=CQ.search.Util.getQueryBuilder()
//CreateauniquegroupIDwillreturne.g."1_group".
vargroupId=qb.createGroupId()
//Hiddenfieldthatdefinesthepropertytosearchforinourcase"dc:format"
//anddeclaresthegroupofpredicates."property"inthename("1_group.property")
//indicatestotheservertousethe"propertypredicate"
//(com.day.cq.search.eval.JcrPropertyPredicateEvaluator).
qb.addField({
"xtype":"hidden",
"renderTo":"<%=elemId%>",
"name":groupId+"."+predicateName,//1_group.property
"value":propertyName
})
//DeclaretocombinethemultiplevaluesusingOR.
qb.add(newCQ.Ext.form.Hidden({
"name":groupId+".p.or",//1_group.p.or
"value":"true"
}))
//Theoptions
varoptions=[
{"label":"JPEG","value":"image/jpeg"},
{"label":"PNG","value":"image/png"},
{"label":"GIF","value":"image/gif"}
]
//Buildacheckboxforeachoption.
for(vari=0i<options.lengthi++){
qb.addField({
"xtype":"checkbox",
"renderTo":"<%=elemId%>",
//1_group.property.0_value,1_group.property.1_valueetc.
"name":groupId+"."+predicateName+"."+i+"_value",
"inputValue":options[i].value,
"boxLabel":options[i].label,
"listeners":{
"check":function(){
//Submitthesearchformwhenchecking/uncheckingacheckbox.
qb.submit()
}
}
})
}
})
your new component for the predicate paragraph system (for example, left).
6. In Edit mode, the new component is now available in the sidekick (found in the Search group). Insert the
component in the Predicates column.
Customizing Search Results

The presentation of search results on an Asset Share page is governed by the selected lens.CQ DAM comes with a set
of predened lenses that can be used to customize an Asset Share page. Customizing an Asset Share in this way is
covered inCreating and Conguring an Asset Share Page (www.adobe.com../../../../../../../docs/en/cq/5-61/dam/creating_and_conguringdamnderandasseteditorpages.html#par_title) .
In addition to using pre-existing lenses, CQ developers can also create their own lenses.
Customizing Actions
CQ DAM comes with a set of predened actions that can be used to customize an Asset Share page. Customizing an
4/8
4/5/2016

Asset Share in this way is covered inCreating and Conguring an Asset Share Page
(www.adobe.com../../../../../../../docs/en/cq/5-61/dam/creating_and_conguringdamnderandasseteditorpages.html#par_title) .
In addition to using pre-existing actions, CQ developers can also create their own actions.
Adding a custom action

Creating custom actions requires basic knowledge about the CQ widgets framework (www.adobe.com/docs/en/cq/5-61/widgets-api/index.html) .
The best practice is to copy an existing action and adjust it. Sample actions are located in
/libs/cq/dam/assetshare/components/actions. See also Developing components (www.adobe.com/docs/en/cq/5-61/developing/components.html) .
Example: Create a simple action

To create a custom action:
1. Create a component folder in your projects directory, for example,
/apps/geometrixx/components/sampleaction.
2. Add content.xml:
1
2
3
4
5
6
7
jcr:title="ImageFormats"
componentGroup="AssetShare"/>
3. Add sampleaction.jsp:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
<%
Sampleactioncomponent
%><%@includefile="/libs/foundation/global.jsp"%>
<scripttype="text/javascript">
//Note:Functionsshouldbedefinedinaglobalscriptblock.Thescriptinside
//thecomponentwillbeloadedineveryparagraphthatusesthiscomponent.
//alertthetitleandpathoftheselectedassets.
functionalertSelectedAssets(){
varselection=CQ.search.Util.getSelection()
if(selection.length==0){
CQ.dam.Util.alertNoSelection()
return
}
varmsg=""
for(vari=0i<selection.lengthi++){
msg+="Title:"+selection[i]["jcr:content"]["metadata"]["dc:title"]+"\n"
msg+="Path:"+selection[i]["jcr:path"]+"\n\n"
}
alert(msg)
}
</script>
<ahref="javascript:alertSelectedAssets()">SampleAction</a>
your new component for the predicate paragraph system (for example, actions).
6. In Edit mode, the new component is now available in the sidekick (found in the Asset Share group). Insert the
component in actions area.
Customizing Editors
The Asset Editor is the page that opens when an asset found through the Asset Share is clicked allowing the user to
edit such aspects of the asset as metadata, thumbnail, title and tags.
Conguration of the editor using the predened editing components is covered in Creating and Conguring an Asset
Editor Page (www.adobe.com/docs/en/cq/5-61/dam/creating_and_conguringdamnderandasseteditorpages.html#par_title_1) .
In addition to using pre-existing editor components, CQ developers can also create their own components.
Creating an Asset Editor Template
5/8
4/5/2016

The following sample pages are included in geometrixx:
Geometrixx Sample Page: /content/geometrixx/en/press/asseteditor.html
Sample Template: /apps/geometrixx/templates/asseteditor
Sample Page Component: /apps/geometrixx/components/asseteditor
Conguring Clientlib
DAM components use an extension of the WCM edit clientlib. The clientlibs are usually loaded in init.jsp.
Compared to the default clientlib loading (in core's init.jsp), a DAM template must have the following:
The template must include the cq.dam.edit clientlib (instead of cq.wcm.edit).
The clientlib must also be included in disabled WCM mode (for example, loaded on publish) to be able to render
the predicates, actions, and lenses.
In most cases, copying the existing sample init.jsp (/apps/geometrixx/components/asseteditor/init.jsp) should meet
these needs.
Conguring JS actions
Some of the DAM components require JS functions dened in component.js. Copy this le to your component
directory and link it.
1
<scripttype="text/javascript"src="<%=component.getPath()%>/component.js"></script
The sample loads this javascript source in head.jsp (/apps/geometrixx/components/asseteditor/head.jsp).
Additional Style Sheets

Some of the DAM components use the CQ widgets library. To be rendered properly in the content context, an
additional style sheet has to be loaded. The tag action component requires one more.
1
<linkhref="/etc/designs/geometrixx/ui.widgets.css"rel="stylesheet"type="text/css"
Geometrixx Style Sheet

The sample page components require that all selectors start with .asseteditor of static.css
(/etc/designs/geometrixx/static.css). Best practice: Copy all .asseteditor selectors to your style sheet and adjust the
rules as desired.
FormChooser: Adjustments for eventually loaded Resources

The Asset Editor uses the Form Chooser, which allows you to edit resources - in this case assets - on the same form
page by simply adding a form selector and the path of the form to the URL of the asset.
For example:
Plain form page: http://localhost:4502/content/geometrixx/en/press/asseteditor.html
(www.adobe.comhttp://localhost:4502/content/geometrixx/en/press/asseteditor.html)
Asset loaded into the form page:
http://localhost:4502/content/dam/geometrixx/icons/diamond.png.form.html/content/geometrixx/en/press/asseteditor.html
(www.adobe.comhttp://localhost:4502/content/dam/geometrixx/icons/diamond.png.form.html/content/geometrixx/en/press/asseteditor.html)
The sample handles in head.jsp (/apps/geometrixx/components/asseteditor/head.jsp) do the following:
They detect if an asset is loaded or if the plain form has to be displayed.
If an asset is loaded, they disable WCM mode as parsys can only be edited on a plain form page.
If an asset is loaded, they use its title instead of the one on the form page.
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
List<Resource>resources=FormsHelper.getFormEditResources(slingRequest)
if(resources!=null){
if(resources.size()==1){
FormsHelper.setFormLoadResource(slingRequest,resources.get(0))
}elseif(resources.size()>1){
}
}
ResourceloadResource=(Resource)request.getAttribute("cq.form.loadresource")
Stringtitle
if(loadResource!=null){
WCMMode.DISABLED.toRequest(request)
Stringpath=loadResource.getPath()
Assetasset=loadResource.adaptTo(Asset.class)
try{
ObjecttitleObj=asset.getMetadata("dc:title")
if(titleObjinstanceofObject[]){
23
Object[]titleArray=(Object[])titleObj
6/8
4/5/2016

23
24
25
26
27
28
29
30
31
32
33
34
35
Object[]titleArray=(Object[])titleObj
title=(titleArray.length>0)?titleArray[0].toString():""
}else{
title=titleObj.toString()
}
}
catch(NullPointerExceptione){
title=path.substring(path.lastIndexOf("/")+1)
}
}
else{
title=currentPage.getTitle()==null?currentPage.getName():currentPage.getTitle()
}
In the HTML part, use the preceding title set (either asset or page title):
1
<title><%=title%></title>
Creating a simple form eld component

This example describes how to build a component that shows and displays the metadata of a loaded asset.
1. Create a component folder in your projects directory, for example,
/apps/geometrixx/components/samplemeta.
2. Add content.xml:
1
2
3
4
5
6
7
jcr:title="ImageDimension"
componentGroup="AssetEditor"/>
3. Add samplemeta.jsp:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
<%
Samplemetadatafieldcomopnent
%><%@pageimport="com.day.cq.dam.api.Asset,
java.security.AccessControlException"%><%
Stringvalue=""
Stringname="dam:sampleMetadata"
booleanreadOnly=false
ResourceloadResource=(Resource)request.getAttribute("cq.form.loadresource"
if(loadResource!=null){
Sessionsession=slingRequest.getResourceResolver().adaptTo(Session.class
try{
session.checkPermission(loadResource.getPath(),"set_property")
readOnly=false
}
catch(AccessControlExceptionace){
readOnly=true
}
catch(RepositoryExceptionre){}
Assetasset=loadResource.adaptTo(Asset.class)
try{
value=asset.getMetadata(name).toString()
}
catch(NullPointerExceptionnpe){
}
}
%>
<divclass="form_row">
<divclass="form_leftcol">
<divclass="form_leftcollabel">SampleMetadata</div>
</div>
<divclass="form_rightcol">
<%
if(readOnly){
%><c:outvalue="<%=value%>"/><%
}
else{
%><inputclass="text"type="text"name="./jcr:content/metadata/<%=
}%>
</div>
</div>
7/8
4/5/2016

4. To make the component available, you need to be able to edit it. To make a component editable, in CRXDE Lite,
add a node cq:editCong of primary type cq:EditCong. So that you can remove paragraphs, add a multi-value
5. Navigate to your browser, and on your sample page (for example, asseteditor.html) switch to design mode and
enable your new component for the paragraph system.
6. In Edit mode, the new component (for example, Sample Metadata) is now available in the sidekick (found in the
Asset Editor group). Insert the component. To be able to store the metadata, it must be added to the metadata
form.
Modifying Metadata Options

You can modify the namespaces available in the metadata form (www.adobe.com/docs/en/cq/5-61/dam/creating_and_conguringdamnderandasseteditorpages.html#Metadata%20Form%20and%20Text%20Field%20%20Conguring%20the%20View%20Metadata%20Component) .
Currently available metadata are dened in /libs/dam/options/metadata:
The rst level inside this directory contains the namespaces.
The items inside each namespace represents a metadata, such as results in a local part item.
The metadata content contains the information for the type and the multi-value options.
The options can be overwritten in /apps/dam/options/metadata:
1. Copy the directory from /libs to /apps.
2. Remove, modify, or add items.
NOTE
If you add new namespaces, they must be registered in your repository/CRX. Otherwise
submitting the metadata form will result in an error.
Customizing Renditions
In CQ DAM terminology a rendition is the form in which an asset is presented. In general, a particular asset may have
multiple renditions. For example, full-color image may have one rendition in its original size, another at a scaled-down
size and another that is both scaled down and converted to grayscale.
The renditions that a particular asset is available in can be customized and new renditions created.
Customizing Asset Processing

In addition to customizing how users nd and edit assets through the Asset Share and Asset Editor, you can also
customize what happens when an asset is uploaded to CQ DAM.
A workow can be dened that will automatically execute when an asset of a particular type is uploaded to the server.
The processing steps are dened in terms of a series of DAM Media Handlers (www.adobe.com/docs/en/cq/5-61/dam/dam_media_handlers.html) . CQ provides some built in handlers, (www.adobe.com/docs/en/cq/5-61/dam/dam_media_handlers.html#par_par2) and additional ones can be either custom developed
(www.adobe.com/docs/en/cq/5-6-1/dam/dam_media_handlers.html#par_par30) or dened by delegating the process
to a command line tool (www.adobe.com/docs/en/cq/5-6-1/dam/dam_media_handlers.html#par_title_1) .
(www.adobe.comhttp://www.adobe.com/go/gfooter_truste_logo)
Copyright 2009-2016 Adobe Systems Incorporated. All rights reserved.
Use of this website signies your agreement to the Terms of Use (www.adobe.comhttp://www.adobe.com/go/gfooter_terms_of_use) and Online Privacy Policy
(www.adobe.comhttp://www.adobe.com/go/gfooter_privacy_policy) .
8/8

Customizing and Extending CQ DAM

Transféré par

Informations du document

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

Customizing and Extending CQ DAM

Transféré par

Droits d'auteur :

Formats disponibles

4/5/2016

Customizing and Extending CQ DAM - docs.adobe.com

Overview (www.adobe.com/docs/en.html) /AEM 5.6.1 (www.adobe.com/docs/en/cq/5-6-1.html) /Working with Digital

Customizing and Extending CQ DAM

Customizing the Look and Feel

Customizing Asset Share

Creating an Asset Share Template

Additional Style Sheets

Customizing and Extending CQ DAM - docs.adobe.com

Geometrixx Style Sheet

Adding custom predicates

Example: Build a simple property predicate

Customizing and Extending CQ DAM - docs.adobe.com

Example: Build a simple group predicate

Customizing and Extending CQ DAM - docs.adobe.com

Customizing Search Results

Customizing and Extending CQ DAM - docs.adobe.com

Adding a custom action

Example: Create a simple action

Creating an Asset Editor Template

Customizing and Extending CQ DAM - docs.adobe.com

The sample loads this javascript source in head.jsp (/apps/geometrixx/components/asseteditor/head.jsp).

Additional Style Sheets

Geometrixx Style Sheet

FormChooser: Adjustments for eventually loaded Resources

Customizing and Extending CQ DAM - docs.adobe.com

Creating a simple form eld component

Customizing and Extending CQ DAM - docs.adobe.com

Modifying Metadata Options

Customizing Asset Processing

Vous aimerez peut-être aussi