Neto 6 Theme Directory Restructure

In Neto 6, we will be restructuring the directory framework for Neto themes. Currently the Neto theme files are contained in two separate directories. To simplify things for designers using our system, we have decided to consolidate them into a single directory.

By having a single directory for files relevant to your Neto theme, managing your theme in version control becomes easier and finding files relevant to your theme even more so.

Current Folder Structure

Themes consist of two core components: templates and assets. Pre-Neto 6, these are stored separately from each other on the file server:

/
├── httpdocs/
│   ├── assets/
│   │   ├── themes/
│   │   │   ├── skeletal/
├── private/
│   ├── www/
│   │   ├── netosuite/
│   │   │   ├── Templates/
│   │   │   │   ├── skeletal/

In the folder structure above, both skeletal directories are relevant to your theme, but they are arbitrarily separated. This makes it difficult to find the correct directory for your theme and also makes version control complicated as you do not have a single directory for your repository. Most people get around this by including everything, all the way up to httpdocs and private in their repository. While this works, it makes deploying your theme to your website harder than it needs to be.

What is changing?

In Neto 6, we are moving your templates into the assets folder. The contents of private/www/netosuite/Templates/skeletal/ will be moved into a new templates folder under /httpdocs/assets/themes/skeletal/.

The final directory structure will be something like this:

/
├── httpdocs/
│   ├── assets/
│   │   ├── themes/
│   │   │   ├── skeletal/
│   │   │   │   ├── templates/
│   │   │   │   │   ├── cart/...
│   │   │   │   │   ├── cms/...
│   │   │   │   │   ├── customer/...
│   │   │   │   │   ├── footers/...
│   │   │   │   │   ├── headers/...
│   │   │   │   │   ├── products/...
│   │   │   │   │   ├── stockists/...
│   │   │   │   │   ├── thumbs/...
│   │   │   │   ├── js/...
│   │   │   │   ├── css/...

Note that while this new templates directory is adjacent to the assets directories (js/CSS/images), it will only be accessible via FTP. Someone visiting /httpdocs/assets/themes/skeletal/templates/headers/template.html won't be able to see the source code for your template in their browser.

How does this affect me?

What this means for most third-party designers is that they will need to access their templates in this new directory via FTP. Nothing else should change.

Developers who already use version control for their theme will need to restructure their themes repository to match the new directory structure to ensure it still works when uploaded/deployed.

To do this, copy your templates directory (private/www/netosuite/Templates/THEMENAME/</code>) into your assets directory (/httpdocs/assets/themes/THEMENAME/</code>) and rename it to templates, as the new directory structure documented above.


Was this article useful?

Be notified when this page is updated. Optional.