Compare commits
3 commits
main
...
feat/hugo-
| Author | SHA1 | Date | |
|---|---|---|---|
| 6875b82e61 | |||
| 63627e9b2b | |||
| 532be6f0ad |
18 changed files with 69 additions and 181 deletions
|
|
@ -13,7 +13,7 @@ jobs:
|
|||
build:
|
||||
runs-on: docker
|
||||
container:
|
||||
image: hugomods/hugo:exts-0.148.1
|
||||
image: hugomods/hugo:dart-sass-0.158.0
|
||||
steps:
|
||||
- name: Pipeline info
|
||||
run: |
|
||||
|
|
|
|||
98
README.md
98
README.md
|
|
@ -29,60 +29,27 @@ 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.
|
||||
See [Automated Deployment](#automated-deployment) for the way the deployment is set up on git.hamburg.ccc.de
|
||||
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.
|
||||
|
||||
### Previewing Changes Locally
|
||||
### Add Pages
|
||||
|
||||
To run a local version, just install HUGO by following the [instructions](https://gohugo.io/installation/) for your operating system.
|
||||
Note that you also need to install the [Dart Sass compiler](https://sass-lang.com/dart-sass/).
|
||||
|
||||
To build the website and run a development webserver, execute:
|
||||
```shell
|
||||
hugo server --buildFuture --buildDrafts
|
||||
hugo server
|
||||
```
|
||||
|
||||
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:
|
||||
To also build posts in the future or in draft state, run this instead:
|
||||
```shell
|
||||
hugo new content --kind article blog/yyyy/yyyy-mm-dd-your-article-title/index.md
|
||||
hugo server -D
|
||||
```
|
||||
|
||||
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
|
||||
|
||||
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.
|
||||
|
||||
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.
|
||||
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:
|
||||
|
|
@ -90,48 +57,29 @@ 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
|
||||
```
|
||||
|
||||
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.
|
||||
#### 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
|
||||
```
|
||||
|
||||
#### Additional Notes on Events and Articles
|
||||
|
||||
By default the first 70 words are shown as a summary on list pages.
|
||||
Please use `<!--more-->` (white space matters) to manually separate the summary from other post content.
|
||||
Please use `<!--more-->` 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).
|
||||
|
||||
#### 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.
|
||||
When using the commands above, the template shall have evenything you need.
|
||||
|
||||
#### Populate the Event Calendar
|
||||
|
||||
|
|
|
|||
|
|
@ -3,3 +3,8 @@ 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.
|
||||
|
|
|
|||
|
|
@ -2,7 +2,9 @@
|
|||
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:
|
||||
|
|
@ -22,4 +24,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.
|
||||
|
|
@ -1,30 +0,0 @@
|
|||
---
|
||||
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.
|
||||
|
|
@ -20,7 +20,6 @@ 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?
|
||||
|
||||
|
|
|
|||
|
|
@ -1,10 +0,0 @@
|
|||
---
|
||||
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.
|
||||
|
|
@ -1,10 +1,10 @@
|
|||
---
|
||||
title: "Digitale Selbstverteidigung"
|
||||
title: "Crypto-Gruppe"
|
||||
draft: false
|
||||
headless: true
|
||||
type: card
|
||||
#image: cryptoparty-300x100.png
|
||||
image: cryptoparty-300x100.png
|
||||
link: https://wiki.hamburg.ccc.de/club:cryptogruppe:start
|
||||
---
|
||||
|
||||
Die Gruppe befasst sich mit Datenschutz, Verschlüsselung, Backup-Strategien und vielem mehr.
|
||||
Die Cryptogruppe befasst sich mit digitaler Selbstverteidigung und veranstaltet u.a. Cryptoparties in Hamburg.
|
||||
|
|
|
|||
|
|
@ -1,10 +0,0 @@
|
|||
---
|
||||
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.
|
||||
|
|
@ -1,10 +0,0 @@
|
|||
---
|
||||
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.
|
||||
|
|
@ -1,10 +0,0 @@
|
|||
---
|
||||
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.
|
||||
|
|
@ -1,5 +1,5 @@
|
|||
baseURL = 'https://hamburg.ccc.de/'
|
||||
languageCode = 'de-de'
|
||||
locale = 'de-de'
|
||||
defaultContentLanguage = 'de'
|
||||
timeZone = 'Europe/Berlin'
|
||||
title = 'CCC Hansestadt Hamburg e.V.'
|
||||
|
|
|
|||
|
|
@ -1,3 +1,6 @@
|
|||
@use "sass:map";
|
||||
@use "sass:math";
|
||||
|
||||
$roomstate_color_unknown: #dda218;
|
||||
$roomstate_color_open: var(--ins-color);
|
||||
$roomstate_color_closed: var(--del-color);
|
||||
|
|
@ -164,7 +167,12 @@ body>main {
|
|||
margin-bottom: 1rem;
|
||||
}
|
||||
|
||||
h1, h2, h3, h4, h5, h6 {
|
||||
h1,
|
||||
h2,
|
||||
h3,
|
||||
h4,
|
||||
h5,
|
||||
h6 {
|
||||
margin: 0.5rem 1rem;
|
||||
}
|
||||
|
||||
|
|
@ -202,7 +210,7 @@ body>main {
|
|||
display: block;
|
||||
margin: 0 auto;
|
||||
// (250px - 2*var(--grid-spacing-horizontal)) * 3/4
|
||||
max-height: (222px * 3/4);
|
||||
max-height: math.div(222px * 3, 4);
|
||||
}
|
||||
|
||||
// 2*250px + 2*var(--spacing) + 1px
|
||||
|
|
@ -211,7 +219,7 @@ body>main {
|
|||
|
||||
img.groups-img {
|
||||
// (150px - 2*var(--grid-spacing-horizontal)) * 3/4
|
||||
max-height: (122px*3/4);
|
||||
max-height: math.div(122px*3, 4);
|
||||
}
|
||||
}
|
||||
|
||||
|
|
@ -221,7 +229,7 @@ body>main {
|
|||
|
||||
img.groups-img {
|
||||
// (350px - 2*var(--grid-spacing-horizontal)) * 3/4
|
||||
max-height: (322px*3/4);
|
||||
max-height: math.div(322px*3, 4);
|
||||
}
|
||||
|
||||
// 2*350px + 2*var(--spacing) + 1px
|
||||
|
|
@ -230,7 +238,7 @@ body>main {
|
|||
|
||||
img.groups-img {
|
||||
// (250px - 2*var(--grid-spacing-horizontal)) * 3/4
|
||||
max-height: (222px*3/4);
|
||||
max-height: math.div(222px*3, 4);
|
||||
}
|
||||
}
|
||||
}
|
||||
|
|
@ -295,7 +303,7 @@ body>main {
|
|||
// When the header content doesn't display nicely anymore, switch to mobile mode.
|
||||
@import "../pico-1.5.11/scss/variables";
|
||||
|
||||
@media (max-width: map-get($breakpoints, md)) {
|
||||
@media (max-width: map.get($breakpoints, md)) {
|
||||
.hamburger-button {
|
||||
display: unset;
|
||||
position: absolute;
|
||||
|
|
@ -375,15 +383,15 @@ body>main {
|
|||
}
|
||||
|
||||
// Use the media queries, which we need, from here:
|
||||
@if map-get($breakpoints, "sm") {
|
||||
@media (min-width: map-get($breakpoints, "sm")) {
|
||||
@if map.get($breakpoints, "sm") {
|
||||
@media (min-width: map.get($breakpoints, "sm")) {
|
||||
ul {
|
||||
padding-left: 0;
|
||||
padding-right: 0;
|
||||
}
|
||||
|
||||
.main-nav {
|
||||
max-width: map-get($viewports, "sm");
|
||||
max-width: map.get($viewports, "sm");
|
||||
}
|
||||
}
|
||||
}
|
||||
|
|
|
|||
|
|
@ -37,7 +37,7 @@
|
|||
<link>{{ .Permalink }}</link>
|
||||
<description>Recent content {{ if ne .Title .Site.Title }}{{ with .Title }}in {{ . }} {{ end }}{{ end }}on {{ .Site.Title }}</description>
|
||||
<generator>Hugo</generator>
|
||||
<language>{{ site.Language.LanguageCode }}</language>{{ with $authorEmail }}
|
||||
<language>{{ site.Language.Locale }}</language>{{ with $authorEmail }}
|
||||
<managingEditor>{{.}}{{ with $authorName }} ({{ . }}){{ end }}</managingEditor>{{ end }}{{ with $authorEmail }}
|
||||
<webMaster>{{ . }}{{ with $authorName }} ({{ . }}){{ end }}</webMaster>{{ end }}{{ with .Site.Copyright }}
|
||||
<copyright>{{ . }}</copyright>{{ end }}{{ if not .Date.IsZero }}
|
||||
|
|
|
|||
|
|
@ -7,14 +7,9 @@
|
|||
{{- $events := where (.Site.GetPage "blog").Pages ".Params.categories" "event" }}
|
||||
{{- $lookback := time.ParseDuration "-6h" }}
|
||||
{{- $upcoming := where $events ".Params.date" "ge" (time.Now.Add $lookback) }}
|
||||
|
||||
{{- $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 }}
|
||||
{{ if $upcoming }}
|
||||
<div class="announcements">
|
||||
<h2 id="aktuell" class="on-hover-trg">Aktuell <a href="#aktuell" class="on-hover"><i class="fa-solid fa-link small"></i></a></h2>
|
||||
<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 $upcoming.ByDate }}
|
||||
<div class="announcement">
|
||||
{{- partial "blog-header.html" (dict "headingLink" true "level" 4 "reduced" true "page" . ) }}
|
||||
|
|
@ -29,8 +24,16 @@
|
|||
{{- end }}
|
||||
</div>
|
||||
{{- end }}
|
||||
</div>
|
||||
{{- end }}
|
||||
|
||||
{{- range $articleNew.ByDate.Reverse }}
|
||||
{{- $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 }}
|
||||
<div class="announcement">
|
||||
{{- partial "blog-header.html" (dict "headingLink" true "level" 4 "reduced" true "page" . ) }}
|
||||
|
||||
|
|
@ -44,7 +47,6 @@
|
|||
{{- end }}
|
||||
</div>
|
||||
{{- end }}
|
||||
<p>Wir pflegen ein <a href="blog">Archiv aller Neuigkeiten</a>.</p>
|
||||
</div>
|
||||
{{- end }}
|
||||
|
||||
|
|
|
|||
|
|
@ -14,12 +14,7 @@
|
|||
{{- 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>
|
||||
|
|
@ -30,7 +25,6 @@
|
|||
{{- end -}}
|
||||
</span>
|
||||
{{- end }}
|
||||
{{- end }}
|
||||
{{- if $showTags }}
|
||||
{{- with .Page.GetTerms "tags" }}
|
||||
<span class="li-space"><i class="fa-solid fa-tag"></i>
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
{{- $cssOptionsMain := dict "transpiler" "libsass" "targetPath" "css/style.css" -}}
|
||||
{{- $cssOptionsPico := dict "transpiler" "libsass" "targetPath" "css/pico.css" -}}
|
||||
{{- $cssOptionsMain := dict "transpiler" "dartsass" "targetPath" "css/style.css" -}}
|
||||
{{- $cssOptionsPico := dict "transpiler" "dartsass" "targetPath" "css/pico.css" -}}
|
||||
{{- $jsResources := resources.Match "js/*.js" }}
|
||||
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0">
|
||||
|
|
|
|||
|
|
@ -1,4 +1,4 @@
|
|||
{{- index .Site.Data "calendar.json" }}
|
||||
{{- index hugo.Data "calendar.json" }}
|
||||
<table>
|
||||
<thead>
|
||||
<tr>
|
||||
|
|
@ -8,7 +8,7 @@
|
|||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
{{- range first 7 (sort $.Site.Data.calendar "dtstart" ) }}
|
||||
{{- range first 7 (sort hugo.Data.calendar "dtstart" ) }}
|
||||
{{- if eq ._type "vevent"}}
|
||||
<tr>
|
||||
{{- $start := time .dtstart }}
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue