CCCB Website
Go to file
2023-06-13 21:45:25 +02:00
.github refacture all the things! 2023-06-13 12:47:07 +02:00
archetypes Move out datengartens into their own section 2018-05-21 18:31:39 +02:00
content It's 2023 2023-01-26 13:26:46 +00:00
layouts reformat html end tags 2023-06-13 21:41:28 +02:00
static/img Delete coderdojo.png 2019-03-17 18:57:43 +01:00
themes update theme 2023-06-13 21:45:25 +02:00
tools reformat html end tags 2023-06-13 21:41:28 +02:00
.editorconfig update gitignore; add editorconfig 2023-06-13 12:53:51 +02:00
.gitattributes ICS Files brauchen CLRF 2018-06-11 22:50:30 +02:00
.gitignore update gitignore; add editorconfig 2023-06-13 12:53:51 +02:00
.gitmodules change submodule to fork, add step to README, fix typo in README 2018-05-18 21:27:55 +02:00
.hugo-params Add baseURL for staging 2019-03-14 20:52:34 +01:00
.python-version Create .python-version 2023-06-12 19:29:12 +02:00
build.sh refacture all the things! 2023-06-13 12:47:07 +02:00
config.yaml refacture all the things! 2023-06-13 12:47:07 +02:00
LICENSE Add LICENSE 2018-08-14 23:11:06 +02:00
README.md refacture all the things! 2023-06-13 12:47:07 +02:00
requirements.txt Update requirements.txt 2023-06-12 20:09:47 +02:00
TODO.md update gitignore; add editorconfig 2023-06-13 12:53:51 +02:00

CCCB logo

CCCB Website

This is the website of the CCCB.

Getting started

  1. Get Hugo: https://gohugo.io/getting-started/installing
  2. Clone this repo
    git clone https://github.com/cccb/www
    
  3. Switch directory
    cd www
    
  4. Fetch Submodules
    git submodule update --recursive --remote --init
    

Run site locally

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

  1. Use your local dev setup (see Getting started) or via GitHub editor.
  2. Make your change in staging branch.
  3. Commit (and push) your change.
  4. GitHub Actions is running the release workflow.
  5. Create merge request to merge changes from staging to production branch. Ask somebody to check merge request or if small change, merge yourself.
  6. GitHub Actions is running the release workflow.
    • If successfull, check Website if change is correct.
  7. Profit!

Made with ❤️ and Hugo.