CCCB Website (https://berlin.ccc.de/)
|
||
---|---|---|
archetypes | ||
assets | ||
config/_default | ||
content | ||
i18n | ||
layouts | ||
static | ||
themes | ||
tools | ||
.editorconfig | ||
.gitattributes | ||
.gitignore | ||
.gitmodules | ||
.hugo-params | ||
.python-version | ||
build.sh | ||
devShells.nix | ||
flake.lock | ||
flake.nix | ||
LICENSE | ||
old_config.yaml.txt | ||
packages.nix | ||
README.md | ||
requirements.txt | ||
TODO.md |
CCCB Website
This is the website of the CCCB.
Getting started
-
Clone this repo (
--recursive
is needed to check out submodules)git clone --recursive https://git.berlin.ccc.de/cccb-website-team/www.git cccb-website
-
Switch directory
cd cccb-website
-
Run hugo webserver
hugo serve
-
Point your browser to: http://localhost:1313/
To ready your site for upload, run ./build.sh
, which also generates all.ics
and adds the calendar table to index.html
.
Every change you make on the project will be reflected in your browser
as long as hugo serve
is running.
Making a change
- Use your local dev setup (see Getting started) or via the Forgejo editor.
- Make your change in
staging
branch. - Commit (and push) your change.
GitHub Actions is running the release workflow.- If successful, check Staging Website if change is correct.
- Create merge request to merge changes from
staging
toproduction
branch. Ask somebody to check merge request or if small change, merge yourself. GitHub Actions is running the release workflow.- If successfull, check Website if change is correct.
- Profit!
Nix stuff
- After entering the shell with
nix develop
, hugo is available andhugo serve
should work - Python including required packages will be available, so the
build.sh
should work without a venv - You can build the staging and production builds with
nix build .#staging-content
andnix build .#production-content
- Do not update the nixpkgs branch - 25.05 contains a newer hugo version that is incompatible with the theme (last checked June 2025)
Made with ❤️ and Hugo.