Previous Article
Building Banking and Insurance Websites with AEM: A Practical Guide
1 October 2026
The real test of a content management system is not what developers can build with it. It is whether the marketing and content team can update the website on a Tuesday afternoon without filing a ticket. Adobe Experience Manager (AEM) is often described as powerful and complex, and both are true, but a well-built AEM site is one of the easiest platforms for authors to work with.
This guide walks through what authoring in AEM actually looks like day to day, the tools content teams use, and what developers need to get right so that authoring stays easy.
Author and publish: two environments
AEM separates author from publish. Authors log in to the author environment, where they create and edit content and preview it exactly as visitors will see it. Nothing they do is public until they publish it. Visitors only ever see the publish environment.
This sounds technical, but for authors it simply means they can draft, preview and get approval safely, with no risk of a half-finished page appearing on the live site.
Editing pages visually
The page editor
In classic AEM Sites, authors open a page and edit it in place. They drag components (text, images, teasers, carousels, forms) from a side panel onto the page, click a component to edit its content, and rearrange sections by dragging. A layout mode lets them resize components for different screen sizes without touching code.
Each component has a dialog with the options developers have exposed: the heading text, an image from the asset library, a link, a style variation. Authors never see HTML or CSS.
The Universal Editor
The Universal Editor is Adobe's newer visual editor. It lets authors edit content in context on almost any front end, including headless sites built in React or other frameworks and Edge Delivery Services sites, not just traditional AEM pages. For teams moving to headless or modern front ends, it means authors keep a visual "click and edit" experience instead of filling in abstract forms.
Document-based authoring with Edge Delivery Services
Edge Delivery Services adds another option: authors write pages in Google Docs or Microsoft Word, in SharePoint or Google Drive. Headings, text, images and simple tables become page sections and blocks. They preview, then publish with a click from a sidebar.
For marketing teams this is often the easiest authoring experience of all, because they already know how to use a document editor. It suits campaign pages, blogs and content-heavy sections particularly well.
Templates and components: freedom with guardrails
Authors don't start from a blank canvas. They create a page from a template (for example "Product page", "Article" or "Campaign landing page"), and the template decides:
- Which components are allowed in each area of the page.
- Which parts are locked, such as a header, footer or legal disclaimer.
- Which style options exist, through the Style System, so authors can pick "dark background" or "two-column" without custom code.
This is what keeps a large AEM site consistent even when dozens of people edit it. Authors have real freedom to build pages, but always within the brand and structure the template allows.
Reusing content instead of copying it
Content Fragments
Content Fragments are structured pieces of content, created from a model with defined fields. A "Team member" fragment might have name, role, photo and bio; a "Product" fragment might have name, price, features and terms. Authors fill in a clean form, and the fragment can then be shown on any number of pages or delivered to apps through AEM's GraphQL API.
Change the fragment once and every place it appears updates. For content that repeats (product details, office addresses, FAQs, legal text) this saves time and prevents inconsistencies.
Experience Fragments
Experience Fragments are reusable groups of components with their layout, such as a promotional banner, a newsletter sign-up block or a site footer. Build it once and place it on many pages. Experience Fragments can also be exported to other channels, for example to Adobe Target for personalisation.
Managing images, video and documents
AEM Assets is the built-in digital asset manager. Authors upload images, videos and PDFs, organise them in folders, tag them, and search for them by keyword or metadata. When adding an image to a page, they pick it from the asset finder rather than uploading it again.
Useful features for content teams include automatic renditions in different sizes, smart cropping for different screen shapes, metadata and usage rights fields, and, with Dynamic Media, images and video delivered in the right size and format for each device. Update an asset once and every page using it shows the new version.
Approvals, versions and scheduling
Workflows
AEM workflows route content for review before it goes live. A simple one sends a page to an editor; a more involved one routes it through brand, legal and compliance. Reviewers get a notification in their inbox, can preview the page, add comments, approve or send it back. The history of who did what is kept.
Versions
AEM saves versions of pages as they are edited and published. Authors can compare versions side by side and restore an earlier one if something goes wrong. That makes mistakes cheap to undo, which in turn makes authors more confident.
Scheduling and Launches
Pages can be scheduled to publish or unpublish at a set date and time, which suits time-limited offers and announcements. For bigger changes, Launches let authors prepare a future version of a whole section, such as a product relaunch or a seasonal campaign, review it in full, and promote it on the go-live date.
Running many sites and languages
Organisations with several brands, countries or languages use two AEM features heavily:
- Multi Site Manager (MSM). A master "blueprint" site is rolled out as live copies. Changes to shared content flow down automatically, while each local site can override what needs to be different.
- Language copies and translation. Content is sent to a translation service or agency directly from AEM, and the translated versions come back for review. Authors can see which pages are translated, in progress or out of date.
Together they let a small central team manage a large network of sites without copying and pasting content between them.
What a typical day looks like for an author
| Task | How it is done in AEM |
|---|---|
| Update a price or a product detail | Edit the Content Fragment once; every page using it updates |
| Launch a campaign landing page | Create a page from the campaign template, or write it in a document with Edge Delivery Services |
| Swap a hero image | Pick a new image from AEM Assets in the component dialog |
| Change the footer on every page | Edit the footer Experience Fragment |
| Publish an offer that starts next Monday | Set a scheduled publish time, or prepare it as a Launch |
| Get legal sign-off | Start the approval workflow; legal approves from their inbox |
| Fix a mistake on a live page | Restore the previous version and republish |
What developers must get right for easy authoring
AEM's authoring tools are only as good as the components and templates built on top of them. These are the things that make the difference between authors loving AEM and avoiding it:
- Clear component dialogs. Plain labels, helpful descriptions, sensible defaults, and no more fields than the author needs.
- Extend Core Components rather than reinventing them. Adobe's Core Components already handle authoring, accessibility and responsiveness well.
- Few, well-designed templates. Each template should match a real kind of page the business publishes.
- Thoughtful content models. Model Content Fragments around how content is reused, not how one page looks.
- Accurate preview. What authors see in the editor must match the live site, or they stop trusting it.
- Training and documentation. A short authoring guide with screenshots for your own components saves endless support questions.
Is AEM easy to manage?
For content teams, a well-built AEM site is easy to manage: visual editing, reusable content, built-in approvals and safe scheduling cover most of what marketing needs without developer help. The complexity sits with the development team, in modelling content well, building good components and keeping the platform healthy. That is a trade worth making for organisations with many pages, many authors, several sites or strict approval needs.
If you are planning an AEM build or want to improve the authoring experience on an existing one, our AEM developers can help with components, templates, Content Fragment models, Universal Editor and Edge Delivery Services setups. Read how AEM supports banking and insurance websites, see how we provide AEM developers, or get in touch.