Skip to content

Commit 07f6e10

Browse files
ferbsxclaude
ferbsx
and
claude
committed
Host on GitHub Pages (project site) instead of lost custom domain
The codecurious.org domain was lost, so move hosting to free GitHub Pages at https://codecurious-bln.github.io/CC-website/. - Remove CNAME for the lost codecurious.org domain - Add GitHub Actions workflow to build (Jekyll 4) and deploy to Pages. GitHub Pages' native build only supports Jekyll 3.x, and the Gemfile pins Jekyll ~> 4.0, so we build with Bundler and deploy the artifact. - _config.yml: point url at codecurious-bln.github.io; keep baseurl empty for local dev. The workflow injects the project base path (/CC-website) at build time via --baseurl. - Convert all root-relative internal links (/assets, /en, /de) to the relative_url filter so they resolve under the project subpath. This also keeps the site portable if it later moves to a root domain. - Fix two German workshop posts whose i18n_key collided with other events (broke the cross-language "view in other language" links). - README: document the GitHub Pages hosting + the required Pages source. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
1 parent 858fbe5 commit 07f6e10

26 files changed

Lines changed: 102 additions & 34 deletions

‎.github/workflows/jekyll.yml‎

Lines changed: 63 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,63 @@
1+
name: Deploy Jekyll site to GitHub Pages
2+
3+
on:
4+
# Build & deploy on every push to the default branch
5+
push:
6+
branches: ["master"]
7+
# Allow manual runs from the Actions tab
8+
workflow_dispatch:
9+
10+
# Permissions required for deploying to GitHub Pages
11+
permissions:
12+
contents: read
13+
pages: write
14+
id-token: write
15+
16+
# Allow one concurrent deployment; don't cancel an in-progress production deploy
17+
concurrency:
18+
group: "pages"
19+
cancel-in-progress: false
20+
21+
jobs:
22+
build:
23+
runs-on: ubuntu-latest
24+
steps:
25+
- name: Checkout
26+
uses: actions/checkout@v4
27+
28+
- name: Setup Ruby
29+
uses: ruby/setup-ruby@v1
30+
with:
31+
# 2.7 matches the pinned Jekyll 4.0.0 / sassc / nokogiri stack in Gemfile.lock
32+
ruby-version: '2.7'
33+
bundler-cache: true # runs `bundle install` and caches gems
34+
35+
- name: Setup Pages
36+
id: pages
37+
uses: actions/configure-pages@v5
38+
with:
39+
# Enable Pages with "GitHub Actions" as the source automatically on the
40+
# first run, so no manual Settings → Pages change is needed. If org
41+
# policy blocks this, enable it manually (see README) and re-run.
42+
enablement: true
43+
44+
- name: Build with Jekyll
45+
# `base_path` is auto-detected from the repo (e.g. /CC-website) so every
46+
# `relative_url` link resolves correctly under the project-page subpath.
47+
run: bundle exec jekyll build --baseurl "${{ steps.pages.outputs.base_path }}"
48+
env:
49+
JEKYLL_ENV: production
50+
51+
- name: Upload artifact
52+
uses: actions/upload-pages-artifact@v3
53+
54+
deploy:
55+
environment:
56+
name: github-pages
57+
url: ${{ steps.deployment.outputs.page_url }}
58+
runs-on: ubuntu-latest
59+
needs: build
60+
steps:
61+
- name: Deploy to GitHub Pages
62+
id: deployment
63+
uses: actions/deploy-pages@v4

‎CNAME‎

Lines changed: 0 additions & 1 deletion
This file was deleted.

‎README.md‎

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -2,6 +2,8 @@
22

