Part 2 – Enabling Implementation of Headless Commerce Using 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.
|Microlearning – A brief introduction to Spartacus storefront for SAP Commerce Cloud and its benefits||Introduction to Spartacus – SAP Commerce Cloud – openSAP Microlearning|
An introduction to “Spartacus”, the technologies it uses, and an overview of its architecture. It also demonstrates how to install Spartacus and extend it to create your storefront
Unit 1: What Is Spartacus?
Unit 2: Why Spartacus?
Unit 3: Comparison with Accelerator
Unit 4: Basic Setup and Features Overview
Unit 5: Spartacus Technology Overview
Unit 6: Extending Spartacus
Unit 7: Architecture Overview
Unit 8: Learning and using Spartacus
|Introduction to “Spartacus” | openSAP|
|Architecture for Spartacus||CX Works | Getting Started with SAP Commerce Cloud Project Spartacus|
|SAP Instructor-Led Training Course||
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.
|This article discusses an approach suitable for small storefronts as well as the larger migrations, where a full re-implementation is recommended||CX Works | Migrate Your Accelerator-based Storefront to Project Spartacus|
|Roadmap gives the overview of the feature releases planned in 2022 and further||
|FAQ section answers most of the common questions asked on basics, implementation, SEO and roadmap etc.||Spartacus FAQ|
|Accelerator / Business feature compatibility (B2B or B2C)||Feature Compatibility|
B2B Commerce Features
If the Spartacus implementation is for B2B then please analyze the following
- B2B Features Available Now (verify the Feature Compatibility )
- 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
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
|Goal of this course is to introduce you to the routing capabilities of Spartacus and basic SEO guidelines for routing. It will also explain how to set up a Spartacus storefront and how to extend it||Routing in Spartacus|
|The goal of this course is to introduce how Spartacus leverages the SAP Commerce Cloud CMS. In the course you’ll learn how to set up Spartacus, how Spartacus uses the CMS, and how to extend Spartacus using the CMS. Additionally, the course will cover some fundamental theoretical concepts around the SAP Commerce Cloud CMS functions and how to best use them with Spartacus.||CMS in Spartacus|
This documentation explains the following,
· Installing and building Spartacus libraries with SAP commerce Cloud
· Cross Domain Web Requests, development environment, web browser support and integrations
|Getting Started with Spartacus Libraries|
|This guide explains the architecture, storefront features, customization/extension, PWA support (progressive Web App), SEO, performance optimizations and server-side rendering (SSR)||Storefront Development Guide|
There are more than 15 microlearning videos on the following topics,
Getting started with Spartacus – Introduction to Spartacus, Styling and CMS
Becoming Competent in Spartacus – Tag management, events management, and Angular Schematics / URL matchers
Integrating with Spartacus – Extensibility of Spartacus
Staying up to date with Spartacus – Moving to Angular 9 , Tag management system and updates.
|Spartacus – openSAP Microlearning|
Communities and GitHub
|Source code GitHub||
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.
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