Showing posts with label tags. Show all posts
Showing posts with label tags. Show all posts

Tuesday, 22 November 2016

AEM Tag field validation

AEM6 uses Coral UI framework for touch UI rendering. So if you need to implement field validation, you should register a validator on that field supported by Coral UI.

To implement validation on tag input field you can use the following sample code.

1. In your tagspicker input field add one property- tagsMessage (Set value to the validation message). Look at the screenshot below-


Thursday, 20 October 2016

Tagging in AEM

What is Tagging? Adobe says: "Tagging allows content to be categorized and organized". Basically tagging is assigning one or more keywords to a piece of Content so that it can be identified whenever necessary based on its categorization. That piece of content could be a page, an asset etc. The entire Adobe guide on tagging is here. Tags are generally assigned to Pages and Assets. You can create tags via the Tagging Console or programmatically. 


Read More

Sunday, 31 July 2016

Developing HTML Template Language Components that search for AEM Content Tags



You can create a custom Adobe Experience Manager (AEM) HTL component that searches for AEM content tags. Tags are a quick and easy method of classifying content within your website. In technical terms, a tag is a piece of metadata assigned to a content node within AEM (usually a page). Within the OSGi component, the AEM Tag Manager is used to search for the content tags, For information about the API, see TagManager API.For information about the API, see AEM TagManager.
Consider the following illustration of the HTL component created in this article that shows defined AEM tags. 

Saturday, 28 May 2016

Using Custom Tag Libraries to search for AEM Content Tags

You can create custom tag libraries for Adobe Experience Manager (AEM) and use them to search for AEM content tags. Tags are a quick and easy method of classifying content within your website. In technical terms, a tag is a piece of metadata assigned to a content node within AEM (usually a page). A custom tag library uses an OSGi component. Within the OSGi component, the AEM Tag Manager is used to search for the content tags, For information about the API, see TagManager API.
A custom tag library is implemented as an OSGi bundle that contains a Java class that extendsTagSupport. For information, see Class TagSupport.
You also need to define a tag library descriptor (TLD) file and bundle that within the OSGi bundle. For information, see Tag Library Descriptors.
After you develop an AEM custom tag library, you can invoke its actions from an AEM component. For example, the component can display information about tag usage (for example, the number of times it is used). In this article, a Tags xtype is used to let the author select a tag from an AEM dialog, as shown in the following illustration.