Wednesday, 15 November 2017

Creating a FavIcon for an Adobe Experience Manager 6.3 Site

You can create a Favicon for an Adobe Experience Manager site. A Favicon is typically an icon associated with a specific site and appears in the web browser tab. For more information, see  Favicon.

If a site does not have a Favicon, the tab in the browser does not display an image, as shown in this illustration.


In contrast, when a site has a Favicon, it appears in the browser tab, as shown here.


To add a Favicon to an Experience Manager site, there are several steps that you must perform. This article covers these steps. 




Join the Adobe Experience Cloud Community 

Join the Adobe Experience Cloud Community by clicking this banner





I (Scott Macdonald) am a Senior Digital Marketing Community Manager at Adobe Systems with 20 years in the high tech industry. I am also a programmer with knowledge in Java, JavaScript, C#,C++, HTML, XML and ActionScript. If  you would like to see more CQ or other Adobe Digital Marketing end to end articles like this, then leave a comment and let me know what content you would like to see.


TwitterFollow the Digital Marketing Customer Care team on Twitter @AdobeExpCare.

YouTube: Subscribe to the AEM Community Channel


Wednesday, 8 November 2017

November 2017 Session of Ask the AEM Community Experts

Date:

Tuesday, November 28, 2017
11:00 AM EST to 12:00 PM
https://communities.a­dobeconnect.com/aemte­ch/

Speaker:
Bertrand de Coatpont

Topic:
More enterprises are using online community experiences, to build upon their brands. They provide a venue where community members can share and learn with their peers.In this Ask the Expert session you will learn how to set up a community site in hours rather than weeks,via a wizard-driven templated approach to cover a variety of initial use cases. AEM Communities also provides the ability to further customize these new community sites via WCM Sites capability. Join us to learn how to leverage the powerful authoring interface to build a vibrant customer community and learn the tools to keep your fan base engaged long after launch.

To sign up- click November Ask the Community Experts.

Join the Adobe Experience Cloud Community 

Join the Adobe Experience Cloud Community by clicking this banner





I (Scott Macdonald) am a Senior Digital Marketing Community Manager at Adobe Systems with 20 years in the high tech industry. I am also a programmer with knowledge in Java, JavaScript, C#,C++, HTML, XML and ActionScript. If  you would like to see more CQ or other Adobe Digital Marketing end to end articles like this, then leave a comment and let me know what content you would like to see.


TwitterFollow the Digital Marketing Customer Care team on Twitter @AdobeExpCare.

YouTube: Subscribe to the AEM Community Channel

Wednesday, 1 November 2017

Exporting Adobe Experience Manager Data Using Sling Model Exporters

You can create an Experience Manager Sling Model Experter to export Experience Manager data as JSON. You can invoke a Sling Model Exporter by using a HTTP Restful call and get back data. For example, assume that you want to get details of an image component located in the We Retail site located here:

http://localhost:4502/editor.html/content/we-retail/us/en/experience.html 

The following illustration shows the image component.


You can use a Sling Model Exporter to get component details that are returned within JSON, as shown in the following illustration.  


To invoke the Sling Model Exporter, you can use this URL:

http://localhost:4502/content/we-retail/us/en/experience/jcr:content/root/responsivegrid/heroimage.model.tidy.json

The data is retrieved from the AEM JCR located here:

/content/we-retail/us/en/experience/jcr:content/root/responsivegrid/heroimage

The following illustration shows this node.


You can create a Sling Model Exporter by using Java APIs located in the org.apache.sling.models.annotations package. To read this development article, click:      https://helpx.adobe.com/experience-manager/using/aem63_sling_model_exporter.html


Join the Adobe Experience Cloud Community 

Join the Adobe Experience Cloud Community by clicking this banner





I (Scott Macdonald) am a Senior Digital Marketing Community Manager at Adobe Systems with 20 years in the high tech industry. I am also a programmer with knowledge in Java, JavaScript, C#,C++, HTML, XML and ActionScript. If  you would like to see more CQ or other Adobe Digital Marketing end to end articles like this, then leave a comment and let me know what content you would like to see.


