I am working on CQ 5.6.1 for a while but i didn't have much knowledge on DAM. So was studying DAM. I came across a term DAM Taxonomy. I couldn't see any direct link to it in documentation.
I want to know what is DAM Taxonomy and how can we create DAM Taxonomy in CQ 5.6.1?
Can we create these taxonomies in CQ 5 or we should use third party applications?
Taxonomy in DAM is no different from the one we have for Sites. You could access it directly in http://localhost:4502/tagging.
Giving you a brief on tagging - Tags are a greater way to organize content / assets. Tags are critical for search. Defining and managing tags are essential as it impacts the search which is the #1 use-case in most DAM deployments.
Links:
DAM & tagging - http://docs.adobe.com/docs/en/cq/5-6-1/dam/dam_documentation.html#Using%20Tags%20to%20Organize%20Assets
Tagging - http://docs.adobe.com/docs/en/aem/6-0/administer/content/tags.html
Related
am having a requirement to use a common content in all the pages. So I decided to use the reference component in AEM. I have created a new page and authored the content. How can this content can be used in the templates, so that it will appear in all pages without re-authoring.
As you are using AEM 6 version, you can utilize the concept of design dialogs in components in static templates. You create a component, add design dialog and choose the fields in the design dialog, which once is authored will reflect in all pages created with that template.
The only activity you have to do while authoring is, you need to add and author the component in a page created with specific template.
If you are using the AEM 6.3 or more, Experience Fragments can be used, you can configure the experience fragment in the template and can be seen across all the pages.
You can use the experience fragment in individual pages as well.
https://docs.adobe.com/content/help/en/experience-manager-learn/sites/experience-fragments/experience-fragments-feature-video-use.html
How to organize a list of content items (i.e. projects in portfolio) into different categories (i.e. industries) in Kentico Cloud content as a service platform.
i.e.
Project 1 (content type project) - Commercial (industry)
Project 2 (content type project) - Commercial (industry)
Project 3 (content type project) - Health care (industry)
There are two solutions on the table:
Create a content type called industries and ad linked items element called industries to the project content type
Create a taxonomy group, called industries and tag the content item "client" with a tag
Our dev favored option 2, however, it seems not to be possible to localize a tag value and it would therefore never be possible to display the tag itself in the multilingual UI.
What would the official recommendation for this?
This question is a migrated from official Kentico Cloud Forum, that would be deleted.
When designing multilingual support for Kentico Cloud, localization of taxonomy groups was designed that way as well.
It is still in the plan to do it in the future, but as many other priorities arrive, multilingual support for taxonomy terms is currently postponed.
According to the question - there is no constraint to model taxonomy just using taxonomy groups.
The best way to model this use case is to use linked items elements functionality as it is in example. It supports multilingual and it could be used for categorization. And it is also possible to limit the element to allow placing only one content type (industry in your case).
I'm looking to see if it's possible to integrate an existing AEM Component that I've developed (lets say button component) into the RTE.
I've read the following blog posts
http://experience-aem.blogspot.com/2015/01/aem-6-sp1-touchui-richtext-editor-color-picker-plugin.html
http://experience-aem.blogspot.com/2015/09/aem-61-touch-ui-rich-text-editor-rte-browse-insert-image.html
I've also read the documentation (which is non existent).
I'm not looking to recreate the exact same component just for the RTE, this would need us to maintain two separate code bases, recreate the custom logic we have in the already existing component which has been tested and automation.
But most of all, go against best practices as we want everything to be agnostic.
We are setting up a fresh AEM 6.2 project and the application will make use of some author specific client libs and some publish specific clientlibs;
We want to ensure that the author specific client libs do not unnecessarily load up on the AEM publish instances. Please guide us as to how we can achieve it?
Hi Adobe document for the clientlibs creation process is below.
https://docs.adobe.com/docs/en/aem/6-2/develop/the-basics/clientlibs.html
consider below points while design phase that will lead to the best practices implementation.
multiple components with their own JavaScript and CSS files
global JavaScript and CSS files
apps folder is not available on the publish instance
CSS resources have to go in the <head>, JavaScript resources at the end of the page
Resources need to be minified
Some resources need to be merged
http://blogs.adobe.com/experiencedelivers/experience-management/clientlibs-explained-example/
TRAC tends to separate wiki pages and tickets quite a lot, but there is definitely an argument for cross-reference.
I know that the TagsPlugin unifies both ticket "Keywords" and a new "Tag" list for wiki pages. I'm looking for a similar functionality for components and milestones. Is it possible with TRAC 0.11? If not, what about more recent versions?
Do I understand correctly, that you request/vote for tagging Trac resources milestone and component? This is reasonable, and could be done, because TagsPlugin is ready for tagging arbitrary Trac realms just by implementing the ITagProvider interface, i.e. by subclassing DefaultTagProvider, and you're up and running with the generic tag store in Trac db table tags as tag store.
Or is your request more about functionality like that provided by
ComponentsProcessorMacro - listing project components with descriptions
ListMilestonesMacro - shows a list of chosen Milestones
MilestoneCompactMacro - milestones displayed in compact table or list
MilestoneQueryMacro - displays a list of matching milestones
PlannedMilestonesMacro - lists milestones ordered by their due dates