Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

AEMaaCS readyness #21

Open
LFDave opened this issue Jun 23, 2021 · 0 comments
Open

AEMaaCS readyness #21

LFDave opened this issue Jun 23, 2021 · 0 comments

Comments

@LFDave
Copy link
Contributor

LFDave commented Jun 23, 2021

Note: this is work in progress to collect topics that come up in regards to compatibility with AEMaaCS. Below were primary findings from having a quick look.

Tasks

  • move mutable content (/content/dam/frontify-aem-connector) from ui.apps
  • replace legacy /etc/cloudservices
  • update deprecated SlingSettingsService in RunmodeUtil

Optimizations

  • narrow down filters in ui.apps are (/apps/cq, /apps/wcm)
  • add primary type to nodes in ui.apps/src/main/content/jcr_root/apps/wcm/core/content/editor/.content.xml
  • considering sling resource merger the nodes should not even be part of the xml
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@LFDave