TwitterFollow the Digital Marketing Customer Care team on Twitter @AdobeExpCare.

YouTube: Subscribe to the AEM Community Channel

Tuesday, 24 October 2017

Creating a Tab layout component for Adobe Experience Manager

You can create an Adobe Experience Manager HTL component that displays data within a tab layout style. By developing a tab layout component, you can organize your data under tabs. That is, a web site visitor can click on a tab on the web page to see different data set. Notice the following illustration displays an AEM component with four tab headings: Home Page, Career Section, Contact Us, and About US.

This development shows use of the JS USE API. To read this development article, click https://helpx.adobe.com/experience-manager/using/htl_tab_component.html.


Join the Adobe Experience Cloud Community 

Join the Adobe Experience Cloud Community by clicking this banner





I (Scott Macdonald) am a Senior Digital Marketing Community Manager at Adobe Systems with 20 years in the high tech industry. I am also a programmer with knowledge in Java, JavaScript, C#,C++, HTML, XML and ActionScript. If  you would like to see more CQ or other Adobe Digital Marketing end to end articles like this, then leave a comment and let me know what content you would like to see.


TwitterFollow the Digital Marketing Customer Care team on Twitter @AdobeExpCare.

YouTube: Subscribe to the AEM Community Channel


Tuesday, 10 October 2017

Creating a Mail List Component for the Experience Manager Toy Store Site

You can create Adobe Experience Manager custom components that function as Mail Sign Up  components. An Mail Sign Up component lets web site visitors sign up to a mailing list that typically includes emailing out newsletters. In this article, the Mail List component is added to the Experience Manager Toy Store site.


When the user fills in the fields and clicks the Submit button, the data is persisted in a relational database by using a DataSourcePool


This development article discusses how to inject a DataSourcePool service into an AEM service to which an HTL component submits data. By injecting a DataSourcePool, your service can connect to a relational database such as MySQL.  

This article shows use of the following AEM technologies: 

1. Build a HTL component that can submit data to a back-end service. 
2. Use Sling Models with an HTL component. 
3. How to inject a DataSourcePool into an AEM 6.3 service. 
4. How to use the org.osgi.service.component.annotations.Component package to write an AEM Servlet.



Join the Adobe Experience Cloud Community 

Join the Adobe Experience Cloud Community by clicking this banner





I (Scott Macdonald) am a Senior Digital Marketing Community Manager at Adobe Systems with 20 years in the high tech industry. I am also a programmer with knowledge in Java, JavaScript, C#,C++, HTML, XML and ActionScript. If  you would like to see more CQ or other Adobe Digital Marketing end to end articles like this, then leave a comment and let me know what content you would like to see.


TwitterFollow the Digital Marketing Customer Care team on Twitter @AdobeExpCare.

YouTube: Subscribe to the AEM Community Channel




  



Thursday, 5 October 2017

Ask the AEM Community Experts for October

Sign up for this month's Ask the AEM Community Experts.

Here are the Details:

Date
Tuesday, October 31, 2017
11:00 AM to 12:00 AM

Topic:
The ability to create custom components is a very important use case when working with Adobe Experience Manager. The preferred language to create custom component is HTL. This session will present a Deep Dive when working with HTL and will cover such topics as working with Sling Models, the Java USE API, how to deal with collections to build rich custom components meant for Experience Manager web sites.

Presenters:
Shivani Garg, AEM Developer
Saurabh Gupta, AEM Developer




Join the Adobe Experience Cloud Community 

Join the Adobe Experience Cloud Community by clicking this banner





I (Scott Macdonald) am a Senior Digital Marketing Community Manager at Adobe Systems with 20 years in the high tech industry. I am also a programmer with knowledge in Java, JavaScript, C#,C++, HTML, XML and ActionScript. If  you would like to see more CQ or other Adobe Digital Marketing end to end articles like this, then leave a comment and let me know what content you would like to see.


TwitterFollow the Digital Marketing Customer Care team on Twitter @AdobeExpCare.

YouTube: Subscribe to the AEM Community Channel



Thursday, 28 September 2017

