Setting up Webstore and Admin views


This article is an overview of the required approach of copying Theme Webstore views into the Admin. 

Approach to create a symbolic link

The most efficient approach is to create a symbolic link between the Webstore and the Admin, which will take care of all the files that are needed to be copied. We would also recommend using source control to manage the templates and not relying on uploading/editing templates through the admin. Checking the templates into source control and deploying them will solve most cases of a mismatch.

The webstore renders templates based on what’s in the webstore directory, these files are versioned control and deployed by what’s in the repo. 

The admin has the content pages, where it can be configured and preview the pages, to do this it’s pulling from its own directory which is a copy or symbolic link from the webstore.

The upload tool accepts a template file and puts it on disk in the admin directory.

Uploading templates through the admin is used as a registration tool to make templates available for pages to inherit from. The admin is not meant as a place to continuously upload changes to templates. For this purpose, it is recommended that the development is done, changes/templates are committed to source control, and then deploy a new build.

Path to Webstore and Admin

It may help to outline the paths of the Webstore 


and the Admin


to help illustrate where the Theme gets placed for the symbolic link.

Any additional information that will help tie the admin and webstore directories for theme development and widget creation would help as well. This will also need to be set up to register the CMS admin functionality properly.

Did you find it helpful? Yes No

Send feedback
Sorry we couldn't be helpful. Help us improve this article with your feedback.