...
| Role | Group | Reponsibliities | HTML, CSS | JavaScript | Enterprise Components | Custom Components | HTL | JSP | Workflow | Backend Server-Side Java | ||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| AEM Administrator | Technology Operations | Monitoring of operations. Arms-Length deployment until CICD is in place. Automation of CMS care and feeding. |  | | | | | | |
| ||||||||||||||||||
| AEM Support | ||||||||||||||||||||||||||||
| AEM Deployer | ||||||||||||||||||||||||||||
| AEM Support Investigation | ||||||||||||||||||||||||||||
| AEM Developer | Enterprise | Development Standards and Stewardship |  |
Devs should only change content, but we know this will be abused. So this is viable only with publishing workflow. The approvals also should meet SOX (ie be under different stream management) | | | |
Devs should only change content, but we know this will be abused. So this is viably only if using publishing workflow. The approvals also should meet SOX (ie be under different stream management) | |
Architecture guideline to keep as much load off of AEM Publisher as possible. Where ongoing calls are required with integration, recommend using a MicroService with browser front-end calls. | ||||||||||||||||||
| Author Head | Digital Marketing | The largest region. Represent interests and sets standards for authors. |  | |
|
| | |
| | ||||||||||||||||||
| Regional Administrator | Region | User Management, Compliance | | | | | | | | |||||||||||||||||||
| Regional AEM Developer | Region | | |
| | | | | ||||||||||||||||||||
| Author | Region | Day to day update of the website using | | |
|
| | |
| | ||||||||||||||||||
| Contributor | Region | Access to very limited frequently updated content. |
|
| | |
| |||||||||||||||||||||
Subscriber Have discussed with Adobe to create a ticket based approach for self-hosted. In managed services it's based on concurrent. | Business Line to Region | Mainly used for being part of the approval workflow and very very limited area of content to update for the Region. |
|
| | |
| |||||||||||||||||||||
...
| Tier | User | Endorsed | Comment |
|---|---|---|---|
| Rendered - JavaScript, HTML | Author Developers, Authors | Client-Side Presentation Logic | |
| Adobe Components | Author Developers | ||
| User Components | |||
| HTL | Author Developers, Authors* | Server-Side Presentation Logic | |
| JSP | Author Developers | Not recommended and with exception. | This is not necessarily bad, but Adobe is recommending to move to HTL to get the benefits of a higher level more controlled library of functions. |
| Java | Not recommended for CMS and enforced by Technology OperationsServer Side ongoing Business Logic and integration. | Not endorsed except of simple key value feeds into the system protected by a facade service. |
...