Konrad Windszus

@tommix1987 The problem is that install hooks on mutable content packages are not supported (details in https://github.com/Netcentric/aem-cloud-validator#prevent-using-install-hooks-in-mutable-content-packages). Also the Groovy Console is currently not compatible with AEMaaCS either (https://github.com/CID15/aem-groovy-console/issues/1

The image from https://github.com/BretFisher/jekyll-serve seems to support multiple architectures. Not sure though how close this is to the GitHub Pages tool versions (https://pages.github.com/versions/).

There is also docker support from https://github.com/github/pages-gem?tab=readme-ov-file#docker.

I will try to come up with something...

This is now natively supported (since AEM 6.3): https://docs.adobe.com/docs/en/aem/6-3/develop/ref/granite-ui/api/jcr_root/libs/granite/ui/components/coral/foundation/form/multifield/index.html.

1. IMHO the correct categories to use are 1. `cq.authoring.editor.sites.page.hook` (https://docs.adobe.com/content/help/en/experience-manager-65/developing/extending-aem/customizing-page-authoring-touch.html) 1. `cq.authoring.page` 1. use `extraClientlibs` for component specific JS/CSS (https://docs.adobe.com/content/help/en/experience-manager-65/developing/components/developing-components.html#creating-a-client-library-for-style-and-behavior), or category `cq.authoring.dialog` if JS/CSS should be loaded for...

@davidjgonzalez WDYT about the categories, especially the one to use for the page creation wizard?

IMHO it makes sense to document those categories centrally instead of per feature (especially as some JS might make sense in multiple use cases). As I don’t know of any...

@badvision Is that something you can provide since you added the feature?

This will break the build, it needs fixing in the same PR. Do you want to pick it up?