https://github.com/protrolium/bildwissenschaft-vortok

ProcessWire site build for Laskfar Vortok • Bildwissenschaft subdomain
https://github.com/protrolium/bildwissenschaft-vortok

latte php processwire

Last synced: 21 days ago
JSON representation

ProcessWire site build for Laskfar Vortok • Bildwissenschaft subdomain

• Host: GitHub
• URL: https://github.com/protrolium/bildwissenschaft-vortok
• Owner: protrolium
• License: other
• Created: 2025-03-03T07:06:55.000Z (over 1 year ago)
• Default Branch: main
• Last Pushed: 2025-07-07T02:52:40.000Z (11 months ago)
• Last Synced: 2025-07-07T03:43:48.073Z (11 months ago)
• Topics: latte, php, processwire
• Language: Latte
• Homepage: https://bildwissenschaft.vortok.info
• Size: 40 KB
• Stars: 0
• Watchers: 1
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md
  • Contributing: CONTRIBUTING.md
  • License: LICENSE.TXT

Awesome Lists containing this project

README

          


# Laskfar Vortok • Bildwissenschaft ProcessWire

A new archive built using the ProcessWire CMF

## Table of Contents

1. [Site Structure](#site-structure)

## 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

            │── (etc)

            ├── sections

            │   ├── about.latte

            │   ├── default-page.latte

            │   ├── home.latte

            │   ├── tag.latte

            │   └── (etc)

            └── layouts

                ├── home.php

                └── default.php (main rockfrontend renderer)

```

### Templates & Layouts

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. 

## Links

* [Laskfar Vortok • Bildwissenschaft](https://bildwissenschaft.vortok.info)