No two platform deployments are the same. Even back-to-back implementations of the Adobe Commerce platform –for companies of similar size within the same industry – will each look and feel and play out to its own rhythms based on the many distinct characteristics of the organization and its own unique business ambitions.
So when Adobe asked dentsu to partner on the development of a detailed, comprehensive Adobe Commerce Playbook, we not only brought our deep practice expertise to the project; we also drew upon the real-life insights gained through scores of client engagements across a wide spectrum of deployment sizes, scopes, and successes – not just the easy wins, but also the demanding and hard-fought achievements.
From the early stages of project scoping and stakeholder buy-in to development, deployment, and support, each section of the playbook dives deep into the process of each stage. Additionally, these processes and considerations apply to any kind of Adobe Commerce project:
Within the playbook’s 155 pages are actionable examples, charts, checklists, and recommendations for project leaders, planners, digital experts, and technical managers, where detailed information is critically important for the success of each implementation.
The table of contents above provides a broad sense of the playbook’s scope. Some of the more specific areas of focus – among many – include:
Like any large IT project, Adobe Commerce is built on coding standards that leverage best practices and standardizations of the underlying technologies (PHP/Zend, symfony, JavaScript, jQuery, HTML, etc.), as well as standards that have been established within the Adobe Commerce Coding Standard. Following these standards is an absolute must to eliminate bugs and improve the quality and maintainability of the custom-built code.
Within the playbook, we dive deeper into some of the main standards of Adobe Commerce development. This includes:
There is no shortage of aspects that must be well thought through and rigorously tested to keep an ecommerce site running without interference. Not only must you identify the right solutions to tackle every aspect of the site – from data storage and programming to caching and security – but you need the right process to ensure the delivery of a platform that runs smoothly and can be built and optimized efficiently.
The playbook offers not only a look at the tools, solutions, processes, and methodologies that have been tested and perfected over a number of Adobe Commerce implementations, but also our recommendations of which solutions best fit specific business needs and objectives.
In addition, the playbook provides a detailed look at dentsu’s project implementation methodology, with a breakdown of our delivery and testing processes across areas like continuous integration/continuous delivery, various QC activities, and testing of UI, APIs, and automation.
We also dive into the actual platform itself, highlighting the infrastructures and environments that are powering Adobe Commerce and the software solutions that make it such a robust platform.
We detail a handful of tactical and actionable ways to optimize your Adobe Commerce instance. This includes recommendations and definitions around security, configuration, and performance optimizations, along with other section to help you understand the ins and outs of the platform, as well as easy fixes for allowing it to run at optimum speed.
Want to learn more? For the full picture, download the playbook and share it with other key stakeholders working to drive commerce transformation for your organization.
If 155 pages of playbook is more than you want to bite off right now, you can also find further information on this website – in more snackable, sharable bites – about Adobe Commerce, dentsu’s POV as an Adobe Platinum Partner, and our work for global commerce leaders:
You can also start a conversation with our commerce experts to better understand the Adobe platform and our proven approach to commerce transformation for global enterprise clients.