Compare commits

...
Sign in to create a new pull request.

12 commits

Author SHA1 Message Date
stb
bf03e8b5a9 Rearrange home page, add link to blogs (#166)
All checks were successful
/ build (push) Successful in 17s
* Make the news section most prominent by moving "about us" down
* Add a link to all blog posts (articles and events)
* Update group cards

Reviewed-on: #166
Reviewed-by: jtbx <jtbx@noreply.git.hamburg.ccc.de>
2026-06-15 18:23:14 +02:00
d73dfb4742 Update description of groups, add missing ones (#168)
All checks were successful
/ build (push) Successful in 15s
Reviewed-on: #168
Reviewed-by: jtbx <jtbx@noreply.git.hamburg.ccc.de>
2026-06-15 18:21:49 +02:00
d4044a7486 Explain the automated deployment processes
Some checks failed
/ build (pull_request) Successful in 40s
/ cleanup-staging (pull_request) Failing after 2m17s
/ build (push) Failing after 2m30s
2026-06-14 23:49:05 +02:00
0992ff34c4 Better explain content types (#165)
Some checks failed
/ build (push) Failing after 2m28s
* make it clear that Hugo/the template distinguishes content types based on frontmatter fields
* explain what the key differences are
* link to the archetypes so people can better understand what the relevant fields are

Reviewed-on: #165
Reviewed-by: jtbx <jtbx@noreply.git.hamburg.ccc.de>
2026-06-14 21:20:52 +02:00
3df895f734 Theme: Reverse article order on start page
Some checks failed
/ build (pull_request) Successful in 41s
/ cleanup-staging (pull_request) Failing after 2m17s
/ build (push) Failing after 2m29s
articles are in the past, so sorting them in descending order will result in the most recent being the first item.
2026-06-13 20:47:23 +02:00
c43009bbb3 Theme: Fix doubled "Neuigkeiten" heading 2026-06-13 20:47:23 +02:00
da5da9fd62 Theme: Display articles for 5 days (+6 hours) 2026-06-13 20:47:23 +02:00
5572f70e96 Fix metadata of latest posts by stb (#164)
All checks were successful
/ build (push) Successful in 16s
Reviewed-on: #164
Reviewed-by: stb <stb@noreply.git.hamburg.ccc.de>
2026-06-13 20:45:11 +02:00
d82786784b Add missing location (#163)
All checks were successful
/ build (push) Successful in 15s
Reviewed-on: #163
2026-06-13 13:15:27 +02:00
d00009a594 ueberwachungsfrei: add missing tag (#162)
All checks were successful
/ build (push) Successful in 15s
Reviewed-on: #162
2026-06-13 13:00:00 +02:00
50dc772a71 Demo-Aufruf ueberwachungsfrei (#161)
Some checks failed
/ build (push) Failing after 2m28s
Reviewed-on: #161
2026-06-13 12:54:48 +02:00
k1ba
d87213881f Codeberg MV Anmeldeformular
Some checks failed
/ cleanup-staging (pull_request) Failing after 2s
/ build (push) Successful in 15s
/ build (pull_request) Failing after 16s
2026-06-11 22:55:53 +02:00
12 changed files with 165 additions and 43 deletions

View file

@ -29,25 +29,60 @@ To populate the calendar data, please run `./fetch-calendar.sh` before running h
Running the hugo command without and parameters will re-generate the site in the `public` directory.
To deploy the website, just copy the whole folder to a directory which is servered by the webserver of your preference.
Please note, that the website should be re-deployed at least daily to update the "announcement" section on the front page even if there were no changed to the content.
Please note that the website should be re-deployed at least daily to update the "announcement" section on the front page even if there were no changed to the content.
See [Automated Deployment](#automated-deployment) for the way the deployment is set up on git.hamburg.ccc.de
### Add Pages
### Previewing Changes Locally
To run a local version, just install HUGO by following the [instructions](https://gohugo.io/installation/) for your operating system.
To build the website and run a development webserver, execute:
```shell
hugo server
hugo server --buildFuture --buildDrafts
```
To also build posts in the future or in draft state, run this instead:
Note: the flags `--buildFuture --buildDrafts` makes Hugo process all content, even if the `publishDate` is still in the future, or the content is marked as `draft: true` in the frontmatter.
You usually want these flags, especially if you are preparing content that should only be shown after a certain date.
Also see [Submitting Your Content](#submitting-your-content) below.
### Adding Content
There are two basic types of posts: Events and blog posts.
Hugo and the template set distinguish between these two types based on frontmatter information.
When manually creating content, you need to take extra care to use the correct frontmatter data.
See the link to the Hugo archetypes below for details.
**If at all possible, use `hugo new content` with the appropriate parameters to create the new content file correctly.**
You should always set these frontmatter fields:
* `categories`: must be either `article` or `event`; see below.
* `date`: the date displayed for this content.
For events, that should be when the event takes place; for blog posts, it is when the post was written.
* `publishDate`: the date and time the content should be published.
Note that if you do not specify a `publishDate`, the value of `date` will be used.
* `title`: the headline of your content.
#### Add a Blog Entry
Blog posts (the archetype is called `article`) should be used for information that will be relevant for a longer period, for example explanations about technical, political or cultural topics.
Articles will be shown for a few days on the home page.
The [blog page](https://hamburg.ccc.de/blog/) shows all posts, newest first.
In addition, the `tags:` can be used to find blog posts about certain topics.
To create a new general blog post, run a command like this:
```shell
hugo server -D
hugo new content --kind article blog/yyyy/yyyy-mm-dd-your-article-title/index.md
```
If you want to create a blog post from scratch, or convert an event into a blog post, see the frontmatter data in [themes/ccchh/archetypes/article.md](themes/ccchh/archetypes/article.md).
In particular, you need to set `categories: article`.
You do not need to specify an explicit `publishDate`, as the value of `date` will be used as a fallback.
#### Add an Event Announcement
There are two basic types of posts: Events and articles.
Events will be shown on the home page from their publishing date until they have happened and shall be used for things which happen at a certain date.
Events will be shown on the home page from the frontmatter `publishDate:` until the `date:` (plus a few hours grace period).
Use them for information that is relevant for a specific event, like a talk or a meeting.
This is not limited to events organized by the CCCHH, but can also be a hint to other events which we think are related to our activities.
To create a new event blog post, run a command like this:
@ -55,29 +90,48 @@ To create a new event blog post, run a command like this:
hugo new content --kind event blog/yyyy/yyyy-mm-dd-your-event-title/index.md
```
#### Add a Blog Entry
As mentioned before, you can also create blog posts for things which aren't events.
They will only be shown in the "blog" section and posted to the RSS feeds and shall be used for things which are relevant for a longer time.
As we have much more event announcements than articles, finding articles in all blog posts can be quite a challenge.
But using these two categories enables filtering, so that the history of articles is in one list.
To create a new general blog post, run a command like this:
```shell
hugo new content --kind article blog/yyyy/yyyy-mm-dd-your-article-title/index.md
```
If you want to create an event from scratch, or convert a blog post into an event, see the frontmatter data in [themes/ccchh/archetypes/event.md](themes/ccchh/archetypes/event.md).
In particular, you need to set `categories: event`, `date:` for the date of the event, `publishDate:` for the date the content should be published, and `location:` to whereever your event takes place.
#### Additional Notes on Events and Articles
By default the first 70 words are shown as a summary on list pages.
Please use `<!--more-->` to manually separate the summary from other post content.
Please use `<!--more-->` (white space matters) to manually separate the summary from other post content.
Please prefix your folder name with a date to make browsing the content in the source code easier.
The date in the URL will be taken from the `date` field in the front matter.
Blog posts from before 2024-01-22 were imported from the previous website and have additional front matter data which is not usually needed (e.g. the lastmod value).
When using the commands above, the template shall have evenything you need.
#### Submitting Your Content
After creating the new content, or making changes to existing content please commit your changes with a meaningful commit message to a fresh branch.
Name the branch in a way that makes it easy to understand what the changes are, for example, the title of your new blog post.
Push the branch to git.hamburg.ccc.de, and create a new pull request.
Invite reviewers, or post the link to the PR to the [#infrastruktur:hamburg.ccc.de](https://matrix.to/#/#infrastruktur:hamburg.ccc.de) Matrix channel.
The changes you have made will be deployed to the staging website automatically (this might take a minute or two).
See the comments in the PR for the link to your preview.
You and the reviewers can use the link to preview the changes.
If you have set a `publishDate` to a date and time in the future, the preview will show the content as it would appear then.
Once at least one reviewer approves the PR, it will be merged and pushed to production.
This usually takes less than five minutes.
### Automated Deployment
The website is automatically rebuilt and redeployed every 20 minutes. At each build and deploy:
* The event calendar is fetched.
* Hugo renders all pages.
* All changed files are deployed to the production web server.
See [.forgejo/workflows/deploy.yaml](.forgejo/workflows/deploy.yaml) for all the details.
Additionally, for each pull request, a version of the website is deployed to the staging website under a unique URL.
The pull request will be updated with the URL, so you and the reviewers can look at the changes as they will appear after merging.
After the PR is closed, the staging URL will be removed.
#### Populate the Event Calendar

View file

@ -3,8 +3,3 @@ title: "CCC Hansestadt Hamburg e.V."
date: 2022-11-20T09:03:20-08:00
draft: false
---
## Über uns
Wir sind der Chaos Computer Club der Hansestadt Hamburg.
Bei uns handelt es sich um eine Gruppe von Menschen, die ein Interesse am kreativen Umgang mit Technik teilen.
Unsere Gesprächsthemen und Projekte reichen von Soft- und Hardware zu Datenschutz und Netzpolitik.

View file

@ -2,9 +2,7 @@
categories: article
title: 'DIDAY.org mit Unterstützung des CCCHH'
date: '2026-06-07T14:00:00+02:00' # date of the event
publishDate: '2026-06-07T14:00:00+02:00' # when to publish
draft: false
location: Z9
authors:
- stb
tags:
@ -24,4 +22,4 @@ Worum geht es beim Digital Independence Day? [Kurz gesagt](https://diday.org/de/
Das besondere: Alle können mitmachen und beitragen. Die gesamte Webseite wird als Open Source auf [codeberg.org/DI-Day/website](https://codeberg.org/DI-Day/website) von allen Interessierten gepflegt und weiterentwickelt. Und um es auch wirklich einfach zu machen, da einzusteigen, haben wir unter [Wie? Gemeinsam](https://diday.org/de/together/) Anleitungen bereitgestellt, wie ihr direkt loslegen könnt.
Der CCC Hansestadt Hamburg e.V. fungiert als Heimat für die Webseite, sowohl technisch als auch rechtlich. Aber die Inhalte kommen von euch allen! Wir freuen uns zu sehen, was in den nächsten Monaten alles dazukommen wird.
Der CCC Hansestadt Hamburg e.V. fungiert als Heimat für die Webseite, sowohl technisch als auch rechtlich. Aber die Inhalte kommen von euch allen! Wir freuen uns zu sehen, was in den nächsten Monaten alles dazukommen wird.

View file

@ -0,0 +1,30 @@
---
categories: event
title: 'Demo-Aufruf: Überwachungsfrei in Hamburg'
date: '2026-06-20T14:00:00+02:00'
publishDate: '2026-06-13T12:00:00+02:00'
draft: false
location: Hansaplatz
authors:
- stb
tags:
- event
- überwachung
- vorratsdatenspeicherung
- widerstand
---
**tl;dr** Kundgebung auf dem Hansaplatz am Samstag, 20.6., 14 Uhr, um weitreichende Überwachung in Deutschland und in Hamburg zu verhindern. Alle Infos: [Überwachungsfrei.eu](https://überwachungsfrei.eu).
Bund und Länder treiben neue Überwachungsgesetze voran. Dazu gehören biometrische Rasterfahndung, automatisierte Massendatenauswertung, die Erhebung von Bewegungsdaten aus Fahrzeugen, Vorratsdatenspeicherung und Chatkontrolle. Hinzu kommt die Auswertung von Standortdaten aus Apps, ganz ohne gesetzliche Grundlage, sowie das Training intransparenter „KIs“ mit den frisch gesammelten Daten.
<!--more-->
Gleichzeitig geraten soziale Probleme aus dem Fokus. Technische Überwachung wird als Lösung gesellschaftlicher und sozialer Herausforderungen betrachtet. Doch mehr Überwachung führt nicht zu mehr sozialer Sicherheit. Sie verschiebt Probleme, statt sie zu lösen, und verändert das Verhältnis zwischen Staat und Bevölkerung grundlegend. Schritt für Schritt wird alltägliches Verhalten unter Beobachtung gestellt und Freiheit eingeschränkt.
Kaum ein Ort in Hamburg verdeutlicht diese Entwicklung so sehr wie der Hansaplatz. Seit 2023 wird hier das Verhalten aller, die sich auf dem Platz aufhalten, durch Kameras und automatisierte Systeme erfasst und ausgewertet. Was als Ausnahme begann, wird nun zum Normalzustand: Kontinuierliche Beobachtung im öffentlichen Raum.
Wir setzen uns für den Schutz von Grundrechten und informationeller Selbstbestimmung ein. Für öffentliche Räume, in denen Menschen sich frei bewegen, austauschen und engagieren können, ohne permanent beobachtet und bewertet zu werden. Wir wollen eine Politik, die die Ursachen gesellschaftlicher Probleme angeht, statt immer neue Überwachungsmaßnahmen einzuführen.
Wir wollen das nicht hinnehmen.
Daher gehen wir auf die Straße. Am 20.06. um 14 Uhr in Hamburg, auf dem Hansaplatz.

View file

@ -20,6 +20,7 @@ Bei uns in den Räumen werden wir am *28.06.2026* an der Mitgliederversammlung d
<!--more-->
Die MV findet primär online statt, es gibt aber bei uns die Möglichkeit dieser zusammen im Hauptraum beizuwohnen und die Geschehnisse mitzuverfolgen.
Wenn ihr daran teilnehmen wollt, füllt bitte einmal das [Anmeldeformular](https://cloud.hamburg.ccc.de/apps/forms/s/jqmsHCSGR3S8brGfjZkwnfpa) aus, damit wir eine Idee haben wie viele Leute wir erwarten müssen.
## Wie funktioniert die Codeberg MV?

View file

@ -0,0 +1,10 @@
---
title: "Über uns"
date: 2026-06-13T00:00:00-02:00
draft: false
headless: true
---
Wir sind der Chaos Computer Club der Hansestadt Hamburg:
Eine Gruppe von Menschen, die ein Interesse am kreativen Umgang mit Technik teilen.
Unsere Gesprächsthemen und Projekte reichen von Soft- und Hardware zu Datenschutz und Netzpolitik.

View file

@ -1,10 +1,10 @@
---
title: "Crypto-Gruppe"
title: "Digitale Selbstverteidigung"
draft: false
headless: true
type: card
image: cryptoparty-300x100.png
#image: cryptoparty-300x100.png
link: https://wiki.hamburg.ccc.de/club:cryptogruppe:start
---
Die Cryptogruppe befasst sich mit digitaler Selbstverteidigung und veranstaltet u.a. Cryptoparties in Hamburg.
Die Gruppe befasst sich mit Datenschutz, Verschlüsselung, Backup-Strategien und vielem mehr.

View file

@ -0,0 +1,10 @@
---
title: "Digitale Selbstverteidigung"
draft: false
headless: true
type: card
# image: TODO
link: https://wiki.hamburg.ccc.de/club:cryptogruppe:start
---
Wir diskutieren mit Menschen aus der Region über netzpolitische Fragestellungen, z. B. die Digitalisierung der Hamburger Verwaltung, neue Überwachung und Polizeibefugnisse, oder die Auswirkungen von KI auf das Leben in Hamburg.

View file

@ -0,0 +1,10 @@
---
title: "Selfhosting Usergroup"
draft: false
headless: true
type: card
# image: TODO
link: https://wiki.hamburg.ccc.de/club:selfhosting:start
---
Wer seine eigenen (Heim-)Server betreiben möchte, und hinter die Kulissen der grafischen Oberflächen schauen möchte, ist hier richtig.

View file

@ -0,0 +1,10 @@
---
title: "Funkamateure"
draft: false
headless: true
type: card
# image: TODO
link: https://wiki.hamburg.ccc.de/club:amateurfunk:start
---
Kreativer Umgang mit Technik? Machen die Funkamateure seid über 100 Jahren, und natürlich auch bei uns im CCCHH.

View file

@ -7,9 +7,14 @@
{{- $events := where (.Site.GetPage "blog").Pages ".Params.categories" "event" }}
{{- $lookback := time.ParseDuration "-6h" }}
{{- $upcoming := where $events ".Params.date" "ge" (time.Now.Add $lookback) }}
{{ if $upcoming }}
{{- $article := where (.Site.GetPage "blog").Pages ".Params.categories" "article" }}
{{- $articleDisplayTime := time.ParseDuration "-126h" }}
{{- $articleNew := where $article ".Params.publishDate" "ge" (time.Now.Add $articleDisplayTime) }}
{{ if or $upcoming $articleNew }}
<div class="announcements">
<h2 id="neuigkeiten" class="on-hover-trg">Neuigkeiten <a href="#neuigkeiten" class="on-hover"><i class="fa-solid fa-link small"></i></a></h2>
<h2 id="aktuell" class="on-hover-trg">Aktuell <a href="#aktuell" class="on-hover"><i class="fa-solid fa-link small"></i></a></h2>
{{- range $upcoming.ByDate }}
<div class="announcement">
{{- partial "blog-header.html" (dict "headingLink" true "level" 4 "reduced" true "page" . ) }}
@ -24,16 +29,8 @@
{{- end }}
</div>
{{- end }}
</div>
{{- end }}
{{- $article := where (.Site.GetPage "blog").Pages ".Params.categories" "article" }}
{{- $articleDisplayTime := time.ParseDuration "-30h" }}
{{- $articleNew := where $article ".Params.publishDate" "ge" (time.Now.Add $articleDisplayTime) }}
{{ if $articleNew }}
<div class="announcements">
<h2 id="neuigkeiten" class="on-hover-trg">Neuigkeiten <a href="#neuigkeiten" class="on-hover"><i class="fa-solid fa-link small"></i></a></h2>
{{- range $articleNew.ByDate }}
{{- range $articleNew.ByDate.Reverse }}
<div class="announcement">
{{- partial "blog-header.html" (dict "headingLink" true "level" 4 "reduced" true "page" . ) }}
@ -47,6 +44,7 @@
{{- end }}
</div>
{{- end }}
<p>Wir pflegen ein <a href="blog">Archiv aller Neuigkeiten</a>.</p>
</div>
{{- end }}

View file

@ -14,7 +14,12 @@
{{- end }}
<div class="infos">
{{- if (eq .Params.categories "event") }}
<span class="li-space"><i class="fa-solid fa-calendar-day"></i> {{ .Date | time.Format "Mon, 2006-01-02 15:04" }}</span>
{{- else }}
<span class="li-space"><i class="fa-solid fa-newspaper"></i> {{ .Date | time.Format "2006-01-02" }}</span>
{{- end }}
{{- if (eq .Params.categories "event") }}
{{- with .Params.location }}
<span class="li-space">
<i class="fa-solid fa-location-dot"></i>
@ -25,6 +30,7 @@
{{- end -}}
</span>
{{- end }}
{{- end }}
{{- if $showTags }}
{{- with .Page.GetTerms "tags" }}
<span class="li-space"><i class="fa-solid fa-tag"></i>