Explain the automated deployment processes

Better explain content types (#165 )
* 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:36:09 +02:00 · 2026-06-14 21:29:55 +02:00
1 changed files with 1 additions and 1 deletions
--- a/README.md
+++ b/README.md
@ -131,7 +131,7 @@ See [.forgejo/workflows/deploy.yaml](.forgejo/workflows/deploy.yaml) for all the
 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.
+After the PR is closed, the URL will be removed.
 #### Populate the Event Calendar