Website for data.coop
Ir al archivo
benjaoming 1b047ab7e1
continuous-integration/drone/pr Build is passing Detalles
continuous-integration/drone/push Build is passing Detalles
Merge pull request 'Update account numbers' (#115) from benjaoming/website:new-account into staging
Reviewed-on: #115
2024-03-25 22:41:35 +00:00
content Update account numbers 2024-03-25 23:31:10 +01: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 Add OpenGraph and hellsite preview 2023-12-16 22:27:59 +01:00
themes/datacoop2020 Add OpenGraph and hellsite preview 2023-12-16 22:27:59 +01:00
.drone.yml Revert baseURL 2023-12-22 20:19:49 +01:00
.gitignore Update for Hugo 0.111.1 2023-03-04 23:43:37 +01:00
Dockerfile Restore Dockerfile 2020-05-29 23:08:04 +02:00
README.md master -> main in README.md [ci skip] 2023-07-30 00:01:09 +02:00
config.yaml Revert baseURL 2023-12-22 20:19:49 +01:00
docker-compose.yml Use klakegg/hugo for building site 2023-07-30 00:26:25 +02:00

README.md

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 main 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.