VirtoCommerce / vc-theme-default

Default theme for VirtoCommerce Storefront
http://demo.virtocommerce.com/Electronics
Other
3 stars 41 forks source link
electronics theme virtocommerce

Deprecation warning ⚠️

The theme is no longer being maintained by Virto Commerce. Developers are encouraged to check out Vue B2B Theme .

You can continue to use the theme with Virto Commerce Platform 3.x and Storefront 5.x; however, this repo will not be kept up-to-date.


Default theme for VirtoCommerce Storefront Share on Facebook Tweet Latest release Total downloads License

Build status Quality Gate Lines of codeDocumentation Ask question at https://stackoverflow.com/questions/tagged/virtocommerce Join the chat at https://gitter.im/VirtoCommerce/vc-community Contributors

Default theme for VirtoCommerce Storefront used by Electronics sample store. It includes the largest number of features and support latest updates of Storefront so it always stay actual.

Default theme UI

Main article: theme development on virtocommerce.com/docs

CMS Content folder structure

CMS Content folder structure

Getting started

  1. Install prerequisites.
  2. Clone repo.
    1. In Visual Studio, go to Team ExplorerClone → Enter https://github.com/VirtoCommerce/vc-theme-default.git as URL and C:\vc-theme-default (for example) as path.
    2. Or execute command
      git clone https://github.com/VirtoCommerce/vc-theme-default.git "C:\vc-theme-default"

      (where C:\vc-theme-default is path to folder where you want to clone repo).

  3. Link you theme repo to store. Execute:
    mklink /d "C:\vc-platform\VirtoCommerce.Platform.Web\App_Data\cms-content\Themes\Electronics\default" "C:\vc-theme-default"

    (where C:\vc-platform\VirtoCommerce.Platform.Web\App_Data\cms-content is path to CMS content storage configured at platform & storefront deployment steps, 'Electronics' is your store name and 'C:\vc-theme-default' is path to your theme repo).

  4. Open theme folder in your IDE
    1. In Visual Studio (including 2017) go to FileOpenWebsite
    2. In Visual Studio Code, go to FileOpenFolder
    3. Select C:\vc-theme-default (where C:\vc-theme-default is path to folder where you want to clone repo) and open it.
  5. Install Node.js dependencies.
    1. In Visual Studio all dependencies will be installed automatically. Just wait a few minutes.
    2. In Visual Studio Code and other editors, you need to run
      npm install

      to install Node.js dependencies.

Prerequisites

Storefront

You need to have local installation of storefront. Follow this article step-by-step to install storefront from binaries or source code.

Visual Studio 2015.3 and above (up to Visual Studio 2017.3 at least)

If you have Visual Studio 2015 with Update 3 and above, you don't need install any prerequisites. Latest versions of Node.js and Gulp already included in your Visual Studio installation and supported in built-in Task Runner Explorer.

Visual Studio from 2015 up to 2015.2

Task Runner Explorer, Node.js and Gulp already included in your Visual Studio installation. However, you need update your Node.js to at least 4.0.0.

  1. Update Node.js to v4.0.0 at least (we recommend latest LTS version). Use C:\Program Files\nodejs installation path (change Program Files to Program Files (x86) on 64-bit machine).
  2. Add Node.js installation path to External Web Tools or move $(PATH) to top: External Web Tools

Visual Studio from 2013.3 up to 2013.5

You need install:

  1. Task Runner Explorer Visual Studio extension
  2. Install Node.js v4.0.0 or above (we recommend latest LTS version)
  3. npm install gulp -g

Visual Studio Code and other editors

  1. Install Node.js v4.0.0 or above (we recommend latest LTS version)
  2. npm install gulp -g

Liquid reference

Liquid is the templating engine that powers Virto Commerce templates. Go to Liquid documentation.

Bundling & minification

Main article: bundling & minification on virtocommerce.com/docs

Bundling is a technique you can use to improve request load time. Bundling improves load time by reducing the number of requests to the server (assets such as CSS and JavaScript will be combined to single file per file format).

Minification & bundling issues

  1. ECMAscript 6 in not supported

The code

let someVar = 1;

will produce an error during minification.

  1. You should always specify field name when you create an object

The code

var id = 1;
var someObj = {id};

will result in an error during minification.

  1. Issue with file naming

How bundling and minification works

How to add bundle to layout

{{ 'bundle/scripts.js' | static_asset_url | append_version | script_tag }}

Bundling and minification process workflow

When you run the default task to bundle & minify theme, the following happens:

  1. ESLint runs and output warnings and errors in javascript code.
  2. Javascript minifies and source maps generates.
  3. CSS processes by Autoprefixer with the following browsers support (documentation may be sometimes outdated; browser versions specified in gulpfile then specified in docs, not vice versa).
  4. CSS minifies and source maps generates.

Bundling and minification flowchart

IDE configuration

Visual Studio (any version)

Bundling & minification will work automatically when you save file and on build.

Visual Studio Code

Bundling & minification will work automatically on build. If you want to automatically bundle & minify files on save, please, install & configure Blade Runnner Visual Studio Code extension.

Other editors

Run

gulp watch

on command line if you want to bundle & minify files on save or run

gulp default

manually when you need to bundle & minify theme files.

Note

Each time you get theme sources from git or when you change dependencies in bower.json, you need to run

bower install

to build Bower dependencies and run the task

gulp packJavaScript

that bundles 3rd party dependencies.

Tips & tricks

Attention: while theme including bundlesconfig.json file, you must not use Bundler & Minifier Visual Studio extension with theme. We're using gulp to bundle & minify files on theme, because it support a lot of possible customizations and has a plugins for css minification and correct source maps generation. Wrong source map generation and lack of css minification is a primary reason why we do not use Bundler & Minifier extension in Visual Studio.

Tip: if bundling & minification failed, you, probably, need to run gulp watch task manually after that. In Visual Studio, go to Task Runner Explorer and click Run on task watch. In Visual Studio Code go to Command Palette (Ctrl+Shift+P) and type

task watch

then press Enter.

The following gulp tasks available to you:

  1. default: default task. Bundles and minifies theme files.
  2. clean: removes bundled & minified files.
  3. lint: runs eslint to check for warnings & errors in javascript files. Look at eslint site for details.
  4. min and min:js, min:css, min:html: minify all or specified types of files.
  5. watch: watching to any changes on bundled & configuration files and update bundles when any change occurs.
  6. compress: creates zip package with all needed files to deploy theme on storefront.
  7. packJavaScript: creates scripts_dependencies.js bundle for all 3rd party dependencies defined in bower.json.

How to localize theme

Main article: how to localize theme on virtocommerce.com/docs

Adding new translation to theme

Storefront theme localization is very similar to VirtoCommerce Platform localization. Check it for details on working with translation files.

  1. Make a copy of <theme repository location>\locales\en.default.json file
  2. Rename the copied file to begin with your needed language 2 letter code (e.g., "es.default.json").
  3. Translate the file content.

Adding new language to store

  1. Open your store in VirtoCommerce Platform ( More → Browse → Stores → <your store> ).
  2. Check whether your language exists in the "Additional languages" available values list or add it in case it's missing: How to add language to store