Website for data.coop
Go to file
Benjamin Bach 1321a1d0d3
All checks were successful
continuous-integration/drone/push Build is passing
build branch main automatically
2023-07-25 21:49:45 +02:00
content Fixes #1 and fixes #2 2023-07-24 20:37:08 +02:00
data/badges Updates and typo fixes 2023-07-24 01:43:35 +02:00
i18n Adding badges with status colors to service definitions 2023-03-06 19:37:48 +01:00
static Cleanup old stuff from bootstrap times 2023-04-01 22:07:07 +02:00
themes/datacoop2020 English translations of a lot of stuff, hopefully everything! 2023-07-24 01:26:16 +02:00
.drone.yml build branch main automatically 2023-07-25 21:49:45 +02:00
.gitignore Update for Hugo 0.111.1 2023-03-04 23:43:37 +01:00
config.yaml Remove "Updates" menu item 2023-01-21 17:00:37 +01:00
docker-compose.yml Fix new website 2022-12-08 09:43:48 +01:00
Dockerfile Restore Dockerfile 2020-05-29 23:08:04 +02:00
Dockerfile_hugo Update for Hugo 0.111.1 2023-03-04 23:43:37 +01:00
README.md Run stuff with docker-compose 2021-05-04 20:57:45 +02:00

data.coop-website

Build Status

This is a Hugo project.

Running with Docker

In docker-compose.yml, we have specified a serve target which you can run locally like this:

docker-compose up serve

Running without Docker

Go to Hugo Github release and fetch the latest package for hugo_extended for your system.

We want to align with the latest version always. If it doesn't work, file an issue!

Example recipe

# Fetch .deb from Github
wget https://github.com/gohugoio/hugo/releases/download/v0.80.0/hugo_extended_X.Y.Z_Linux-64bit.deb -O hugo_extended.deb

# Install package
sudo dpkg -i hugo_extended.deb

# Clone repo
git clone https://git.data.coop/data.coop/website.git data.coop-website

# Go to website
cd data.coop-website

# Run development server
hugo server

Deploying the site

Simply pushing to master in our main repo at https://git.data.coop/data.coop/website/ will trigger a build-and-deploy of the website.

Multilingual notes

Our website is made multi-lingual using the following 3 structures:

  1. The folder i18n/ contains translations of strings used in the theme.
  2. Each content article and news text has a language version such content/<slug>.en.md
  3. The config.yaml contains settings specific to each language, such as navigation.