Part 2 – Enabling Implementation of Headless Commerce Using Composable Storefront (Spartacus)

Once the planning and implementation strategy is completed, the next step is to look at the aids support the implementation phase. It is always a challenge to find the correct and latest information which are scattered in various channels like Spartacus documentation, CX works, microlearning and openSAP trainings. The primary aim of the article is to provide one page of access to all resources for the development team.

Introduction to Spartacus

The first step of the implementation is to enable the development team technically in Spartacus. Most of the team may be new to the headless approach. They need to know about the product, its modules and how it works before starting any development activities. The following training modules help the team to know the product in detail.

Analysis Phase Guidance

Once the team is familiar with Spartacus architecture and modules, they need to plan the implementation. The team also needs to compare the current implementation of the accelerator-based storefront to the new front-end headless architecture and do the feature analysis (if they are running already on SAP Commerce Cloud). They also need to review the impact of existing custom code, CMS, Google Analytics, and SEO implementations. The roadmap review will help the team decide whether to develop the features or wait for the release. The guidance resources listed below will help the team complete the analysis phase and enable the team to contribute effectively to the project planning, deployment, and schedules.

B2B Commerce Features 

If the Spartacus implementation is for B2B then please analyze the following

• B2B Features Available Now (verify the Compatibility Matrix | SAP Help Portal)
  • Fully Available in Spartacus release – Fully functional and integrated with back-end via OCC (Omni Commerce Connect)
  • OCC Layer Alone Available – In some cases, the OCC API layer is available, but the related frontend has yet to be released. This is true for some B2B cases and will enable the business to develop their own UI storefront for the feature and go live quickly, without necessarily waiting for UI to be released

• Release notes and B2B Features roadmap
  • SAP Road Map Explorer. roadmap will give an idea about the features which will be released in near and future. This will help the team to decide whether to wait for the feature or go ahead with own development based on the priority and complexity

Implementation Enablement Sources

Even though the team completed analysis in the elaboration phase, they may get into the situation where they need more help and guidance on the development. When the team is starting the development, they need in-depth and detailed technical aids and supporting materials to refer and work on. Here are some of the resources which help development team to deep dive on topics

 Communities and GitHub

Conclusion

This article is written as the second part of the part one Deliver-outstanding-customer-experience-with-headless-commerce-using-spartacus   to provide one page of access to all Spartacus resources for the development. The training improves the knowledge and delivery efficiency of the technical team, and the supporting documents save their effort on finding the information, best practices, and suggestions.

Note:

Please read the part one of this article Deliver-outstanding-customer-experience-with-headless-commerce-using-spartacus  which address some key considerations to help the business team which plan and strategize their implementation roadmap for headless architecture using a Spartacus storefront