Skip to main content
Adobe Employee
vivekanand-mishAdobe Employee
Adobe Employee
March 13, 2023
Solved

Archetype for Assets as a Cloud Service

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? 

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
vivekanand-mishAccepted solution
Adobe Employee
March 14, 2023

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 in thread

1 reply

Adobe Employee
vivekanand-mishAdobe EmployeeAuthorAccepted solution
Adobe Employee
March 14, 2023

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.

Translate
    Terms & ConditionsAccessibility statement

    Loading footer...