The AEM Developer and Business User Relationship | AEM Community Blog Seeding

[#1]

The AEM Developer and Business User Relationship by Kevin Nennig

Abstract

Empower the business user while driving development in parallel.

Let’s start with a story:
Your business has requirements for a new website. Your business hires an external vendor to ‘reimagine’ the website. This new website wireframe/blueprint/skeleton structure is handed off to the development team to create the website. The marketing team (business users) submit and supply the content that needs to be on each page. The marketing team reviews the website and approves the release. Development team leads the go-live.

Months later, there are updates that are needed to the website and the marketing team needs to submit a ticket to IT to get the site updated. The update needs to fit into a development sprint and development resources need to be allocated and justified to prioritize the update. 1–2 months later the page updates have been approved and are now live on your website.

Does this story sound too familiar?
The above story represents a classical approach to website development. The business supplies the requirements and the development team creates and maintains it, a clear line. Business users can’t write code, so it has to be this way right? Nope! Many modern web platforms allow for business users to be more involved with the creation and update process because of a simple rule:

Separation of Content and Code
Rather than make a clear line outside the system, make a clear line within the system, allowing developers and business users to work in parallel on projects based on sprints, goals, priority, etc. This is how Adobe Experience Manager is designed. Developers design components and skeleton content and business users (Authors) write and publish content, make templates, structure pages, and drive the website experience.

Though AEM has separation of Content and Code this is still forgotten
Working with many different companies that come to my training sessions, I’ve seen many different ways of interacting with with the AEM system. Sadly, it’s all too common where you see the classical ‘submit a request to IT to update a page and publish it’. This is not a limitation of AEM, rather, it’s a misunderstanding of how to use and interact with Adobe Experience Manager.

Read Full Blog

The AEM Developer and Business User Relationship

Q&A

Please use this thread to ask the related questions.