33
This is a community project to build the [code curious website](https://codecurious-bln.github.io/CC-website/). It is using [Jekyll](https://jekyllrb.com).
44

5+
The site is hosted on **GitHub Pages** at <https://codecurious-bln.github.io/CC-website/>. Every push to `master` is built and deployed automatically by the [GitHub Actions workflow](.github/workflows/jekyll.yml) (the repo's *Settings → Pages → Build and deployment → Source* must be set to **GitHub Actions**).
6+
57
## Installation
68

79
Go to your terminal and run:

‎_config.yml‎

Lines changed: 6 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -21,8 +21,12 @@
2121
title: code curious
2222
email: contact@codecurious.org
2323
description: ""
24-
baseurl: "" # the subpath of your site, e.g. /blog
25-
url: "https://codecurious-bln.github.io/CC-website/" # the base hostname & protocol for your site, e.g. http://example.com
24+
# baseurl is the subpath the site is served from. It is left empty so local
25+
# development (`bundle exec jekyll serve`) works at http://localhost:4000/.
26+
# For production on GitHub Pages the build workflow injects the correct value
27+
# (`/CC-website`) via `--baseurl`, so all links must use the `relative_url` filter.
28+
baseurl: ""
29+
url: "https://codecurious-bln.github.io" # the base hostname & protocol for your site
2630
twitter_username: codecurious_bln
2731
github_username: codecurious-bln
2832
instagram_username: code.curious

‎_includes/footer.html‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ <h2 class="footer-heading">{{ site.title | escape }}</h2>
1313
</li>
1414
{%- endif -%}
1515
<li>
16-
<a href="/de/impressum">Impressum</a>
16+
<a href="{{ '/de/impressum' | relative_url }}">Impressum</a>
1717
</li>
1818
</ul>
1919
</div>

‎_includes/translated_links.html‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@
1414
{% assign post_language= post.dir | replace: '/' | slice: 0,2 | default: "en" %}
1515
{% endif %}
1616
{% if page_language != post_language %}
17-
<a title="{{ site.data.translation['viewIn'][post_language]}} {{ site.data.translations.languages[post_language].label }}" class="{{post_language}} page-link" href="{{ post.url }}">🌎 {{ site.data.translation['viewIn'][post_language]}}</a>
17+
<a title="{{ site.data.translation['viewIn'][post_language]}} {{ site.data.translations.languages[post_language].label }}" class="{{post_language}} page-link" href="{{ post.url | relative_url }}">🌎 {{ site.data.translation['viewIn'][post_language]}}</a>
1818
{% endif %}
1919
{% endfor %}
2020
{% endif %}

‎de/_posts/2012-05-18-interview-mit-lena-herrmann.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -6,9 +6,9 @@ i18n_key: lena-interview
66
categories: de blog
77
---
88

9-
![photo of Lena Herrmann, white woman with short blonde hair.](/assets/images/Lena_Herrmann.jpeg)
9+
![photo of Lena Herrmann, white woman with short blonde hair.]({{ '/assets/images/Lena_Herrmann.jpeg' | relative_url }})
1010

11-
(Achtung: Dieser Artikel wurde aus dem Englischen übersetzt. Den Originalartikel findet ihr [hier](/en/blog/2012/05/18/interview-with-lena-herrmann/ "Interview with Lena Hermann"))
11+
(Achtung: Dieser Artikel wurde aus dem Englischen übersetzt. Den Originalartikel findet ihr [hier]({{ '/en/blog/2012/05/18/interview-with-lena-herrmann/' | relative_url }} "Interview with Lena Hermann"))
1212

1313
Lena Hermann ist Frau, Mutter, Feministin, politische Aktivistin und eine Agile Developerin. Sie ist außerdem Coach bei den Rails Girls Berlin, und in ihrer Freizeit hilft sie außerdem den Teilnehmern der vorhergehenden Workshops, eine eigene Blogging-Plattform zu bauen. Ich bin mir nicht sicher, wo sie ihre Stärke hernimmt. Es muss wohl der Samba sein.
1414

‎de/_posts/2017-10-25-rails-girls-berlin-wird-erwachsener.markdown‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ i18n_key: RGBgrowingup
55
categories: de blog
66
---
77

8-
![](/assets/images/IMG_0876b.jpg)
8+
![]({{ '/assets/images/IMG_0876b.jpg' | relative_url }})
99

1010
Seit dem ersten Workshop im Jahr 2012 gibt es in Berlin die Initiative Rails Girls. Wir haben über dreißig Workshops veranstaltet mit über 1200 Teilnehmenden. Aus unserer Community sind so tolle Projekte entstanden wie [speakerinnen.org](http://speakerinnen.org), [rorganize.it](http://rorganize.it) und [diversitytickets.org](http://diversitytickets.org). Aber auch der [Rails Girls Summer of Code](https://railsgirlssummerofcode.org/), [ClojureBridge Berlin](http://clojurebridge-berlin.org/) und die [Heart of Code](http://heartofcode.org/) sind unter anderem von Menschen aufgebaut, die mit uns (wieder) Spaß am Programmieren fanden.
1111

‎de/_posts/2019-11-30-js-testing-workshop.markdown‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ i18n_key: js_testing_workshop_2019_11
55
title: JS Testing Workshop
66
---
77

8-
![Foto von einem Laptop mit JavaScript Code auf dem Bildschirm neben einem Stück Kuchen](/assets/images/JStesting-Nov19.jpg)
8+
![Foto von einem Laptop mit JavaScript Code auf dem Bildschirm neben einem Stück Kuchen]({{ '/assets/images/JStesting-Nov19.jpg' | relative_url }})
99

1010
## Lerne noch mehr Programmieren ♥️
1111

‎de/_posts/2019-12-07-rails-beginner-workshop.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ slug: Anfaenger_innen-Workshop
55
i18n_key: rails_beginner_workshop_2019_12
66
---
77

8-
![Foto von dutzenden Frauen mit Laptops, die zusammen um einen großen weißen Tisch herum programmieren.](/assets/images/Dec19-Banner.jpeg)
8+
![Foto von dutzenden Frauen mit Laptops, die zusammen um einen großen weißen Tisch herum programmieren.]({{ '/assets/images/Dec19-Banner.jpeg' | relative_url }})
99

1010
### Lerne Programmieren ♥️
1111
Unser Rails-Beginner-Workshop steht im Zeichen von Ruby on Rails, mit dessen Hilfe du deine erste kleine Web-Anwendung erstellen wirst. Es wird in kleinen Gruppen gearbeitet, die von jeweils einem Coach geleitet werden. Du kannst und sollst jederzeit Fragen stellen! Abgerundet wird das Programm durch anfängerfreundliche und unterhaltsame Talks zu verschiedenen Themen rund um das Programmieren.

0 commit comments

Comments
 (0)