Compare commits

...

No commits in common. "main" and "pages" have entirely different histories.
main ... pages

40 changed files with 22 additions and 904 deletions

BIN
.DS_Store vendored

Binary file not shown.

3
.gitmodules vendored
View file

@ -1,3 +0,0 @@
[submodule "themes/ananke"]
path = themes/ananke
url = https://github.com/theNewDynamic/gohugo-theme-ananke.git

View file

View file

@ -1,57 +0,0 @@
# hugo.yml
#
# Takes a repository with Hugo source, generates the static site and
# pushes the result to Codeberg pages
#
# Needs a codeberg access token (codeberg_token) as a secret in Woodpecker config
# Also uses another secret (mail) with email address for git config
#
# .domains file in the repository is copied to the output branch so custom domains work
#
# The HUGO_OUTPUT variable must be set to the build output folder configured in Hugo
#
# Exclude page pipeline to be run on "pages" branch
when:
branch:
exclude: pages
event: [push, pull_request]
# Recursive cloning is used to fully clone the themes given as Git submodules
clone:
git:
image: woodpeckerci/plugin-git
settings:
recursive: true
steps:
# Build hugo static files
build:
image: klakegg/hugo
commands:
- hugo --minify
when:
event: [pull_request, push]
publish:
image: bitnami/git
# Must be set in Woodpecker configuration
secrets: [mail, codeberg_token]
environment:
- HUGO_OUTPUT=public
commands:
# Git configuration
- git config --global user.email $MAIL
- git config --global user.name "Woodpecker CI"
- git clone -b pages https://$CODEBERG_TOKEN@codeberg.org/$CI_REPO.git $CI_REPO_NAME
# Copy build step output to repository folder
- cp -ar $HUGO_OUTPUT/. $CI_REPO_NAME/
# Needed for custom domains
- cp .domains $CI_REPO_NAME || true # Ignore if it doesn't exist
# Commit and push all static files with pipeline started timestamp
- cd $CI_REPO_NAME
- git add .
- git commit -m "Woodpecker CI ${CI_COMMIT_SHA}"
- git push
when:
event: push

1
404.html Normal file
View file

@ -0,0 +1 @@
<!doctype html><html lang=de-de><head><meta charset=utf-8><meta http-equiv=x-ua-compatible content="IE=edge,chrome=1"><title>Meine neue Hugo Seite</title><meta name=viewport content="width=device-width,minimum-scale=1"><meta name=description content><meta name=generator content="Hugo 0.111.3"><meta name=robots content="noindex, nofollow"><link rel=stylesheet href=/hugo-codeberg-pages-template/ananke/css/main.min.css><link rel=canonical href=https://joerglohrer.codeberg.page/hugo-codeberg-pages-template/404.html><meta property="og:title" content="404 Page not found"><meta property="og:description" content><meta property="og:type" content="website"><meta property="og:url" content="https://joerglohrer.codeberg.page/hugo-codeberg-pages-template/404.html"><meta itemprop=name content="404 Page not found"><meta itemprop=description content><meta name=twitter:card content="summary"><meta name=twitter:title content="404 Page not found"><meta name=twitter:description content></head><body class="ma0 avenir bg-near-white DEV"><header><div class=bg-black><nav class="pv3 ph3 ph4-ns" role=navigation><div class="flex-l justify-between items-center center"><a href=/hugo-codeberg-pages-template/ class="f3 fw2 hover-white no-underline white-90 dib">Meine neue Hugo Seite</a><div class="flex-l items-center"><div class=ananke-socials></div></div></div></nav></div></header><main class=pb7 role=main><article class="center cf pv5 measure-wide-l"><h1>This is not the page you were looking for</h1></article></main><footer class="bg-black bottom-0 w-100 pa3" role=contentinfo><div class="flex justify-between"><a class="f4 fw4 hover-white no-underline white-70 dn dib-ns pv2 ph3" href=https://joerglohrer.codeberg.page/hugo-codeberg-pages-template/>&copy; Meine neue Hugo Seite 2024</a><div><div class=ananke-socials></div></div></div></footer></body></html>

73
LICENSE
View file

@ -1,73 +0,0 @@
Apache License
Version 2.0, January 2004
http://www.apache.org/licenses/
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
1. Definitions.
"License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document.
"Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License.
"Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity.
"You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License.
"Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files.
"Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types.
"Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below).
"Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof.
"Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution."
"Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work.
2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form.
3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed.
4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions:
(a) You must give any other recipients of the Work or Derivative Works a copy of this License; and
(b) You must cause any modified files to carry prominent notices stating that You changed the files; and
(c) You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and
(d) If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License.
You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License.
5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions.
6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file.
7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License.
8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages.
9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability.
END OF TERMS AND CONDITIONS
APPENDIX: How to apply the Apache License to your work.
To apply the Apache License to your work, attach the following boilerplate notice, with the fields enclosed by brackets "[]" replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. We also recommend that a file or class name and description of purpose be included on the same "printed page" as the copyright notice for easier identification within third-party archives.
Copyright 2024 joerglohrer
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.

191
README.md
View file

