Concerning viewsets

Prev | Next

Third-party companies may choose to create their own viewsets and their own theme collections, to be entirely supported by that company. Default functionality (for example, buttons that submit AJAX requests like the Apply Promo Code button on checkout) should still function as expected by formatting and submitting requests in the same way. Practically speaking, we recommend that companies begin with simpler theme development based on cities or cities2 and only develop viewsets if they wish to radically alter the layout of the views or they have specialized needs.

It should be noted that it is technically possible to completely supersede the viewset by creating a theme which contains every file normally found in the viewset, meaning that Web Store would use all the theme files and none of the underlying view files. In this instance, you are no longer really using the view from Web Store. However, this violates the principle of how views and themes work together and is not recommended. If you are changing enough files where little of the view is being used, this may be a case where creating your own viewset is a consideration.

Note that viewsets form part of the core product, so if you do decide to go this route, most likely users with Web Stores in MultiTenant environments will not be able to use your theme.

### Prev | Next