Check your AEM webmaster skills: 5 helpful tips


It doesn’t take much to become a better webmaster in Adobe Experience Manager (AEM). With these five simple steps, you’ll be able to improve your skillset and become the ultimate Adobe webmaster.

There's a constant need to update a website, make new pages, and keep your company's branding consistent. This will have a positive impact on your website's performance in the end – if you do it right.

5 steps to becoming the ultimate AEM webmaster

Though these tips were compiled specifically for AEM, users of other platforms will find a lot of these helpful as well. These five tips will help you stand out, and more importantly, will help improve your website's performance.

Communicate all progress

Oftentimes, progress may be delayed or even halted for a specific reason. Let's say a new component has been developed for a page. You fill it in with the correct copy of the text, and then you notice some issues with the design. This will need to be fixed in the next development cycle and ends up slowing down your progress.

It's in everyone's best interest to tell your stakeholders whenever there's an impact on your delivery speed. Transparent communication is key, building trust and confidence between all parties involved.

This doesn't mean that only negative news should be communicated. If progress is going faster than previously estimated, it's a great idea to inform your stakeholders then, as well.

Use out of the box functionality

When creating pages for a website, there's a tendency to customize specific components for very unique needs. But more often than not, you can actually find a way to realize the requirements with out-of-the-box functionalities.

A current example is AEM's new styling system. Whenever there's a need to create a custom component for a new style, you may be better off using an AEM core component.

Listen to the underlying problem

It may seem easy to suggest solutions to problems stated by stakeholders. But more often than not, there's an underlying problem not voiced out loud.

For example, a stakeholder states that a list component should actually be formatted differently. A quick solution would be to suggest using another component which fits the stakeholder's needs, but it’s more helpful to find out why exactly this is an issue. Place yourself in the other party's shoes and ask why the stakeholder wants the list formatted differently.

Maybe the underlying issue is another component on the page that doesn't look good with the list. Or the list itself could be improved by using a different style. The answers to these questions can lead you to the real issue plaguing the stakeholder.

Check the assets

Within the Digital Asset Manager (DAM) of AEM, we often see images or other assets with an unacceptable size. We're talking of sometimes even 15+ MB images, which can cause the website to load very slowly. So before using assets on your page, please adapt the size and be aware of the impact they can have.

Apply user feedback

Reach out to your designers, marketers and other developers before publishing – and to your users, after going live. Any of the stakeholders may notice specific styles, text changes, or other components that could fit better with your current page.

In the case of users, A/B testing can help determine which call to action (CTA) generates more clicks. What was different, and what made that CTA better?

In the end, user feedback is the information that counts in a lot of cases, even outside an AEM or website building context.

Overall, the most important step of all is communication. This is by far the most valuable quality anyone in any role can have. With the proper communication skills, you’ll be successful.

That's it! If you keep the above in mind and apply those five steps, you're well on your way to becoming a truly great webmaster.