Using an WCMUsePojo class to populate an Experience Manager Touch UI Select Field

You can create an Adobe Experience Manager (AEM) 6.3 Touch UI component that contains a drop-down control that can be used within the AEM Touch UI view. The data type of the drop-down field is /libs/granite/ui/components/foundation/form/select.

An AEM author selects drop-down values during design time. For example, an author can select a country from the drop-down field, as shown in this illustration.



You can populate a drop-down field by using a com.adobe.granite.ui.components.ds.DataSource object. For information, see DataSource.

Furthermore, you can create this object in a Java WCMUsePojo class and use HTL to invoke it. That is, get the values defined in the DataSource object. Finally you can bind the resource type of the HTL code to the dialog node that represents the drop-down field.

This development article steps your through how to use a DataSource object, a Java Map collection object, and HTL to populate a drop-down field in an AEM 6.3 component.

To read this development article, click https://helpx.adobe.com/experience-manager/using/aem63_datasource.html


Join the Adobe Experience Cloud Community 

Join the Adobe Experience Cloud Community by clicking this banner





I (Scott Macdonald) am a Senior Digital Marketing Community Manager at Adobe Systems with 20 years in the high tech industry. I am also a programmer with knowledge in Java, JavaScript, C#,C++, HTML, XML and ActionScript. If  you would like to see more CQ or other Adobe Digital Marketing end to end articles like this, then leave a comment and let me know what content you would like to see.


TwitterFollow the Digital Marketing Customer Care team on Twitter @AdobeExpCare.

YouTube: Subscribe to the AEM Community Channel





Wednesday, 27 September 2017

Setting Maximum items in an Experience Manager 6.3 Multifield

You can create an Adobe Experience Manager (AEM) 6.3 Touch UI component that can be used within the AEM Touch UI view. Furthermore, you can use the AEM HTML Template Language (HTL - formally known as Sightly) to develop the AEM component. For example, consider an author whom enters information into a multi-field control in the component's dialog, as shown in this illustration.


In the previous illustration, notice that the Page Name and Path controls are used within a multifield control. When an author clicks the Add Field button, a new area that contains a Page Name, Path and Flag control appears. This lets an author dynamically enter as many values as required into the dialog.

Sometimes you may have a requirement to set a limit of the number of multifield items that an author can set. When the author attempts to go over the limit, a message appears, as shown in this illustration. 


This development article discusses how to use script to set the maximum number of multifield items an AEM author can set in a Touch UI component dialog. To read this development article, click https://helpx.adobe.com/experience-manager/using/multifield_aem63_setlimit.html.


Join the Adobe Experience Cloud Community 

Join the Adobe Experience Cloud Community by clicking this banner





I (Scott Macdonald) am a Senior Digital Marketing Community Manager at Adobe Systems with 20 years in the high tech industry. I am also a programmer with knowledge in Java, JavaScript, C#,C++, HTML, XML and ActionScript. If  you would like to see more CQ or other Adobe Digital Marketing end to end articles like this, then leave a comment and let me know what content you would like to see.


TwitterFollow the Digital Marketing Customer Care team on Twitter @AdobeExpCare.

YouTube: Subscribe to the AEM Community Channel




Wednesday, 20 September 2017

Creating Personal Experiences using Experience Manager and Target

When working with Adobe Experience Manager and Adobe Target to create personalization use cases, you can use Experience fragments to change the content that is displayed. Experience Fragments are a new feature introduced in AEM 6.3. They allow content authors to reuse content across channels including Sites pages and 3rd party systems. For more information, see Using AEM Experience Fragments.

Using Experience Fragments, you can display content based on the audience. For example, some users may see this content.


While others see this content. 


Using Adobe Target, you can setup personalization use cases. This article steps you through how to setup personalization use cases using Experience Fragments, Experience Manager, and Adobe Target. 



Join the Adobe Experience Cloud Community 

Join the Adobe Experience Cloud Community by clicking this banner





I (Scott Macdonald) am a Senior Digital Marketing Community Manager at Adobe Systems with 20 years in the high tech industry. I am also a programmer with knowledge in Java, JavaScript, C#,C++, HTML, XML and ActionScript. If  you would like to see more CQ or other Adobe Digital Marketing end to end articles like this, then leave a comment and let me know what content you would like to see.


