Update docker.io/pretalx/standalone Docker tag to v2025.2.3

docs/concepts-and-configurations/documentation-structure.md

@@ -0,0 +1,16 @@
+---
+title: Documentation Structure
+order: 1
+summary: >-
+  How our documentation is organized and what we do to balance ease of writing and understanding.
+---
+
+!!! info "ToDo"
+
+    This section needs updating
+
+- Docs should be english
+- Guides are for step-by-step things
+  - Guides always have a "Goal" explicitly formulated
+- Concepts and Configuration aim to make readers understand something in detail
+

docs/concepts-and-configurations/index.md

@@ -0,0 +1,10 @@
+---
+title: Concepts and Configurations
+order: 0
+sidebar_title: Start
+summary: >-
+  Concepts and configurations is a selection of how we organize and manage our infrastructure.  You can find here how processes are planned, how services are expected to integrate with each other and how they are configured.
+
+---
+
+

docs/concepts-and-configurations/who-we-are.md

@@ -0,0 +1,17 @@
+---
+title: Who We Are and What We Do
+---
+
+We are the infrastructure team of the [Chaos Computer Club Hansestadt Hamburg](https://hambugr.ccc.de).
+ We operate all the infrastructure related to that club in a fun, sustainable and cooperative way.
+We are always open for new ideas and discussions and you can reach us at [infra@hamburg.ccc.de](mailto:infra@hamburg.ccc.de) or directly in the hackerspace.
+
+In doing so we operate on common values of **trust**, **fun**, helping each other learn, and of course the [Hacker Ethics](https://www.ccc.de/en/hackerethics).
+
+Topics that interest us and which we engage in:
+
+- Networking in our local club (See [Networking in Z9](./networking_in_z9.md))
+- Operating our own bare metal servers in Club and our local data center (See [Managed Resources](./managed-resources.md))
+- Providing services for our members and groups (See [Managed Resources](./managed-resources.md))
+- Hacking on (self hosted) Smart-Home services and automation for our space (See [Club Automation](./club-automation.md))
+

docs/guides/index.md

@@ -0,0 +1,13 @@
+---
+title: Guides
+order: 0
+sidebar_title: Start
+summary: >-
+    Guides are your one-stop-shop for reaching a certain goal.
+    You want to achieve something? The relevant guide will give you step-by-step instructions on how to do it.
+---
+
+For a complete list, see the sidebar on the left but the important guides everyone should know are the following:
+
+- [Writing Documentation](./writing-documentation.md)
+

docs/guides/onboarding.md

@@ -0,0 +1,3 @@
+# Onboarding
+
+TODO

docs/guides/writing-documentation.md

@@ -0,0 +1,99 @@
+---
+title: Writing Documentation
+order: 1
+---
+
+!!! success "Goal"
+
+    How to add a new article to this documentation or modify an existing one so that it is understandable, discoverable and fosters understanding.
+
+## 1. Understand the Structure
+
+You need to understand how we write documentation and which rules and structures you should follow when you are adding things (don't worry, it's not too much).
+For this purpose, please read the accompanying document [Documentation Structure](../concepts-and-configurations/documentation-structure.md)
+
+## 2. Clone the Repository
+
+On the top right of this page is a GitHub icon which leads you to the repository containing this documentation.
+It's [git.hamburg.ccc.de/ccchh/ansible-infra.git](https://git.hamburg.ccc.de/ccchh/ansible-infra.git) btw.
+
+Go ahead and clone the repository:
+
+```shell
+git clone ssh://forgejo@git.hamburg.ccc.de/CCCHH/ansible-infra.git
+```
+
+## 3. Add/Edit your Markdown File
+
+Once you have cloned the repository, you can just edit a file in the [`docs/`](https://git.hamburg.ccc.de/CCCHH/ansible-infra/src/branch/main/docs) under the correct
+
+!!! info
+
+    Our documentation software will automatically discover any new files and assets.
+    You don't need to touch any configuration or index files.
+
+!!! note
+
+    You can preview your changes by running the following commands:
+    ```shell
+    uv venv
+    uv pip install -r docs_requirements.txt
+    mkdocs serve
+    ```
+
+When adding new content, you can use one of the templates below to get started:
+
+/// details | Template for *Guides*
+```markdown
+---
+title: My new Guide
+---
+
+!!! success "Goal"
+
+    Add s small summary describing the end-goal this guide helps a reader achieve
+
+## 1. Step One
+
+## 2. Step Two
+
+## ...
+
+## Closing Up
+
+This section is optional but if there's any way for the reader to verify their goal has been achieved, you should mention it here.
+```
+///
+
+/// details | Template for *Concepts and Configurations*
+!!! danger "TODO"
+///
+
+## 4. Open a Pull-Request
+
+After writing your changes locally, push them to the git repository and open a Pull-Request.
+
+<a target="_blank" href="https://git.hamburg.ccc.de/CCCHH/ansible-infra/compare/main...main">
+  <button style="cursor: pointer;">Open Pull-Request</button>
+</a>
+
+After the PR is opened, our CI/CD will automatically build the new documentation version and comment a link to your deployed changes on your PR.
+If everything looks good, request a review from one of the existing team members.
+
+## 5. Review a Pull-Request
+
+!!! warning
+
+    This section is meant to be done by a PR reviewer
+
+When reviewing documentation Pull-Requests, make sure of the following criteria:
+
+- All changed content should be correct and up-to-date.
+- If new content is added, it should either be clearly a guide or belong to *Concepts and Configurations*. If both content types are mixed, they should be split up.
+- Ensure all added or edited hyperlinks are working and pointing to the correct targets.
+- Look at the deployed staging version and make sure there is no rendering fuckery going on.
+
+## Closing Up
+
+After everything is merged and done your changes will be automatically deployed over at [https://infra-docs.hamburg.ccc.de/](https://infra-docs.hamburg.ccc.de/).
+

docs/index.md

@@ -1,5 +1,11 @@
 # CCCHH Infrastructure Documentation
 
-Home for CCCHH infrastructure documentation.
+Welcome, this is the home of the CCCHH infrastructure documentation.
+For an introduction, see the selection of important articles below:
+
+- [Who We Are and What We Do](./concepts-and-configurations/who-we-are.md)
+- [Onboarding](./guides/onboarding.md)
+- [Guides](./guides/index.md) for goal oriented step-by-step instructions.
+- [Concepts and Configurations](./concepts-and-configurations/index.md) for a explanations about how things work and why we things a certain way.
+- [Writing Documentation](./guides/writing-documentation.md)
 
-- **Guides**: Documentation on how to achieve various things.

mkdocs.yml

@@ -2,11 +2,13 @@ site_name: CCCHH Infrastructure Documentation
 site_url: https://infra-docs.hamburg.ccc.de
 repo_url: https://git.hamburg.ccc.de/CCCHH/ansible-infra
 copyright: MIT
+
 markdown_extensions:
   - smarty
   - admonition
   - attr_list
   - codehilite
+  - pymdownx.blocks.details
   - pymdownx.superfences:
       css_class: codehilite
 

resources/chaosknoten/pretalx/docker_compose/compose.yaml.j2

@@ -33,7 +33,7 @@ services:
       - pretalx_net
 
   pretalx:
-    image: docker.io/pretalx/standalone:v2025.1.0
+    image: docker.io/pretalx/standalone:v2025.2.3
     entrypoint: gunicorn
     command:
       - "pretalx.wsgi"
@@ -78,7 +78,7 @@ services:
       - pretalx_net
 
   celery:
-    image: docker.io/pretalx/standalone:v2025.1.0
+    image: docker.io/pretalx/standalone:v2025.2.3
     command:
       - taskworker
     restart: unless-stopped