Universal Editor and Edge Delivery: A Seamless Duo for AEM

After writing my first article on Edge Delivery Services (here’s the link if you missed it!), where I compared Traditional AEM and Edge Delivery Services, I was encouraged to explore the Universal Editor. So, here I am with my second post, diving deeper into Edge and how it works with Universal Editor.

In my previous article, I kind of focused on comparing Edge implementation focusing on Document-Based Authoring with Traditional AEM. This post, however, revolves around using Edge Publishing with Universal Editor and how it addresses various challenges in the authoring process.

Why Universal Editor for Edge Delivery Services?

When Adobe first introduced Document-Based Authoring, I was genuinely excited to see how it worked with Edge. The idea of using something as intuitive as Google Docs or SharePoint Documents for CMS felt like a game-changer.

With Document-Based Authoring, content authors could create and manage content without needing extensive training or prior knowledge of AEM. It's as simple as working with a document editor, and features like Sidekick further extend its functionality for seamless authoring.

However, while Document-Based Authoring simplifies many aspects, it also leaves gaps for advanced use cases:

1. In-Context Editing: Lacking real-time editing in the actual site context.
2. Complex Business Processes: Difficulty in setting up intricate workflows.
3. Missing Core AEM Features: No built-in support for translation, rollouts, tagging, or extensive metadata management.

For existing AEM customers accustomed to traditional authoring workflows, adopting Document-Based Authoring can be little challenging.

I feel this is where Universal Editor comes in—a proactive solution from Adobe to address these challenges. It provides a robust alternative for authoring while retaining the scalability and flexibility of Edge Publishing.

There are some good documentation available to explain how content authoring can be done with Universal Editor, i recommend referring this to understand it more.

How Do You Choose Between Universal Editor and Document-Based Authoring?

Now that we have two ways to author content in Edge Publishing, how do you decide which one is right for your needs? Let’s break it down:

Authoring Needs

When it comes to authoring, the choice between Universal Editor and Document-Based Authoring depends on the complexity of your requirements.

Universal Editor is designed to handle complex authoring needs more effortlessly. Whether you’re dealing with intricate workflows, Multisite Management (MSM), translation setups, or advanced authoring management, Universal Editor stands out as the go-to option. It offers the robust tools needed to manage challenging and multifaceted authoring tasks efficiently.

On the other hand, Document-Based Authoring is perfect for simpler authoring needs. This approach is ideal for teams that want a quick, straightforward setup and don’t require formal training. If your authors are comfortable using familiar tools like Google Docs or SharePoint, Document-Based Authoring is an excellent choice for its simplicity and ease of use.

Content Storage

Another key factor to consider is where your content will be stored.

Universal Editor stores authored content in AEM nodes (JCR), providing a centralized and robust content repository. This approach ensures data security and aligns well with customers who prioritize control over their content’s storage and location.

In contrast, Document-Based Authoring stores content in external platforms like Google Drive or SharePoint. While this can be convenient for some teams, it may not appeal to customers who have concerns about data location, privacy, or relying on third-party platforms for content storage.

Existing vs. New AEM Customers

The decision may also depend on whether you are an existing AEM customer or new to the platform. This is something i have realized basis my experience.

Existing Customers who are accustomed to traditional AEM workflows typically prefer Universal Editor. It integrates seamlessly with their established processes and leverages the capabilities they have relied on for years.

For New Customers, Document-Based Authoring can be particularly appealing. Its simplicity, ease of use, and minimal setup requirements make it an attractive choice for businesses that are just starting their journey with AEM.

By understanding your authoring needs, content storage preferences, and customer profile, you can make an informed decision on which option best suits your business.

Beyond Edge Delivery Services: The Power of Universal Editor

Universal Editor is a powerful, flexible tool with applications far beyond Edge Delivery Services. While this post focuses on its role in Edge, it’s equally effective as a standalone solution for various authoring needs.

I’m excited to explore its broader potential in future posts too :)

The Way Forward

Adobe has done an excellent job offering flexibility with these two authoring options in Edge Publishing. Depending on your business needs and use cases, you can choose either and still achieve incredible performance (and YES achieving a perfect 100 Lighthouse score! :) ) with Edge Delivery Services.

What do you think about Universal Editor? Have you tried it yet? Let me know your thoughts and experiences in the comments below!