An AEM installation generally consists of at least two environments:
These interact to enable you to make content available on your website so that your visitors can access it.
The author environment provides the mechanisms for creating, updating, and reviewing this content before actually publishing it:
- An author creates and reviews the content. Content can be of many different types such as pages, assets, publications, etc.
- This content will, at some point, be published to your website.
On the author environment the functionality of AEM is made available through AEM's authoring UI. For the publish environment you design the entire look-and-feel of the interface made available to your users.
AEM itself is used to publish the AEM documentation.
The author works in what is known as the author environment . This provides an easy to use interface (graphical user interface (GUI or UI)) for creating the content. It requires the author to login, using an account that has been assigned the appropriate access rights.
Your account needs the appropriate access rights to create, edit or publish content.
Depending on how your instance and your personal access rights are configured you can perform many tasks on your content, including (amongst others):
- Generating new content or edit existing content on a page
- Using predefined templates to create new content pages
- Creating, editing, and managing your assets and collections
- Moving, copying, and deleting content pages, assets, etc.
- Publishing (or un-publishing) pages, assets, etc.
Additionally, there are administrative tasks that help you manage your content:
- Workflows that control how changes are managed such as enforcing a review before publication
- Projects that coordinate individual tasks
AEM is also administered from the author environment.
When ready, your site's content is published to the publish environment . Here the website's pages are made available to the intended audience in accordance with the look-and-feel of the designed interface.
For more information about publishing and unpublishing pages, see the document Publishing Pages.
To optimize performance for visitors to your website, the dispatcher implements load balancing and caching.