To be an enterprise offering you should cover the below topics.
| 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. | | | ||||||
Appendix link to Administrations, Super Administrator and Who's Who.
...
...
| 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 Server Side ongoing Business Logic and integration. | Not endorsed except of simple key value feeds into the system protected by a facade service. |
... change into a table with why and if will be something open in future,
Ensure costs here if that makes sense,
General
Backend Integration (provided we follow the rules of keeping CMS to CMS) *
Backend Advanced Consulting $,
Enterprise Governance Services
Free Best Effort
Base package for a new region.
Reduction of costs as new regions enter.
Fund language support requirements.
Model of seat licence charges and bandwidth caching charges.
Expected of Author Teams
...
...
...
...
Top Reasons,
Additional Technical Reasons,
Experience Fragments - include content and layout for channels that can be managed from within or independent of Experience Manager. Control brand content on owned web properties, or affiliated properties, like Pinterest and Facebook.
Content Fragments - authoring modular and abstracted content delivery not bound to channel. Sites automatically creates versions content to synchronize variations across pages, channels and devices.
Read up on difference between fragments (Experience versus Content) |