TwitterFollow the Digital Marketing Customer Care team on Twitter @AdobeExpCare.

YouTube: Subscribe to the AEM Community Channel



Wednesday, 13 September 2017

Ask the AEM Community Experts for Sept 2017

September 2017 – Ask the AEM Community Expert Session


Topic: Best practices for working with ContextHub in Adobe Experience Manager

Speaker: Varun Mitra, Training Instructor/Developer, Worldwide Field Enablement Adobe

ContextHub is a framework for storing, manipulating, and presenting context data. The client-side JavaScript API enables you to access the data for personalizing content. Join Varun Mitra, on Tuesday September 26th at 8:00 AM PDT for an in depth look at best practices for working with ContextHub , and how to use a data layer in an AEM Sites.

To watch this session -- click:


http://bit.ly/917AtACE


Join the Adobe Experience Cloud Community 

Join the Adobe Experience Cloud Community by clicking this banner




I (Scott Macdonald) am a Senior Digital Marketing Community Manager at Adobe Systems with 20 years in the high tech industry. I am also a programmer with knowledge in Java, JavaScript, C#,C++, HTML, XML and ActionScript. If  you would like to see more CQ or other Adobe Digital Marketing end to end articles like this, then leave a comment and let me know what content you would like to see.


TwitterFollow the Digital Marketing Customer Care team on Twitter @AdobeExpCare.

YouTube: Subscribe to the AEM Community Channel

Monday, 11 September 2017

Creating a custom Touch UI Grid Component for Adobe Experience Manager

You can develop a custom Adobe Experience Manager (AEM) Touch UI grid component to address your business requirements. An AEM grid control component lets an AEM author split the content in the main panel of the web-page into multiple columns. Using a component dialog, an author defines the number of columns required and then create, delete, or move content within each of the columns.


Using a custom Grid control, an AEM author can specify different width options by using a dialog.


This grid component uses Bootstrap.  To read this development article, click https://helpx.adobe.com/experience-manager/using/bootstrap_grid.html

NOTE: This development article shows an example of using a HTL component with Sling Models. 

Join the Adobe Experience Cloud Community 

Join the Adobe Experience Cloud Community by clicking this banner





I (Scott Macdonald) am a Senior Digital Marketing Community Manager at Adobe Systems with 20 years in the high tech industry. I am also a programmer with knowledge in Java, JavaScript, C#,C++, HTML, XML and ActionScript. If  you would like to see more CQ or other Adobe Digital Marketing end to end articles like this, then leave a comment and let me know what content you would like to see.


TwitterFollow the Digital Marketing Customer Care team on Twitter @AdobeExpCare.

YouTube: Subscribe to the AEM Community Channel


Friday, 8 September 2017

Creating an Adobe Experience Manager 6.3 Project using Adobe Maven Archetype 11

You can create AEM 63 projects by using Adobe Maven Archetype 11.  This development article walks you through creating an AEM 6.3 project by using Archetype 11 and explains the default AEM files and services that are created.

The following illustration represents a default page that is created.



Under the Service Component section in the above illustration, notice the values that are displayed.

HelloWorldModel says:
 Hello World!
 This is instance: fe95f477-e525-432b-9fed-9d65dba3f5d2
 Resource type is: aem10/components/content/helloworld


These values are returned by a default AEM service. Once you understand all of the files and services that are created by Maven, you can use this project as starting point for your AEM 6.3 projects.

To read this development article, click https://helpx.adobe.com/experience-manager/using/maven_arch11.html.


Join the Adobe Experience Cloud Community 

Join the Adobe Experience Cloud Community by clicking this banner




I (Scott Macdonald) am a Senior Digital Marketing Community Manager at Adobe Systems with 20 years in the high tech industry. I am also a programmer with knowledge in Java, JavaScript, C#,C++, HTML, XML and ActionScript. If  you would like to see more CQ or other Adobe Digital Marketing end to end articles like this, then leave a comment and let me know what content you would like to see.


