Managing different Content Types like URLs, Links, Maps, widgets and articles

[nsvsrk]

Hi,

I have come across a requirement to create and utilize different Content Types in AEM, like URLs, Links, Maps, embedded code (widgets) and articles.

I am aware of creating and utilizing templates, pages and DAM assets like Images and videos, but not any of the above items.

For example, when a URL is created, system should make sure that it is unique in the system and is valid.

System should also record metadata like its "owner name" and "last updated by" attributes.

Ultimately, system should allow using these content types in multiple pages and components.

If we have to manage these content types, how to proceed?

Where should they be stored and as what node/resource types?

Is there any OOB support for these?

Highly appreciate any light being thrown on this subject.

Thanks,

Rama.

[smacdonald2008]

With respect to URLs - are you referring to an URL that a user may place in a text component? 

With widgets - are you referring to EXTJS data types or granite types that can go on a component dialog such as a textfield? 

Ultimately, system should allow using these content types in multiple pages and components

AEM does allow sling resource types (scripts) to go into multiple pages. Remember - in AEM everything is content and has a sling resource type based on a script. 

If you are interested in articles - you can create all sorts of social components such as blogs and article components (etc) and inject them into  multiple pages. 

In addition  - AEM supports custom node types. See: 

Custom Node Types 

[Jörg_Hoh]

Hi,

what do you mean with "URL"? When you add "Link" as other example, you probably mean with URL the fully qualified address of a resource in your AEM instance. This is something you don't need to manage, as your authors create these names, and the system ensures that these are unique. Also the "lastModified" property is normally maintained by all authoring activities.

AEM does not know the notion of a "owner" of a resource. I tracks the creator and the last user which has done a modification.

If you want to design new elements, which can be reused like assets on multiple pages, I would recommend you to get in touch with experienced AEM architects and developers; a lot of approaches can be implemented, but depending on requirements only a small number make really sense and fit into the overall design of the UI and the system.

Jörg

[Lokesh_Shivalingaiah]

I agree with @Jorg ! 

If you are mentioning about the URL of a page that is created, then its automatically built based on your site structure. Also it automatically creates the audit properties like created by, modified by, creation date and last modified date. 

If we have to capture any other metadata for the page, then we need to create a custom widget to take those properties at the relevant places like page properties, template configs etc

Please get help of any AEM architects so that its been designed properly based on the requirements

[nsvsrk]

Hi,

Thanks for your responses.

I agree that when we create any content in AEM, a unique URL is automatically associated with it.

But there is nothing like someone creating and maintaining URLs themselves right?

Also, URLs could be external URLs.

I mean.widgets = embedded code  

Please suggest whether this could be achieved.

Thanks,

Rama.

[smacdonald2008]

In AEM - as Jorg points out - an URL is the fully qualified address of a resource . You can control an URL using Resource Mapping. See:

https://docs.adobe.com/docs/en/aem/6-1/deploy/configuring/resource-mapping.html

Not sure what you mean by .widgets = embedded code

[nsvsrk]

Hi,

With your following question, I am clarifying what a widget means for me -- as embedded code.

With widgets - are you referring to EXTJS data types or granite types that can go on a component dialog such as a textfield? 

Thanks,

Rama.

[Lokesh_Shivalingaiah]

Yes, by default the structure where the page is created takes the URL of that page. However, if they want a different URL for a particular page then the same can be achieved using 'Vanity URLs' in the page properties of that page. This way authors/business can have the URLs of their choice.

If they want some external URLs, then have a component created which takes the external URL and forward to that URL when accessed.

[Jörg_Hoh · Accepted solution]

Hi,

Regarding URLs: URLs are not a first level citizen in AEM; while the pages do have an implicit URL (based on their name and their location within the page tree, plus maybe some optional mapping), links to external pages are not handled explicitly. By default they can be created by every author using the Richttext editor. If you need to manage these links explicitly (this can mean, that every external link needs approval) you need to model these links explicitly (maybe as page), create an approval workflow for it, and find a way to allow an author to embedd such a link to a page. While I have seen this once, it is a very rare requirement.

kind regards,
Jörg