DoCommerce 2.0

Design Review 10/08/2016

CU Requirements

  • D8 as backend with Commerce 2.0
  • Basic catalog
  • Rivhit integration
  • Stock support
  • PRM integration

Possible Approaches

  1. DoCommerce rewrite
    • Robust plugin system
    • Contribable
    • New technology integrations (ratchet, bower, etc)
    • A standalone repository in bitbucket
    • Possible estimate - 250h + 40h CU cust.
  2. Direct Port from DoCommerce 1.0
    • 1:1 feature specification with 1.0, no api change
    • Sense -> Master DoCommerce -> DoCommerce 2.0 -> CU DoCommerce
    • Forks per project (like today)
    • Possible estimate - 150h + 40h CU cust.

Chosen Approach:

Direct Port

 

Considerations:

  • Time + Budget

Existing Architecture

Technologies:

  • Drupal Commerce
  • Payment
  • Rivhit payment
  • Commerce Stock
  • Angular
    • ui.router
    • ngAnimate
    • ngWebsocket

Customizations:

  • Catalog appearance
  • Categories + filters
  • Checkout steps
    • Endpoint imp.
    • Angular checkout
  • Payment (rivhit)

Features List

Red Flags

  • Commerce 2.0 beta and stock not released yet

Recommendation

  • MVP Features
    • Backoffice
    • Stock
    • Rivhit
    • etc
  • Additional features
    • Proper plugin system
    • Separation of frontend / backend repositories
    • Pandora features reuse
      • Multiple payment methods

Next DRs

  • Commerce 2.0 status and API overview
  • DoCommerce 2.0 structure and signatures
  • D8 Payment & Rivhit Payment

Optional:

  • DoCommerce Plugin System
  • DoCommerce repository strategy
Made with Slides.com