Feature Request

Is your feature request related to a problem? Please describe.
The button core component allows for a title, and icon and a link. Semantically, this is a link and not a button, they are different things. Links go somewhere, buttons do something. (https://a11y-101.com/design/button-vs-link)

Describe the solution you'd like
Rename the button component to link (or

The wrapper client libs being recommended in https://adobe-consulting-services.github.io/acs-aem-commons/pages/releases/4-0-0.html are a big step ahead, but for certain use cases other mechanisms are more appropriate:

Client Libs being used inside dialogs should rather be directly referenced via property extraClientlibs (https://helpx.adobe.com/experience-manager/6-4/sites/developing/using/de

Set includeExamples=n as default for new projects, because it might be confusing to get the examples by default for those not expecting and desiring them. As these examples are hosted on https://www.aemcomponents.dev/ it's not a necessity to have them inside the project.

According to https://html.spec.whatwg.org/multipage/introduction.html#intro-early-example HTML attribute values must be either

1. Quoted in double quotes
2. Quoted in single quotes
3. Not quoted.

The HTL spec at https://github.com/adobe/htl-spec/blob/master/SPECIFICATION.md#21-syntax should explicitly state which form is supported!

Would be nice to have a complete custom cloud service example in the repo

The docs provide their own example, which the example could definitely be based off of

In the package.json for the demo the config doesn't match the standard port or what's reported in the readme.
"config": { "crx": "http://admin:admin@localhost:4602/crx/repository/crx.default" },

There is also groovy script support in http://felix.apache.org/documentation/subprojects/apache-felix-script-console-plugin.html. It would be nice to maintain a section in the readme which outlines the advantages of this console over the one being maintained at Apache Felix.

Is your feature request related to a problem? Please describe.
It's very easy to forget about updating META-INF/services for ServiceLoader every time HandlerFactory or ActionFactory is created/deleted.

Describe the solution you'd like
An annotation could be used to automaticaly detect factories. One existing solution is [Google's AutoService](https://github.com/google/auto/tree/mast

We are trying to improve our AEM development practices. The first step of that for us is to determine the best path for an initial sync to local development environments. The biggest barrier has been, predictably, the time required to sync "/content" and, more specifically, "/content/dam."

What I've done so far is install Grabbit v3.0.5 on our AEM 6.0 SP3 server and v.3.0.5 on a clean, local AEM

HTL Spec was updated in June 2018 to support variable setting via data-sly-set (https://github.com/adobe/htl-spec/blob/1.4/SPECIFICATION.md#2212-set) and available in AEM 6.5 (https://docs.adobe.com/content/help/en/experience-manager-65/release-notes/sites.html), AEM 6.3 SP3 and AEM 6.4 SP1 (https://github.com/adobe/htl-spec).

This potentially means we should now recommend the usage of `data-sl

ACS Commons Tag Creator claims to replace Tag Mkaer as per https://adobe-consulting-services.github.io/acs-aem-commons/features/mcp-tools/tag-creator/index.html

The Tag Maker documentation should call out that its deprecated and add a link to Tag Creator page.

It would be great to have a feature which creates a user but then triggers the password reset functionality in AEM so the user can set his/her own password.

Of course if the actool runs again for the 2nd time, the account is not locked and the user is not required to reset the password again.

(AEM already provides a bit of this functionality, although the overall documentation could be impro

While going over the Wiki and the markdown files, I ran into a few files that look like they're supposed to show examples and counterexamples of valid/invalid code.

Examples:

• https://github.com/Cognifide/AEM-Rules-for-SonarQube/blob/master/src/main/resources/rules/HTL-11.md
• https://github.com/Cognifide/AEM-Rules-for-SonarQube/blob/master/src/main/resources/rules/AEM-15.md

Please confir

Is your feature request related to a problem? Please describe.
AEM Dialogs support helpPaths which surface as help links in a componen's dialog. Since we have such nice docs pages for each component, we should link out to them using this mechanism!

For example..

Currently the sample refetch doesn't include possible vanity url and aliases of a flushed path.

It would be nice to add it so that it would also automatically regenerate those url pro actively.

Version 15.6.2 of react-addons-test-utils just got published.