If your organization is planning to migrate to Adobe Experience Manager (AEM), this three-part blog series provides a helpful overview of the process, including best practices and all the areas you should consider before you begin. This blog is Part 2 in our series. Read Part 1 for an overview of the migration process.
As we continue our high-level overview on the six most critical steps in an AEM migration, we hope this information will provide a clearer picture of the migration process, and what your enterprise can expect along the journey. Here are the first three steps.
- Identify the minimum viable product - The first step toward a successful migration is defining the Minimum Viable Product, the smallest thing you can build that delivers customer value (and as a bonus captures some of that value back). Here are a few pointers on what should ideally be defined:
- How much functionality is needed for a web page to be fully operable (e.g., responsiveness, navigation, third-party integrations)
- A high-level design and basic layout (for the home page, landing page and a product/content page)
- UX design guidelines (tested with Adobe Target using A/B testing and multivariate testing)
- Navigation elements (e.g., Global Navigation, header, footer)
- Site structure, content structure and pattern library (including how your content will be stored and translated)
Once this work is complete, your team can finalize wireframes and publish design guidelines.
- Begin development - Once you know the bare minimum requirements of your homepage, landing page and product/content pages, your team can start creating necessary templates and components. Based on our successful migration projects, we’ve learned a few tips:
- Keep the number of components/templates as low as possible. Aim for reusability. Keep pages and components fluid so multiple layouts can be created with the same set of templates and components. Use column control and scaffolding to assist.
- Next, finalize the JS and front-end frameworks based on the behavior and responsiveness needs of the website.
- During the development phase, the order of development is a key factor determining the success of the task at hand. Having seen multiple implementations first hand, we are able to put together an optimal order of development.
- Design guidelines and pattern library
- Static markup
- Site/content structure
- Simple content components
- Complex components that need backend functionality
- Define your QA strategy - The next step is to determine the QA strategy, including what tools will be used for QA performance and automation. The focus here should be on getting the overall strategy and long-term vision right. A few other things to consider:
- Performance monitoring and reporting for the same
- How will these tools integrate into development of the system?
- How will these tools affect continuous integrations (including your content repository and archetype definition? (The sooner you can make decisions, the better for site development.)
Watch for our third and final blog post in this series, which will provide a glimpse into the final three steps of an AEM migration.