@ -1,191 +0,0 @@
---
title: Deployment von Hugo auf Codeberg Pages via Woodpecker CI
author: Jörg Lohrer
description: Mit Codeberg-Pages eine eigene Webseite hosten
image: https://i.imgur.com/8CCHQZf.png
tags: Hugo, Codeberg, Woodpecker, CI
lang: de
dir: ltr
licence: CC-BY
---
Beispiel-Ergebnis: https://joerglohrer.codeberg.page/hugo-codeberg-pages-template/
# Deployment von Hugo auf Codeberg Pages via Woodpecker CI
## Anleitung zur Erstellung einer Hugo-Website auf Codeberg Pages
Diese Anleitung zeigt Dir Schritt für Schritt, wie Du eine Hugo-Website auf Codeberg Pages erstellen kannst.
### Voraussetzungen:
- Du brauchst ein [Codeberg](https://codeberg.org/)-Konto.
- Du solltest bereit sein zu teilen
- Du brauchst [Zugang zur WoodpeckerCI](https://codeberg.org/Codeberg-e.V./requests) bei Codeberg.
### Schritte
#### 1. ![](https://raw.githubusercontent.com/primer/octicons/main/icons/repo-forked-24.svg) ***Forke das Template Repository***
* Klicke auf den Fork-Button auf der Template-Seite:
https://codeberg.org/joerglohrer/hugo-codeberg-pages-template
Dadurch wird eine Kopie des Repositorys in deinem eigenen Codeberg-Konto erstellt.
#### 2. ***Ändere die `hugo.toml`-Datei***
Öffne die `hugo.toml`-Datei i![](https://raw.githubusercontent.com/primer/octicons/main/icons/git-branch-24.svg) ***main***-Branch deines Repositorys.
Ändere die erste Zeile in folgendem Format:
`baseURL = 'https://UserName.codeberg.page/RepoName`
Ersetze `UserName` durch Deinen Codeberg-Benutzernamen und `RepoName` durch den gewünschten Namen deiner Website gleichlautend mit dem Namen des Repository.
#### 3. Generiere einen Zugriffstoken:
Melden Dich bei Deinem Codeberg-Konto an und navigiere zu Einstellungen > Anwendungen: https://codeberg.org/user/settings/applications.
Klicke auf die Schaltfläche "Neue Anwendung erstellen".
Geb Deiner Anwendung einen Namen, z. B. "Hugo-Website". Aktiviere die Option "Lesen und Schreiben" unter "repository". Klicke auf die Schaltfläche "Token generieren". Kopiere den generierten Zugriffstoken.
#### 4. Füge das Repository zu einer neuen Pipeline hinzu
Melde Dich bei CI/CD: https://ci.codeberg.org/ an. Klicke auf die Schaltfläche "+ Repository hinzufügen". Wähle dein Repository aus der Liste aus und klicke auf "Aktivieren".
Wähle die Einstellungen zur gerade erstellten Pipeline aus. Klicke auf "Allgemein" und gib bei Pipeline-Pfad `.woodpecker.yml`ein. Speiche die Einstellung füge zwei Geheimnisse hinzu:
- Name: `codeberg_token` - Wert: der in Schritt 3. generierte erstellten Zugriffstoken
- Name: `mail` - Wert: Deine Mailadresse
#### 5. Erstelle Markdown-Dateien
Navigiere im Repository zu Verzeichnis `/content`. Erstelle hier beliebige Markdown-Dateien (`*.md`). Diese Dateien werden beim Pushen in das Repository automatisch durch zu einer statischen Webseite im ![](https://raw.githubusercontent.com/primer/octicons/main/icons/git-branch-24.svg) ***pages***-Branch verarbeitet
#### Fertig!
Deine aktualisierte Seite ist unter: `https://UserName.codeberg.page/RepoName` erreichbar. Sie wird automatisch aktualisiert, wenn Du Änderungen an den (Markdown-)Dateien im ![](https://raw.githubusercontent.com/primer/octicons/main/icons/git-branch-24.svg) ***main***-Branch vornimmst.
#### Noch ein paar Hinweise
- Hugo-Dokumentation https://gohugo.io/documentation/
- Codeberg Pages-Dokumentation https://docs.codeberg.org/codeberg-pages/
- Codeberg's CI Dokumentation https://docs.codeberg.org/ci/
- Woodpecker Beispiele (auch die verwendete `.woodpecker.yaml` für Hugo): https://codeberg.org/Codeberg-CI/examples)
#### Tipps:
- ***Design:*** Passe die Vorlagendateien im Verzeichnis themes an, um deiner Website einen individuellen Look zu geben.
- ***Features:*** Nutze Hugo-Module, um deine Website zu erweitern.
- ***Eigene Domain:*** Verknüpfe deine Website mit einem eigenen Domainnamen.
---
## Wie das hier alles erstellt wurde
https://toheine.net/posts/2023/website-deployment/
https://discourse.gohugo.io/t/is-it-possible-to-use-hugo-in-codeberg-page-repositories/31012/3
### [Neues Repository auf Codeberg erstellen](https://codeberg.org/repo/create)
Lizenz: Apache-2.0, Repository initalisieren Standardbranch main, Rpository zu einem Template machen
### Repo klonen
https://docs.codeberg.org/getting-started/first-repository/#option-a%3A-clone-the-newly-created%2C-empty-repository
```git clone https://codeberg.org/joerglohrer/hugo-codeberg-pages-template.git
cd hugo-codeberg-pages-template
```
### Branch `pages` erstellen
```
git switch --orphan pages
```
- `git switch`: Dieser Befehl wird verwendet, um zwischen verschiedenen Git-Branches zu wechseln.
- `--orphan`: Diese Option erzeugt einen neuen Branch, der keine Eltern-Commits hat. Er ist sozusagen völlig losgelöst von der bisherigen Commit-Historie des Repositorys.
- `pages`: Das ist der Name des neuen Branches, der erstellt wird.
```
git rm --cached -r .
```
- `git rm`: Der Befehl zum Entfernen von Dateien aus der Git-Verfolgung. Die Dateien werden nicht aus deinem Arbeitsverzeichnis gelöscht.
- `--cached`: Diese Flagge weist Git an, die Dateien nur aus dem Staging-Bereich zu entfernen, nicht aus deinem lokalen Dateisystem.
- `-r`: Diese Flagge aktiviert die rekursive Entfernung, d.h. sie zielt auf Dateien in allen Unterverzeichnissen ab.
- `.` : Der Punkt kennzeichnet "alles im aktuellen Verzeichnis und darunter".
```
nano neu.md
git add neu.md
git commit -m "neu"
git push --set-upstream origin pages
```
![](https://pad.gwdg.de/uploads/1596177b-0edd-4b54-bf40-6ee57da781b3.png)
### Hugo installieren
hugo new site hugo-codeberg-pages-template --force
### Vorbereitung für die Pipeline
#### [Access Token erstellen](https://docs.codeberg.org/advanced/access-token/)
Unter https://codeberg.org/user/settings/applications
![](https://pad.gwdg.de/uploads/f6c96753-5ec0-4171-883f-3c73b0f8b8fb.png)
Im Beispiel wird der Token-Name "hugopagetoken" generiert bei dem in den Berechtigungen unter "repository" Lesen und Schreiben ausgewählt ist.
Soblad man auf “Token generieren” klickt, erscheint der Token mit einem Hinweis, diesen jetzt zu kopieren, da er später nicht mehr angezeigt wird.
#### Geheimnisse eintragen
Auf https://ci.codeberg.org/repos das Repo hinzufügen für das die Pipeline gestartet werden soll und dort die Geheimnisse eintragen:
![](https://pad.gwdg.de/uploads/f2e2ac23-bd28-47d3-8337-7191d54cbef2.png)
Im Beispiel wird ein Geheimnis mit dem Namen `codeberg_token` mit generierte `hugopagetoken` mit dem Wert `883029f2a627c7b5fa181f24b9205a775add1ff1` eingesetzt und dann noch das Geheimnis `mail` mit der Mailadresse des dazu passenden Codeberg-Users als Wert gespeichert.
Die Geheimnisse werden zur Laufzeit als Umgebungsvariablen an einzelne Pipelineschritte übergeben.
![](https://pad.gwdg.de/uploads/71208375-05dc-4388-986e-6b5d3df9941f.png)
Unter Allgemein
![](https://pad.gwdg.de/uploads/e78b0d20-0591-4331-8c0d-f1ce388ee527.png)
`.woodpecker.yml` angeben und die Vorlage verwenden aus folgendem Pipeline Beispiel
### Codeberg Pages
https://docs.codeberg.org/codeberg-pages/
Example Pipeline
https://codeberg.org/Codeberg-CI/examples/src/branch/main/Hugo
```shell=ssh
# hugo.yml
#
# Nimmt ein Repository mit Hugo-Quellcode, generiert die statische Website und veröffentlicht das Ergebnis auf Codeberg Pages
#
# Benötigt ein Codeberg-Zugangs-Token (codeberg_token) als secret in der Woodpecker-Konfiguration
# Verwendet auch ein anderes secret (mail) mit E-Mail-Adresse für die Git-Konfiguration
#
# .domains-Datei im Repository wird in den Ausgabezweig kopiert, damit benutzerdefinierte Domains funktionieren
#
# Die Variable HUGO_OUTPUT muss auf den in Hugo konfigurierten Ausgabeordner gesetzt werden.
# Ausschluss, dass die page-pipeline auf den "pages" Zweig angewendet wird
when:
branch:
exclude: pages
event: [push, pull_request]
# Rekursives Klonen wird verwendet, um die als Git-Submodule angegebenen Themes vollständig zu klonen
clone:
git:
image: woodpeckerci/plugin-git
settings:
recursive: true
steps:
# Build hugo static files
build:
image: klakegg/hugo
commands:
- hugo --minify
when:
event: [pull_request, push]
publish:
image: bitnami/git
# Must be set in Woodpecker configuration
secrets: [mail, codeberg_token]
environment:
- HUGO_OUTPUT=public
commands:
# Git configuration
- git config --global user.email $MAIL
- git config --global user.name "Woodpecker CI"
- git clone -b pages https://$CODEBERG_TOKEN@codeberg.org/$CI_REPO.git $CI_REPO_NAME
# Copy build step output to repository folder
- cp -ar $HUGO_OUTPUT/. $CI_REPO_NAME/
# Needed for custom domains
- cp .domains $CI_REPO_NAME || true # Ignore if it doesn't exist
# Commit and push all static files with pipeline started timestamp
- cd $CI_REPO_NAME
- git add .
- git commit -m "Woodpecker CI ${CI_COMMIT_SHA}"
- git push
when:
event: push
```

File diff suppressed because one or more lines are too long

View file

@ -1,5 +0,0 @@
+++
title = '{{ replace .File.ContentBaseName "-" " " | title }}'
date = {{ .Date }}
draft = true
+++

1
categories/index.html Normal file
View file

@ -0,0 +1 @@
<!doctype html><html lang=de-de><head><meta charset=utf-8><meta http-equiv=x-ua-compatible content="IE=edge,chrome=1"><title>Meine neue Hugo Seite</title><meta name=viewport content="width=device-width,minimum-scale=1"><meta name=description content><meta name=generator content="Hugo 0.111.3"><meta name=robots content="noindex, nofollow"><link rel=stylesheet href=/hugo-codeberg-pages-template/ananke/css/main.min.css><link href=/hugo-codeberg-pages-template/categories/index.xml rel=alternate type=application/rss+xml title="Meine neue Hugo Seite"><link href=/hugo-codeberg-pages-template/categories/index.xml rel=feed type=application/rss+xml title="Meine neue Hugo Seite"><link rel=canonical href=https://joerglohrer.codeberg.page/hugo-codeberg-pages-template/categories/><meta property="og:title" content="Categories"><meta property="og:description" content><meta property="og:type" content="website"><meta property="og:url" content="https://joerglohrer.codeberg.page/hugo-codeberg-pages-template/categories/"><meta itemprop=name content="Categories"><meta itemprop=description content><meta name=twitter:card content="summary"><meta name=twitter:title content="Categories"><meta name=twitter:description content></head><body class="ma0 avenir bg-near-white DEV"><header><div class="pb3-m pb6-l bg-black"><nav class="pv3 ph3 ph4-ns" role=navigation><div class="flex-l justify-between items-center center"><a href=/hugo-codeberg-pages-template/ class="f3 fw2 hover-white no-underline white-90 dib">Meine neue Hugo Seite</a><div class="flex-l items-center"><div class=ananke-socials></div></div></div></nav><div class="tc-l pv3 ph3 ph4-ns"><h1 class="f2 f-subheadline-l fw2 light-silver mb0 lh-title">Categories</h1></div></div></header><main class=pb7 role=main><article class="cf pa3 pa4-m pa4-l"><div class="measure-wide-l center f4 lh-copy nested-copy-line-height nested-links mid-gray"></div></article><div class="mw8 center"><section class=ph4></section></div></main><footer class="bg-black bottom-0 w-100 pa3" role=contentinfo><div class="flex justify-between"><a class="f4 fw4 hover-white no-underline white-70 dn dib-ns pv2 ph3" href=https://joerglohrer.codeberg.page/hugo-codeberg-pages-template/>&copy; Meine neue Hugo Seite 2024</a><div><div class=ananke-socials></div></div></div></footer></body></html>

1
categories/index.xml Normal file
View file

@ -0,0 +1 @@
<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Categories on Meine neue Hugo Seite</title><link>https://joerglohrer.codeberg.page/hugo-codeberg-pages-template/categories/</link><description>Recent content in Categories on Meine neue Hugo Seite</description><generator>Hugo -- gohugo.io</generator><language>de-de</language><atom:link href="https://joerglohrer.codeberg.page/hugo-codeberg-pages-template/categories/index.xml" rel="self" type="application/rss+xml"/></channel></rss>

View file

@ -1,60 +0,0 @@
---
title: Deployment von Hugo auf Codeberg Pages via Woodpecker CI
author: Jörg Lohrer
description: Mit Codeberg-Pages eine eigene Webseite hosten
lang: de
dir: ltr
licence: CC-BY
---
# Deployment von Hugo auf Codeberg Pages via Woodpecker CI
Beispielseite: https://joerglohrer.codeberg.page/hugo-codeberg-pages-template/ersteseite/
## Anleitung zur Erstellung einer Hugo-Website auf Codeberg Pages
Diese Anleitung zeigt Dir Schritt für Schritt, wie Du eine Hugo-Website auf Codeberg Pages erstellen kannst.
### Voraussetzungen:
- Du brauchst ein [Codeberg](https://codeberg.org/)-Konto.
- Du solltest bereit sein zu teilen
- Du brauchst [Zugang zur WoodpeckerCI](https://codeberg.org/Codeberg-e.V./requests) bei Codeberg.
### Schritte
#### 1. ![](https://raw.githubusercontent.com/primer/octicons/main/icons/repo-forked-24.svg) ***Forke das Template Repository***
* Klicke auf den Fork-Button auf der Template-Seite:
https://codeberg.org/joerglohrer/hugo-codeberg-pages-template
Dadurch wird eine Kopie des Repositorys in deinem eigenen Codeberg-Konto erstellt.
#### 2. ***Ändere die `hugo.toml`-Datei***
Öffne die `hugo.toml`-Datei i![](https://raw.githubusercontent.com/primer/octicons/main/icons/git-branch-24.svg) ***main***-Branch deines Repositorys.
Ändere die erste Zeile in folgendem Format:
`baseURL = 'https://UserName.codeberg.page/RepoName`
Ersetze `UserName` durch Deinen Codeberg-Benutzernamen und `RepoName` durch den gewünschten Namen deiner Website gleichlautend mit dem Namen des Repository.
#### 3. Generiere einen Zugriffstoken:
Melden Dich bei Deinem Codeberg-Konto an und navigiere zu Einstellungen > Anwendungen: https://codeberg.org/user/settings/applications.
Klicke auf die Schaltfläche "Neue Anwendung erstellen".
Geb Deiner Anwendung einen Namen, z. B. "Hugo-Website". Aktiviere die Option "Lesen und Schreiben" unter "repository". Klicke auf die Schaltfläche "Token generieren". Kopiere den generierten Zugriffstoken.
#### 4. Füge das Repository zu einer neuen Pipeline hinzu
Melde Dich bei CI/CD: https://ci.codeberg.org/ an. Klicke auf die Schaltfläche "+ Repository hinzufügen". Wähle dein Repository aus der Liste aus und klicke auf "Aktivieren".
Wähle die Einstellungen zur gerade erstellten Pipeline aus. Klicke auf "Allgemein" und gib bei Pipeline-Pfad `.woodpecker.yml`ein. Speiche die Einstellung füge zwei Geheimnisse hinzu:
- Name: `codeberg_token` - Wert: der in Schritt 3. generierte erstellten Zugriffstoken
- Name: `mail` - Wert: Deine Mailadresse
#### 5. Erstelle Markdown-Dateien
Navigiere im Repository zu Verzeichnis `/content`. Erstelle hier beliebige Markdown-Dateien (`*.md`). Diese Dateien werden beim Pushen in das Repository automatisch durch zu einer statischen Webseite im ![](https://raw.githubusercontent.com/primer/octicons/main/icons/git-branch-24.svg) ***pages***-Branch verarbeitet
#### Fertig!
Deine aktualisierte Seite ist unter: `https://UserName.codeberg.page/RepoName` erreichbar. Sie wird automatisch aktualisiert, wenn Du Änderungen an den (Markdown-)Dateien im ![](https://raw.githubusercontent.com/primer/octicons/main/icons/git-branch-24.svg) ***main***-Branch vornimmst.
#### Noch ein paar Hinweise
- Hugo-Dokumentation https://gohugo.io/documentation/
- Codeberg Pages-Dokumentation https://docs.codeberg.org/codeberg-pages/
- Codeberg's CI Dokumentation https://docs.codeberg.org/ci/
- Woodpecker Beispiele (auch die verwendete `.woodpecker.yaml` für Hugo): https://codeberg.org/Codeberg-CI/examples)
#### Tipps:
- ***Design:*** Passe die Vorlagendateien im Verzeichnis themes an, um deiner Website einen individuellen Look zu geben.
- ***Features:*** Nutze Hugo-Module, um deine Website zu erweitern.
- ***Eigene Domain:*** Verknüpfe deine Website mit einem eigenen Domainnamen.

8
ersteseite/index.html Normal file
View file

@ -0,0 +1,8 @@
<!doctype html><html lang=de-de><head><meta charset=utf-8><meta http-equiv=x-ua-compatible content="IE=edge,chrome=1"><title>Deployment von Hugo auf Codeberg Pages via Woodpecker CI | Meine neue Hugo Seite</title><meta name=viewport content="width=device-width,minimum-scale=1"><meta name=description content="Mit Codeberg-Pages eine eigene Webseite hosten"><meta name=generator content="Hugo 0.111.3"><meta name=robots content="noindex, nofollow"><meta name=author content="Jörg Lohrer"><link rel=stylesheet href=/hugo-codeberg-pages-template/ananke/css/main.min.css><link rel=canonical href=https://joerglohrer.codeberg.page/hugo-codeberg-pages-template/ersteseite/><meta property="og:title" content="Deployment von Hugo auf Codeberg Pages via Woodpecker CI"><meta property="og:description" content="Mit Codeberg-Pages eine eigene Webseite hosten"><meta property="og:type" content="article"><meta property="og:url" content="https://joerglohrer.codeberg.page/hugo-codeberg-pages-template/ersteseite/"><meta property="article:section" content><meta itemprop=name content="Deployment von Hugo auf Codeberg Pages via Woodpecker CI"><meta itemprop=description content="Mit Codeberg-Pages eine eigene Webseite hosten"><meta itemprop=wordCount content="349"><meta itemprop=keywords content><meta name=twitter:card content="summary"><meta name=twitter:title content="Deployment von Hugo auf Codeberg Pages via Woodpecker CI"><meta name=twitter:description content="Mit Codeberg-Pages eine eigene Webseite hosten"></head><body class="ma0 avenir bg-near-white DEV"><header><div class=bg-black><nav class="pv3 ph3 ph4-ns" role=navigation><div class="flex-l justify-between items-center center"><a href=/hugo-codeberg-pages-template/ class="f3 fw2 hover-white no-underline white-90 dib">Meine neue Hugo Seite</a><div class="flex-l items-center"><div class=ananke-socials></div></div></div></nav></div></header><main class=pb7 role=main><div class="flex-l mt2 mw8 center"><article class="center cf pv5 ph3 ph4-ns mw7"><header><h1 class=f1>Deployment von Hugo auf Codeberg Pages via Woodpecker CI</h1></header><div class="nested-copy-line-height lh-copy f4 nested-links mid-gray"><h1 id=deployment-von-hugo-auf-codeberg-pages-via-woodpecker-ci>Deployment von Hugo auf Codeberg Pages via Woodpecker CI</h1><p>Beispielseite: <a href=https://joerglohrer.codeberg.page/hugo-codeberg-pages-template/ersteseite/>https://joerglohrer.codeberg.page/hugo-codeberg-pages-template/ersteseite/</a></p><h2 id=anleitung-zur-erstellung-einer-hugo-website-auf-codeberg-pages>Anleitung zur Erstellung einer Hugo-Website auf Codeberg Pages</h2><p>Diese Anleitung zeigt Dir Schritt für Schritt, wie Du eine Hugo-Website auf Codeberg Pages erstellen kannst.</p><h3 id=voraussetzungen>Voraussetzungen:</h3><ul><li>Du brauchst ein <a href=https://codeberg.org/>Codeberg</a>-Konto.</li><li>Du solltest bereit sein zu teilen</li><li>Du brauchst <a href=https://codeberg.org/Codeberg-e.V./requests>Zugang zur WoodpeckerCI</a> bei Codeberg.</li></ul><h3 id=schritte>Schritte</h3><h4 id=1-httpsrawgithubusercontentcomprimerocticonsmainiconsrepo-forked-24svg-forke-das-template-repository>1. <img src=https://raw.githubusercontent.com/primer/octicons/main/icons/repo-forked-24.svg alt> <em><strong>Forke das Template Repository</strong></em></h4><ul><li>Klicke auf den Fork-Button auf der Template-Seite:
<a href=https://codeberg.org/joerglohrer/hugo-codeberg-pages-template>https://codeberg.org/joerglohrer/hugo-codeberg-pages-template</a>
Dadurch wird eine Kopie des Repositorys in deinem eigenen Codeberg-Konto erstellt.</li></ul><h4 id=2-ändere-die-hugotoml-datei>2. <em><strong>Ändere die <code>hugo.toml</code>-Datei</strong></em></h4><p>Öffne die <code>hugo.toml</code>-Datei i<img src=https://raw.githubusercontent.com/primer/octicons/main/icons/git-branch-24.svg alt> <em><strong>main</strong></em>-Branch deines Repositorys.
Ändere die erste Zeile in folgendem Format:<br><code>baseURL = 'https://UserName.codeberg.page/RepoName</code>
Ersetze <code>UserName</code> durch Deinen Codeberg-Benutzernamen und <code>RepoName</code> durch den gewünschten Namen deiner Website gleichlautend mit dem Namen des Repository.</p><h4 id=3-generiere-einen-zugriffstoken>3. Generiere einen Zugriffstoken:</h4><p>Melden Dich bei Deinem Codeberg-Konto an und navigiere zu Einstellungen > Anwendungen: <a href=https://codeberg.org/user/settings/applications>https://codeberg.org/user/settings/applications</a>.
Klicke auf die Schaltfläche &ldquo;Neue Anwendung erstellen&rdquo;.
Geb Deiner Anwendung einen Namen, z. B. &ldquo;Hugo-Website&rdquo;. Aktiviere die Option &ldquo;Lesen und Schreiben&rdquo; unter &ldquo;repository&rdquo;. Klicke auf die Schaltfläche &ldquo;Token generieren&rdquo;. Kopiere den generierten Zugriffstoken.</p><h4 id=4-füge-das-repository-zu-einer-neuen-pipeline-hinzu>4. Füge das Repository zu einer neuen Pipeline hinzu</h4><p>Melde Dich bei CI/CD: <a href=https://ci.codeberg.org/>https://ci.codeberg.org/</a> an. Klicke auf die Schaltfläche &ldquo;+ Repository hinzufügen&rdquo;. Wähle dein Repository aus der Liste aus und klicke auf &ldquo;Aktivieren&rdquo;.
Wähle die Einstellungen zur gerade erstellten Pipeline aus. Klicke auf &ldquo;Allgemein&rdquo; und gib bei Pipeline-Pfad <code>.woodpecker.yml</code>ein. Speiche die Einstellung füge zwei Geheimnisse hinzu:</p><ul><li>Name: <code>codeberg_token</code> - Wert: der in Schritt 3. generierte erstellten Zugriffstoken</li><li>Name: <code>mail</code> - Wert: Deine Mailadresse</li></ul><h4 id=5-erstelle-markdown-dateien>5. Erstelle Markdown-Dateien</h4><p>Navigiere im Repository zu Verzeichnis <code>/content</code>. Erstelle hier beliebige Markdown-Dateien (<code>*.md</code>). Diese Dateien werden beim Pushen in das Repository automatisch durch zu einer statischen Webseite im <img src=https://raw.githubusercontent.com/primer/octicons/main/icons/git-branch-24.svg alt> <em><strong>pages</strong></em>-Branch verarbeitet</p><h4 id=fertig>Fertig!</h4><p>Deine aktualisierte Seite ist unter: <code>https://UserName.codeberg.page/RepoName</code> erreichbar. Sie wird automatisch aktualisiert, wenn Du Änderungen an den (Markdown-)Dateien im <img src=https://raw.githubusercontent.com/primer/octicons/main/icons/git-branch-24.svg alt> <em><strong>main</strong></em>-Branch vornimmst.</p><h4 id=noch-ein-paar-hinweise>Noch ein paar Hinweise</h4><ul><li>Hugo-Dokumentation <a href=https://gohugo.io/documentation/>https://gohugo.io/documentation/</a></li><li>Codeberg Pages-Dokumentation <a href=https://docs.codeberg.org/codeberg-pages/>https://docs.codeberg.org/codeberg-pages/</a></li><li>Codeberg&rsquo;s CI Dokumentation <a href=https://docs.codeberg.org/ci/>https://docs.codeberg.org/ci/</a></li><li>Woodpecker Beispiele (auch die verwendete <code>.woodpecker.yaml</code> für Hugo): <a href=https://codeberg.org/Codeberg-CI/examples>https://codeberg.org/Codeberg-CI/examples</a>)</li></ul><h4 id=tipps>Tipps:</h4><ul><li><em><strong>Design:</strong></em> Passe die Vorlagendateien im Verzeichnis themes an, um deiner Website einen individuellen Look zu geben.</li><li><em><strong>Features:</strong></em> Nutze Hugo-Module, um deine Website zu erweitern.</li><li><em><strong>Eigene Domain:</strong></em> Verknüpfe deine Website mit einem eigenen Domainnamen.</li></ul></div></article></div></main><footer class="bg-black bottom-0 w-100 pa3" role=contentinfo><div class="flex justify-between"><a class="f4 fw4 hover-white no-underline white-70 dn dib-ns pv2 ph3" href=https://joerglohrer.codeberg.page/hugo-codeberg-pages-template/>&copy; Meine neue Hugo Seite 2024</a><div><div class=ananke-socials></div></div></div></footer></body></html>

View file

Before

Width:  |  Height:  |  Size: 314 KiB

After

Width:  |  Height:  |  Size: 314 KiB

View file

Before

Width:  |  Height:  |  Size: 68 KiB

After

Width:  |  Height:  |  Size: 68 KiB

View file

@ -1,4 +0,0 @@
baseURL = 'https://joerglohrer.codeberg.page/hugo-codeberg-pages-template'
languageCode = 'de-de'
title = 'Meine neue Hugo Seite'
theme = 'ananke'

View file

Before

Width:  |  Height:  |  Size: 56 KiB

After

Width:  |  Height:  |  Size: 56 KiB

View file

Before

Width:  |  Height:  |  Size: 276 KiB

After

Width:  |  Height:  |  Size: 276 KiB

3
index.html Normal file
View file

@ -0,0 +1,3 @@
<!doctype html><html lang=de-de><head><meta charset=utf-8><meta http-equiv=x-ua-compatible content="IE=edge,chrome=1"><title>Meine neue Hugo Seite</title><meta name=viewport content="width=device-width,minimum-scale=1"><meta name=description content><meta name=generator content="Hugo 0.111.3"><meta name=robots content="noindex, nofollow"><link rel=stylesheet href=/hugo-codeberg-pages-template/ananke/css/main.min.css><link href=/hugo-codeberg-pages-template/index.xml rel=alternate type=application/rss+xml title="Meine neue Hugo Seite"><link href=/hugo-codeberg-pages-template/index.xml rel=feed type=application/rss+xml title="Meine neue Hugo Seite"><link rel=canonical href=https://joerglohrer.codeberg.page/hugo-codeberg-pages-template/><meta property="og:title" content="Meine neue Hugo Seite"><meta property="og:description" content><meta property="og:type" content="website"><meta property="og:url" content="https://joerglohrer.codeberg.page/hugo-codeberg-pages-template/"><meta itemprop=name content="Meine neue Hugo Seite"><meta itemprop=description content><meta name=twitter:card content="summary"><meta name=twitter:title content="Meine neue Hugo Seite"><meta name=twitter:description content></head><body class="ma0 avenir bg-near-white DEV"><header><div class="pb3-m pb6-l bg-black"><nav class="pv3 ph3 ph4-ns" role=navigation><div class="flex-l justify-between items-center center"><a href=/hugo-codeberg-pages-template/ class="f3 fw2 hover-white no-underline white-90 dib">Meine neue Hugo Seite</a><div class="flex-l items-center"><div class=ananke-socials></div></div></div></nav><div class="tc-l pv3 ph3 ph4-ns"><h1 class="f2 f-subheadline-l fw2 light-silver mb0 lh-title">Meine neue Hugo Seite</h1></div></div></header><main class=pb7 role=main><article class="cf ph3 ph5-l pv3 pv4-l f4 tc-l center measure-wide lh-copy mid-gray"></article><div class="pa3 pa4-ns w-100 w-70-ns center"><section class="w-100 mw8"><div class="relative w-100 mb4"><article class="bb b--black-10"><div class="db pv4 ph3 ph0-l no-underline dark-gray"><div class="flex flex-column flex-row-ns"><div class="blah w-100"><h1 class="f3 fw1 athelas mt0 lh-title"><a href=/hugo-codeberg-pages-template/ersteseite/ class="color-inherit dim link">Deployment von Hugo auf Codeberg Pages via Woodpecker CI</a></h1><div class="f6 f5-l lh-copy nested-copy-line-height nested-links">Deployment von Hugo auf Codeberg Pages via Woodpecker CI Beispielseite: https://joerglohrer.codeberg.page/hugo-codeberg-pages-template/ersteseite/
Anleitung zur Erstellung einer Hugo-Website auf Codeberg Pages Diese Anleitung zeigt Dir Schritt für Schritt, wie Du eine Hugo-Website auf Codeberg Pages erstellen kannst.
Voraussetzungen: Du brauchst ein Codeberg-Konto. Du solltest bereit sein zu teilen Du brauchst Zugang zur WoodpeckerCI bei Codeberg. Schritte 1. Forke das Template Repository Klicke auf den Fork-Button auf der Template-Seite: https://codeberg.org/joerglohrer/hugo-codeberg-pages-template Dadurch wird eine Kopie des Repositorys in deinem eigenen Codeberg-Konto erstellt.</div><a href=/hugo-codeberg-pages-template/ersteseite/ class="ba b--moon-gray bg-light-gray br2 color-inherit dib f7 hover-bg-moon-gray link mt2 ph2 pv1">read more</a></div></div></div></article></div></section></div></main><footer class="bg-black bottom-0 w-100 pa3" role=contentinfo><div class="flex justify-between"><a class="f4 fw4 hover-white no-underline white-70 dn dib-ns pv2 ph3" href=https://joerglohrer.codeberg.page/hugo-codeberg-pages-template/>&copy; Meine neue Hugo Seite 2024</a><div><div class=ananke-socials></div></div></div></footer></body></html>

3
index.xml Normal file
View file

@ -0,0 +1,3 @@
<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Meine neue Hugo Seite</title><link>https://joerglohrer.codeberg.page/hugo-codeberg-pages-template/</link><description>Recent content on Meine neue Hugo Seite</description><generator>Hugo -- gohugo.io</generator><language>de-de</language><atom:link href="https://joerglohrer.codeberg.page/hugo-codeberg-pages-template/index.xml" rel="self" type="application/rss+xml"/><item><title>Deployment von Hugo auf Codeberg Pages via Woodpecker CI</title><link>https://joerglohrer.codeberg.page/hugo-codeberg-pages-template/ersteseite/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://joerglohrer.codeberg.page/hugo-codeberg-pages-template/ersteseite/</guid><description>Deployment von Hugo auf Codeberg Pages via Woodpecker CI Beispielseite: https://joerglohrer.codeberg.page/hugo-codeberg-pages-template/ersteseite/
Anleitung zur Erstellung einer Hugo-Website auf Codeberg Pages Diese Anleitung zeigt Dir Schritt für Schritt, wie Du eine Hugo-Website auf Codeberg Pages erstellen kannst.
Voraussetzungen: Du brauchst ein Codeberg-Konto. Du solltest bereit sein zu teilen Du brauchst Zugang zur WoodpeckerCI bei Codeberg. Schritte 1. Forke das Template Repository Klicke auf den Fork-Button auf der Template-Seite: https://codeberg.org/joerglohrer/hugo-codeberg-pages-template Dadurch wird eine Kopie des Repositorys in deinem eigenen Codeberg-Konto erstellt.</description></item></channel></rss>

1
nocheineseite/index.html Normal file
View file

@ -0,0 +1 @@
<!doctype html><html lang=de-de><head><meta charset=utf-8><meta http-equiv=x-ua-compatible content="IE=edge,chrome=1"><title>Meine neue Hugo Seite</title><meta name=viewport content="width=device-width,minimum-scale=1"><meta name=description content="noch mehr content mit noch mehr Inhalt"><meta name=generator content="Hugo 0.111.3"><meta name=robots content="noindex, nofollow"><link rel=stylesheet href=/hugo-codeberg-pages-template/ananke/css/main.min.css><link rel=canonical href=https://joerglohrer.codeberg.page/hugo-codeberg-pages-template/nocheineseite/><meta property="og:title" content><meta property="og:description" content="noch mehr content mit noch mehr Inhalt"><meta property="og:type" content="article"><meta property="og:url" content="https://joerglohrer.codeberg.page/hugo-codeberg-pages-template/nocheineseite/"><meta property="article:section" content><meta itemprop=name content><meta itemprop=description content="noch mehr content mit noch mehr Inhalt"><meta itemprop=wordCount content="7"><meta itemprop=keywords content><meta name=twitter:card content="summary"><meta name=twitter:title content><meta name=twitter:description content="noch mehr content mit noch mehr Inhalt"></head><body class="ma0 avenir bg-near-white DEV"><header><div class=bg-black><nav class="pv3 ph3 ph4-ns" role=navigation><div class="flex-l justify-between items-center center"><a href=/hugo-codeberg-pages-template/ class="f3 fw2 hover-white no-underline white-90 dib">Meine neue Hugo Seite</a><div class="flex-l items-center"><div class=ananke-socials></div></div></div></nav></div></header><main class=pb7 role=main><div class="flex-l mt2 mw8 center"><article class="center cf pv5 ph3 ph4-ns mw7"><header><h1 class=f1></h1></header><div class="nested-copy-line-height lh-copy f4 nested-links mid-gray"><h1 id=noch-mehr-content>noch mehr content</h1><p>mit noch mehr Inhalt</p></div></article></div></main><footer class="bg-black bottom-0 w-100 pa3" role=contentinfo><div class="flex justify-between"><a class="f4 fw4 hover-white no-underline white-70 dn dib-ns pv2 ph3" href=https://joerglohrer.codeberg.page/hugo-codeberg-pages-template/>&copy; Meine neue Hugo Seite 2024</a><div><div class=ananke-socials></div></div></div></footer></body></html>

View file

@ -1,102 +0,0 @@
<!DOCTYPE html>
<html lang="de-de">
<head><script src="/dings/livereload.js?mindelay=10&amp;v=2&amp;port=1313&amp;path=dings/livereload" data-no-instant defer></script>
<meta charset="utf-8">
<meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1">
<title>My New Hugo Site</title>
<meta name="viewport" content="width=device-width,minimum-scale=1">
<meta name="description" content="">
<meta name="generator" content="Hugo 0.123.7">
<meta name="robots" content="noindex, nofollow">
<link rel="stylesheet" href="/dings/ananke/css/main.min.css" >
<link rel="canonical" href="http://localhost:1313/dings/404.html">
<meta property="og:title" content="404 Page not found" />
<meta property="og:description" content="" />
<meta property="og:type" content="website" />
<meta property="og:url" content="http://localhost:1313/dings/404.html" />
<meta itemprop="name" content="404 Page not found">
<meta itemprop="description" content=""><meta name="twitter:card" content="summary"/><meta name="twitter:title" content="404 Page not found"/>
<meta name="twitter:description" content=""/>
</head>
<body class="ma0 avenir bg-near-white">
<header>
<div class="bg-black">
<nav class="pv3 ph3 ph4-ns" role="navigation">
<div class="flex-l justify-between items-center center">
<a href="/dings/" class="f3 fw2 hover-white no-underline white-90 dib">
My New Hugo Site
</a>
<div class="flex-l items-center">
<div class="ananke-socials">
</div>
</div>
</div>
</nav>
</div>
</header>
<main class="pb7" role="main">
<article class="center cf pv5 measure-wide-l">
<h1>
This is not the page you were looking for
</h1>
</article>
</main>
<footer class="bg-black bottom-0 w-100 pa3" role="contentinfo">
<div class="flex justify-between">
<a class="f4 fw4 hover-white no-underline white-70 dn dib-ns pv2 ph3" href="http://localhost:1313/dings/" >
&copy; My New Hugo Site 2024
</a>
<div>
<div class="ananke-socials">
</div>
</div>
</div>
</footer>
</body>
</html>

View file

@ -1,119 +0,0 @@
<!DOCTYPE html>
<html lang="de-de">
<head><script src="/dings/livereload.js?mindelay=10&amp;v=2&amp;port=1313&amp;path=dings/livereload" data-no-instant defer></script>
<meta charset="utf-8">
<meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1">
<title>My New Hugo Site</title>
<meta name="viewport" content="width=device-width,minimum-scale=1">
<meta name="description" content="">
<meta name="generator" content="Hugo 0.123.7">
<meta name="robots" content="noindex, nofollow">
<link rel="stylesheet" href="/dings/ananke/css/main.min.css" >
<link href="/dings/categories/index.xml" rel="alternate" type="application/rss+xml" title="My New Hugo Site" />
<link href="/dings/categories/index.xml" rel="feed" type="application/rss+xml" title="My New Hugo Site" />
<link rel="canonical" href="http://localhost:1313/dings/categories/">
<meta property="og:title" content="Categories" />
<meta property="og:description" content="" />
<meta property="og:type" content="website" />
<meta property="og:url" content="http://localhost:1313/dings/categories/" />
<meta itemprop="name" content="Categories">
<meta itemprop="description" content=""><meta name="twitter:card" content="summary"/><meta name="twitter:title" content="Categories"/>
<meta name="twitter:description" content=""/>
</head>
<body class="ma0 avenir bg-near-white">
<header>
<div class="pb3-m pb6-l bg-black">
<nav class="pv3 ph3 ph4-ns" role="navigation">
<div class="flex-l justify-between items-center center">
<a href="/dings/" class="f3 fw2 hover-white no-underline white-90 dib">
My New Hugo Site
</a>
<div class="flex-l items-center">
<div class="ananke-socials">
</div>
</div>
</div>
</nav>
<div class="tc-l pv3 ph3 ph4-ns">
<h1 class="f2 f-subheadline-l fw2 light-silver mb0 lh-title">
Categories
</h1>
</div>
</div>
</header>
<main class="pb7" role="main">
<article class="cf pa3 pa4-m pa4-l">
<div class="measure-wide-l center f4 lh-copy nested-copy-line-height nested-links mid-gray">
</div>
</article>
<div class="mw8 center">
<section class="ph4">
</section>
</div>
</main>
<footer class="bg-black bottom-0 w-100 pa3" role="contentinfo">
<div class="flex justify-between">
<a class="f4 fw4 hover-white no-underline white-70 dn dib-ns pv2 ph3" href="http://localhost:1313/dings/" >
&copy; My New Hugo Site 2024
</a>
<div>
<div class="ananke-socials">
</div>
</div>
</div>
</footer>
</body>
</html>

View file

@ -1,11 +0,0 @@
<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
<title>Categories on My New Hugo Site</title>
<link>http://localhost:1313/dings/categories/</link>
<description>Recent content in Categories on My New Hugo Site</description>
<generator>Hugo -- gohugo.io</generator>
<language>de-de</language>
<atom:link href="http://localhost:1313/dings/categories/index.xml" rel="self" type="application/rss+xml" />
</channel>
</rss>

View file

@ -1,123 +0,0 @@
<!DOCTYPE html>
<html lang="de-de">
<head><script src="/dings/livereload.js?mindelay=10&amp;v=2&amp;port=1313&amp;path=dings/livereload" data-no-instant defer></script>
<meta charset="utf-8">
<meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1">
<title>My New Hugo Site</title>
<meta name="viewport" content="width=device-width,minimum-scale=1">
<meta name="description" content="">
<meta name="generator" content="Hugo 0.123.7">
<meta name="robots" content="noindex, nofollow">
<link rel="stylesheet" href="/dings/ananke/css/main.min.css" >
<link href="/dings/index.xml" rel="alternate" type="application/rss+xml" title="My New Hugo Site" />
<link href="/dings/index.xml" rel="feed" type="application/rss+xml" title="My New Hugo Site" />
<link rel="canonical" href="http://localhost:1313/dings/">
<meta property="og:title" content="My New Hugo Site" />
<meta property="og:description" content="" />
<meta property="og:type" content="website" />
<meta property="og:url" content="http://localhost:1313/dings/" />
<meta itemprop="name" content="My New Hugo Site">
<meta itemprop="description" content=""><meta name="twitter:card" content="summary"/><meta name="twitter:title" content="My New Hugo Site"/>
<meta name="twitter:description" content=""/>
</head>
<body class="ma0 avenir bg-near-white">
<header>
<div class="pb3-m pb6-l bg-black">
<nav class="pv3 ph3 ph4-ns" role="navigation">
<div class="flex-l justify-between items-center center">
<a href="/dings/" class="f3 fw2 hover-white no-underline white-90 dib">
My New Hugo Site
</a>
<div class="flex-l items-center">
<div class="ananke-socials">
</div>
</div>
</div>
</nav>
<div class="tc-l pv3 ph3 ph4-ns">
<h1 class="f2 f-subheadline-l fw2 light-silver mb0 lh-title">
My New Hugo Site
</h1>
</div>
</div>
</header>
<main class="pb7" role="main">
<article class="cf ph3 ph5-l pv3 pv4-l f4 tc-l center measure-wide lh-copy mid-gray">
</article>
</main>
<footer class="bg-black bottom-0 w-100 pa3" role="contentinfo">
<div class="flex justify-between">
<a class="f4 fw4 hover-white no-underline white-70 dn dib-ns pv2 ph3" href="http://localhost:1313/dings/" >
&copy; My New Hugo Site 2024
</a>
<div>
<div class="ananke-socials">
</div>
</div>
</div>
</footer>
</body>
</html>

View file

@ -1,11 +0,0 @@
<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
<title>My New Hugo Site</title>
<link>http://localhost:1313/dings/</link>
<description>Recent content on My New Hugo Site</description>
<generator>Hugo -- gohugo.io</generator>
<language>de-de</language>
<atom:link href="http://localhost:1313/dings/index.xml" rel="self" type="application/rss+xml" />
</channel>
</rss>

View file

@ -1,11 +0,0 @@
<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9"
xmlns:xhtml="http://www.w3.org/1999/xhtml">
<url>
<loc>http://localhost:1313/dings/categories/</loc>
</url><url>
<loc>http://localhost:1313/dings/</loc>
</url><url>
<loc>http://localhost:1313/dings/tags/</loc>
</url>
</urlset>

View file

@ -1,119 +0,0 @@
<!DOCTYPE html>
<html lang="de-de">
<head><script src="/dings/livereload.js?mindelay=10&amp;v=2&amp;port=1313&amp;path=dings/livereload" data-no-instant defer></script>
<meta charset="utf-8">
<meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1">
<title>My New Hugo Site</title>
<meta name="viewport" content="width=device-width,minimum-scale=1">
<meta name="description" content="">
<meta name="generator" content="Hugo 0.123.7">
<meta name="robots" content="noindex, nofollow">
<link rel="stylesheet" href="/dings/ananke/css/main.min.css" >
<link href="/dings/tags/index.xml" rel="alternate" type="application/rss+xml" title="My New Hugo Site" />
<link href="/dings/tags/index.xml" rel="feed" type="application/rss+xml" title="My New Hugo Site" />
<link rel="canonical" href="http://localhost:1313/dings/tags/">
<meta property="og:title" content="Tags" />
<meta property="og:description" content="" />
<meta property="og:type" content="website" />
<meta property="og:url" content="http://localhost:1313/dings/tags/" />
<meta itemprop="name" content="Tags">
<meta itemprop="description" content=""><meta name="twitter:card" content="summary"/><meta name="twitter:title" content="Tags"/>
<meta name="twitter:description" content=""/>
</head>
<body class="ma0 avenir bg-near-white">
<header>
<div class="pb3-m pb6-l bg-black">
<nav class="pv3 ph3 ph4-ns" role="navigation">
<div class="flex-l justify-between items-center center">
<a href="/dings/" class="f3 fw2 hover-white no-underline white-90 dib">
My New Hugo Site
</a>
<div class="flex-l items-center">
<div class="ananke-socials">
</div>
</div>
</div>
</nav>
<div class="tc-l pv3 ph3 ph4-ns">
<h1 class="f2 f-subheadline-l fw2 light-silver mb0 lh-title">
Tags
</h1>
</div>
</div>
</header>
<main class="pb7" role="main">
<article class="cf pa3 pa4-m pa4-l">
<div class="measure-wide-l center f4 lh-copy nested-copy-line-height nested-links mid-gray">
</div>
</article>
<div class="mw8 center">
<section class="ph4">
</section>
</div>
</main>
<footer class="bg-black bottom-0 w-100 pa3" role="contentinfo">
<div class="flex justify-between">
<a class="f4 fw4 hover-white no-underline white-70 dn dib-ns pv2 ph3" href="http://localhost:1313/dings/" >
&copy; My New Hugo Site 2024
</a>
<div>
<div class="ananke-socials">
</div>
</div>
</div>
</footer>
</body>
</html>

View file

@ -1,11 +0,0 @@
<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
<title>Tags on My New Hugo Site</title>
<link>http://localhost:1313/dings/tags/</link>
<description>Recent content in Tags on My New Hugo Site</description>
<generator>Hugo -- gohugo.io</generator>
<language>de-de</language>
<atom:link href="http://localhost:1313/dings/tags/index.xml" rel="self" type="application/rss+xml" />
</channel>
</rss>

BIN
resources/.DS_Store vendored

Binary file not shown.

Binary file not shown.

Binary file not shown.

File diff suppressed because one or more lines are too long

View file

@ -1 +0,0 @@
{"Target":"/ananke/css/main.min.css","MediaType":"text/css","Data":{}}

1
sitemap.xml Normal file
View file

@ -0,0 +1 @@
<?xml version="1.0" encoding="utf-8" standalone="yes"?><urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9" xmlns:xhtml="http://www.w3.org/1999/xhtml"><url><loc>https://joerglohrer.codeberg.page/hugo-codeberg-pages-template/categories/</loc></url><url><loc>https://joerglohrer.codeberg.page/hugo-codeberg-pages-template/ersteseite/</loc></url><url><loc>https://joerglohrer.codeberg.page/hugo-codeberg-pages-template/</loc></url><url><loc>https://joerglohrer.codeberg.page/hugo-codeberg-pages-template/tags/</loc></url></urlset>

1
tags/index.html Normal file
View file

@ -0,0 +1 @@
<!doctype html><html lang=de-de><head><meta charset=utf-8><meta http-equiv=x-ua-compatible content="IE=edge,chrome=1"><title>Meine neue Hugo Seite</title><meta name=viewport content="width=device-width,minimum-scale=1"><meta name=description content><meta name=generator content="Hugo 0.111.3"><meta name=robots content="noindex, nofollow"><link rel=stylesheet href=/hugo-codeberg-pages-template/ananke/css/main.min.css><link href=/hugo-codeberg-pages-template/tags/index.xml rel=alternate type=application/rss+xml title="Meine neue Hugo Seite"><link href=/hugo-codeberg-pages-template/tags/index.xml rel=feed type=application/rss+xml title="Meine neue Hugo Seite"><link rel=canonical href=https://joerglohrer.codeberg.page/hugo-codeberg-pages-template/tags/><meta property="og:title" content="Tags"><meta property="og:description" content><meta property="og:type" content="website"><meta property="og:url" content="https://joerglohrer.codeberg.page/hugo-codeberg-pages-template/tags/"><meta itemprop=name content="Tags"><meta itemprop=description content><meta name=twitter:card content="summary"><meta name=twitter:title content="Tags"><meta name=twitter:description content></head><body class="ma0 avenir bg-near-white DEV"><header><div class="pb3-m pb6-l bg-black"><nav class="pv3 ph3 ph4-ns" role=navigation><div class="flex-l justify-between items-center center"><a href=/hugo-codeberg-pages-template/ class="f3 fw2 hover-white no-underline white-90 dib">Meine neue Hugo Seite</a><div class="flex-l items-center"><div class=ananke-socials></div></div></div></nav><div class="tc-l pv3 ph3 ph4-ns"><h1 class="f2 f-subheadline-l fw2 light-silver mb0 lh-title">Tags</h1></div></div></header><main class=pb7 role=main><article class="cf pa3 pa4-m pa4-l"><div class="measure-wide-l center f4 lh-copy nested-copy-line-height nested-links mid-gray"></div></article><div class="mw8 center"><section class=ph4></section></div></main><footer class="bg-black bottom-0 w-100 pa3" role=contentinfo><div class="flex justify-between"><a class="f4 fw4 hover-white no-underline white-70 dn dib-ns pv2 ph3" href=https://joerglohrer.codeberg.page/hugo-codeberg-pages-template/>&copy; Meine neue Hugo Seite 2024</a><div><div class=ananke-socials></div></div></div></footer></body></html>

1
tags/index.xml Normal file
View file

@ -0,0 +1 @@
<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Tags on Meine neue Hugo Seite</title><link>https://joerglohrer.codeberg.page/hugo-codeberg-pages-template/tags/</link><description>Recent content in Tags on Meine neue Hugo Seite</description><generator>Hugo -- gohugo.io</generator><language>de-de</language><atom:link href="https://joerglohrer.codeberg.page/hugo-codeberg-pages-template/tags/index.xml" rel="self" type="application/rss+xml"/></channel></rss>

BIN
themes/.DS_Store vendored

Binary file not shown.

@ -1 +0,0 @@
Subproject commit f34c219436ab1c3b116f8706a521d40c4b8693b9