A new studio portfolio built using the ProcessWire CMF

1. Site Structure

We are using the RockFrontEnd module to control templates, which are written in the LATTE php template engine. The structure of pages and templates is roughly as follows:

root
└── site
    └── assets
        ├── classes
        │   ├── DefaultPage.php
        │   └── HomePage.php
        └── templates
            ├── home.php
            ├── default-page.php
            ├── tag.php
            ├── tags.php
            │── (etc)
            ├── sections
            │   ├── about.latte
            │   ├── default-page.latte
            │   ├── home.latte
            │   ├── tag.latte
            │   └── (etc)
            └── layouts
                ├── home.php
                └── default.php (main rockfrontend renderer)

The action happens in the templates directory. Here we create any number of php pages and include the ProcessWire namespace in them, otherwise they are essentially empty pages acting as containers. In the layouts directory are stored any number of layouts, default.php being our main RockFrontEnd page renderer. This page will pull from the sections directory to render a template based on a page's assigned template in ProcessWire. Thus if we add a new template in ProcessWire (i.e. about) and assign pages to it, we will need to add that page to the templates directory when we try pulling in its corresponding latte files from the sections directory via default.php.

The page classes correspond to the pages in the layout directory, only in lowercase and without the word 'Page'. These custom classes extend ProcessWire Page classes, and the names must match.

• The Teaching Machine