Base Pages
Home page
Product list (based on categories)
Product details
Cart Page
Checkout page
Payment
Since we already have a working app, we will proceed by just splitting the view part and business logic/data part and move the view to theme and data will be passed to the theme to build the view
Webpack configuration
Webpack configuration needs to be configured properly. Need to keep chages required to be done minimal when theme structure or files changed.
The path to theme which is configured in config file currently uses the folder name to resolve the path to the theme, but this needs to be done using package name(from package .json) of theme.
Move other project related configuration that can be done to config.json file.
Decide if we can move to gatsby2.0. It gives some advantages but also there are some negative feedback.
Base Pages Home page Product list (based on categories) Product details Cart Page Checkout page Payment
Since we already have a working app, we will proceed by just splitting the view part and business logic/data part and move the view to theme and data will be passed to the theme to build the view
Webpack configuration Webpack configuration needs to be configured properly. Need to keep chages required to be done minimal when theme structure or files changed. The path to theme which is configured in config file currently uses the folder name to resolve the path to the theme, but this needs to be done using package name(from package .json) of theme.
Move other project related configuration that can be done to config.json file.
Decide if we can move to gatsby2.0. It gives some advantages but also there are some negative feedback.