This directory/repository contains the website of the technikum29 computer museum. The official installation of this website is available at https://technikum29.de.

Since 2019-02-05, this website is managed via Github, the repository can be found at https://github.com/technikum29/technikum29-www

Since the repository is huge, we recommend a shallow copy by running git clone --depth=1 https://github.com/technikum29/technikum29-www.git. However, if you want to commit your changes, you first need to download the whole repository, for instance with git fetch --unshallow origin. This will download ~5GB of data.

Between 2012 and 2025, Version 6 of the website was based on a custom PHP toolkit. With Version 8 of this website, this technology was dropped in favour the up-to-date static site generator (SSG) 11ty. See Konvertierung-v8.md for the background. For a quick first start,

1. you need to have a JavaScript runtime such as node on your computer.
2. In the terminal, run npm install on the fresh git checkout. You only need to do this once at installation.
3. Run npx @11ty/eleventy --serve in order to spin up a development webserver. Open http://localhost:8080/ in your browser and preview your edits locally before commiting/pushing them.

The static site generator will convert all input from the src directory to output in the _site directory. Never edit the output files directly. Each file has metadata at its top (front matter). The navigation/menu/sitemap are extracted from these files, there is no more central navigation.xml file. Content files are in /de (German pages) and /en (English pages). Static assets (Pictures, Photos, CSS/JS) are supposed to be located in /shared.

For an editorial guide how to edit files and in particular about the meaning of the front matter variables, see src/de/website-guide.md, which is rendered at https://v8.technikum29.de/de/website-guide.

You can inspect the javascript SSG runtime by using Node.js debugging techniques. That is,

1. Put the keyword debugger; somewhere in the code, say for instance somewhere in data/eleventyComputed.js
2. Fire up Chrome, enter chrome://inspect into the URL bar, click on Open dedicated DevTools for Node. These are the same browser tools you typically use for client side JS debugging.
3. Invoke SKIP_HEAVY_ASSETS=1 npx --node-options=--inspect @11ty/eleventy
4. You should see some CLI output like Debugger attached..

If you put your break point cleverly, you can inspect all variables such as the holy 11ty data object. Within the computed data, this maybe a Proxy(Object) but at later times, such as during template evaluatin in _includes/default-layout.jsx, it is filled with actual data.

In order to make the user experience more convenient, a few dynamic server side functions remain even after getting rid of PHP for the content pages. This is, in particular, the content negotiating /index.php as well as the 404.php error handler which features a little regexp-based URL rewriting map for cool URIs.

In order to test this deployment method locally,

1. You need to install PHP on your computer, but you don't need an additional webserver.
2. Run BUILD_PHP=1 npx @11ty/eleventy
3. Optional: Make the router which respects the 404-handler: tee _site/router.php <<< '<?php if(file_exists(__DIR__.parse_url($_SERVER["REQUEST_URI"],PHP_URL_PATH))) return false; include"404.php";'
4. Serve: cd _site && php -S 127.0.0.1:8080 router.php

Here is an example nginx configuration for deployment:

server {
   server_name v8.technikum29.de;

   root /path/to/your/v8.technikum29.de;
   index index.php index.html index.htm;
   error_page 404 = /404.php; # important: equal sign required for allow redirection!

   location / {
      autoindex on;
      try_files $uri $uri/ =404;
   }

   location ~ \.php$ {
      # typical php-fpm configuration here
   }
}