TwitterFollow the Digital Marketing Customer Care team on Twitter @AdobeExpCare.

YouTube: Subscribe to the AEM Community Channel

Monday, 28 August 2017

Creating an Experience Manager Responsive Banner Component

As an Adobe Experience Manager Developer, you can create a custom Banner component. A Banner Component typically embeds an advertisement into a web page.  That is, it is used to attract traffic to a website by linking to the website of the advertiser. This development article walk you thought how to build a responsive Banner component that can be used in an AEM site.


The Banner component built in this article uses Sling Models and the Bootstrap library. For information, see Bootstrap.


AEM 6.2

AEM 6.3

To read this development article, click https://helpx.adobe.com/experience-manager/using/htl_banner.html.


Join the Adobe Experience Cloud Community 

Join the Adobe Experience Cloud Community by clicking this banner





I (Scott Macdonald) am a Senior Digital Marketing Community Manager at Adobe Systems with 20 years in the high tech industry. I am also a programmer with knowledge in Java, JavaScript, C#,C++, HTML, XML and ActionScript. If  you would like to see more CQ or other Adobe Digital Marketing end to end articles like this, then leave a comment and let me know what content you would like to see.


TwitterFollow the Digital Marketing Customer Care team on Twitter @AdobeExpCare.

YouTube: Subscribe to the AEM Community Channel

Tuesday, 15 August 2017

Passing Binary Data between Experience Manager Workflow Steps

You can develop a custom Adobe Experience Manager (AEM) workflow step that sets a binary value that can be retrieved by another step in the same workflow. For example, assume you read a byte array and you need that value in a later step. You can store the value and retrieve it in a later step.

To read and write binary values in an AEM workflow, you need to write custom steps. A custom workflow step is implemented as an OSGi bundle that you can build using Maven and the AEM Workflow APIs that belong to the com.adobe.granite.workflow.exec package. For information, see Package com.adobe.granite.workflow.exec.

To demonstrate how to pass values in a workflow between steps, this article uses the following workflow model.




Join the Adobe Experience Cloud Community 

Join the Adobe Experience Cloud Community by clicking this banner





I (Scott Macdonald) am a Senior Digital Marketing Community Manager at Adobe Systems with 20 years in the high tech industry. I am also a programmer with knowledge in Java, JavaScript, C#,C++, HTML, XML and ActionScript. If  you would like to see more CQ or other Adobe Digital Marketing end to end articles like this, then leave a comment and let me know what content you would like to see.


TwitterFollow the Digital Marketing Customer Care team on Twitter @AdobeExpCare.

YouTube: Subscribe to the AEM Community Channel




Friday, 11 August 2017

Creating an AEM HTML Template Language 6.3 component that uses a Multifield

You can create an Adobe Experience Manager (AEM) 6.3 Touch UI component that can be used within the AEM Touch UI view. Furthermore, you can use the AEM HTML Template Language (HTL - formally known as Sightly) to develop the AEM component. For example, consider an author whom enters information into a multi-field control in the component's dialog, as shown in this illustration.


To read this Adobe Experience Manager 6.3 development article, click https://helpx.adobe.com/experience-manager/using/multifield_aem63.html

Added an new package for AEM 6.3 that included a RTE

Based on community feedback - such as https://forums.adobe.com/thread/2379678, we added a separate package that contains a RTE in the Multifield. It works - see: 


This is the JCR node structure now:


Notice that the RTE data is stored as JSON data under the page: 




You can see this by installing the second package that is part of this article

Join the Adobe Experience Cloud Community 

Join the Adobe Experience Cloud Community by clicking this banner





I (Scott Macdonald) am a Senior Digital Marketing Community Manager at Adobe Systems with 20 years in the high tech industry. I am also a programmer with knowledge in Java, JavaScript, C#,C++, HTML, XML and ActionScript. If  you would like to see more CQ or other Adobe Digital Marketing end to end articles like this, then leave a comment and let me know what content you would like to see.


TwitterFollow the Digital Marketing Customer Care team on Twitter @AdobeExpCare.

YouTube: Subscribe to the AEM Community Channel