SAP commerce cloud project Spartacus getting started

Spartacus Is a free open source JavaScript Web Applications , It's on 2019 year 5 Month issued 1.0 edition , And new updates will continue to be released every few weeks . It allows you to SAP Commerce Cloud Quickly create your own based on JavaScript Brand store . Spartacus It's using Angular Compiling , And publish as a set of Libraries . Use JavaScript The recommended approach is to build your own JavaScript Web Application and import Spartacus library . There is no need to modify , The store can be used out of the box , but Spartacus The design can be upgraded 、 Customizable and scalable , To meet all your brand and functional requirements .

Spartacus It's using SAP Commerce Cloud A strategic approach to maintaining customizable storefronts . It replaces in SAP Commerce v4.4 Accelerator template first introduced in , To provide an off the shelf entry implementation . Even though Accelerator The template allows partners to quickly develop an omni channel experience by changing the sample store , But the template is not easy to upgrade , They are based on JSP, And the store and SAP Commerce The core platform is tightly coupled .

Spartacus Architecture

Even though Spartacus And SAP Commerce Cloud Separate , But it only applies to SAP Commerce Cloud platform . Spartacus rely on SAP Commerce Cloud API and CMS Content to run . It is 100% API Driven , Designed to run headless . You are free to expand Spartacus Included libraries to include your own customizations . Your Spartacus Implementation can also be achieved through SAP Expand the suite . because Spartacus And SAP Commerce Cloud Platform separation , Therefore, you can choose to separate front-end and back-end development , It may even have a separate deployment / Release cycle . Your Spartacus The store can also be independent of SAP Commerce Cloud Platform expansion . The only time you may need to adjust the version is SAP Commerce Cloud For Spartacus The use of API Under the circumstances . for example ,Spartacus 2.0 Version has some features that can only be used SAP Commerce core 2005 Released in API To activate .

Spartacus Use multiple languages 、 Combination of technology and Library , Include Angular、TypeScript、RxJS、NgRx、SASS and Bootstrap. The final output is pure JavaScript. Angular Currently used as a development framework , But the goal is to allow the use of other frameworks .

Spartacus Respond quickly , Including mobile 、 The tablet 、 Support for desktop and wide desktop breakpoints , However, you are free to configure your own breakpoints . Spartacus It also has a built-in progressive Web Applications (PWA) function , You can configure your store to use it . This will make your store more like a traditional native iOS/Android Mobile applications , Excellent performance, reliability and mobile native functionality .

Open SAP On Spartacus A series of learning videos link

Spartacus It's just a set of Libraries , It contains a set of core libraries 、 Components and styles . It has its own release cycle , The goal is to publish every two weeks . You have complete control over whether to accept these library updates . You can select the library version to use in your application （Spartacus Use Semantic version control 2.0）, These can be used to fully configure and customize your store . More details about major version updates , Please refer to this page .

Customization is different from the accelerator ; You never directly customize Spartacus Code —— Instead, overwrite or replace styles and codes . This approach allows easy upgrade . About extension Spartacus For more information , You can see our Video library .

Underlying Frameworks/Libraries

If you've been developing SAP Commerce Cloud Solution , You may be more familiar with our Accelerator （ As follows ）, They are based on Spring Model view controller (MVC) Applications for . because Spartacus It's a JavaScript Applications , Underlying framework / The library is completely different . At the beginning of development Spartacus Before the application , You may need to take the time to familiarize yourself with these technologies / frame .

The following covers the framework being used / The main site of the library , And it is a good reference for information that can help your development work ：

• Languages: Typescript, Sass
• Frameworks: Angular, RxJS, NgRx
• Dependency management: Yarn, npm
• Build: Angular CLI (under the hood: webpack, ng-packagr)
• Testing: Jasmine, Cypress, Karma
• Code Quality: Prettier, TSLint
• IDE: Visual Studio Code (or equivalent)
• Source control / distribution: Github, npmjs

SAP Spartacus Public class ：https://open.sap.com/courses/sparta1

SAP Commerce Cloud Accelerators

because Spartacus And SAP Commerce Cloud Separate , So you don't need to use Spartacus. You are free to create and maintain your own JavaScript Web Applications , You can also continue to use SAP Commerce Cloud Embedded in Accelerator Templates , Although these are not the strategic direction forward . At the time of release ,Spartacus Will not have a relationship with SAP Commerce Cloud Accelerators All functions of the same features , But these gaps will be in Spartacus The document covers .

If you are already using based on Accelerator And want to migrate to Spartacus, Then you'd better start from scratch . Spartacus In technology and Architecture （ Templates and Libraries 、 Headless and embedded 、JSP And Angular） Aspects are completely transformed from accelerator to paradigm . They are so different , So that it is impossible to base Accelerator The code is ported to Spartacus The store . in other words , because Spartacus And SAP Commerce Cloud Platform separation , You can run based on Accelerator Shops and Spartacus Store to simplify to Spartacus The transition of . for example , If you currently have one B2B Accelerator Store and want to set up a new B2C The store , You can use Spartacus establish B2C The store , While still hosting your B2B Accelerator store . Suppose you have set up a source repository to build and deploy B2B Accelerator The store , To add B2C The store ：

• Modify your repository to include information for building / Based on the deployment JavaScript The correct structure of the store .

• Configure your manifest.json File to define Spartacus Called API aspect.

• In your manifest.json Define a new application in the file , Pointing to your Spartacus The location of the store .

You can continue to add new Spartacus Store applications and configure your endpoints to allow specific traffic to enter your store . They are still using the same SAP Commerce Cloud platform , So you can run multiple stores at the same time , While still maintaining the same information （ Customer 、 The shopping cart 、 Orders, etc ）.

Scalability

As mentioned above , Because of your Spartacus Storefront and SAP Commerce Cloud Store separation , You can choose to extend it separately . Other extension considerations can also be leveraged （ For example, the content delivery network (CDN)） To help reduce the load . Besides ,Spartacus Will include PWA function , For example, network cache function , This will allow you to choose to cache resources locally on the user's device . Delayed loading can also be used to determine whether / When to load some components . Last , because Spartacus yes API Driven , It can take advantage of SAP Business technology platform 、Kyma The runtime and the accompanying extensible microservices quickly move to Spartacus Add new features to the store .

Server-side vs. Client-Side Rendering

By default ,Spartacus Set to client render , But you can configure server-side rendering (SSR). Consider the Advantages and disadvantages It's important to decide which option best meets your requirements . For e-commerce solutions , Usually SSR Search engine optimization (SEO) Is more important than any benefit presented by the client .

Support

You can use this slack channel