Expand my Community achievements bar.

Don’t miss the AEM Skill Exchange in SF on Nov 14—hear from industry leaders, learn best practices, and enhance your AEM strategy with practical tips.
SOLVED

Archetype for Assets as a Cloud Service

Avatar

Employee Advisor

We have archetype for a full fledge project - AEM Sites and SPA based. Do we have any option to build code repo for Assets as a cloud service instance which does not have sites feature? 

1 Accepted Solution

Avatar

Correct answer by
Employee Advisor

Anyone looking at this thread- I don't see any option to create a new repo for Assets only implementation but what I got recommendations from my peers is to use the full sites archetype and comment out redundant modules (e.g. dispatcher, ui.frontend, ui.tests etc). A possible reason why we don't have dedicated option is due to the fact that assets implementations can be augmented by certain add-on features like brand-portal, asset share commons etc. which follow sites like implementation. So these module might seem redundant but futuristic to support site features.

View solution in original post

1 Reply

Avatar

Correct answer by
Employee Advisor

Anyone looking at this thread- I don't see any option to create a new repo for Assets only implementation but what I got recommendations from my peers is to use the full sites archetype and comment out redundant modules (e.g. dispatcher, ui.frontend, ui.tests etc). A possible reason why we don't have dedicated option is due to the fact that assets implementations can be augmented by certain add-on features like brand-portal, asset share commons etc. which follow sites like implementation. So these module might seem redundant but futuristic to support site features.