diff --git a/.github/FUNDING.yml b/.github/FUNDING.yml
deleted file mode 100644
index fb01171..0000000
--- a/.github/FUNDING.yml
+++ /dev/null
@@ -1,4 +0,0 @@
-# These are supported funding model platforms
-
-github: daattali
-patreon: DeanAttali
diff --git a/.github/workflows/ci.yml b/.github/workflows/ci.yml
index 511db28..25e744b 100644
--- a/.github/workflows/ci.yml
+++ b/.github/workflows/ci.yml
@@ -5,11 +5,22 @@ jobs:
name: Build Jekyll
runs-on: ubuntu-latest
steps:
- - uses: actions/checkout@v3
- - name: Build the site in the jekyll/builder container
+ - uses: actions/checkout@v4
+ - uses: ruby/setup-ruby@v1
+ with:
+ ruby-version: '3.3'
+ - name: Install dependencies
+ run: bundle install && bundle exec appraisal install
+ - name: Setup Pages
+ id: configure-pages
+ uses: actions/configure-pages@v5
+ - name: Setup CI config
run: |
- export JEKYLL_VERSION=3.8
- docker run \
- -v ${{ github.workspace }}:/srv/jekyll -v ${{ github.workspace }}/_site:/srv/jekyll/_site \
- -e PAGES_REPO_NWO=${{ github.repository }} \
- jekyll/builder:$JEKYLL_VERSION /bin/bash -c "chmod 777 /srv/jekyll && jekyll build --future"
+ echo "---" > _config_ci.yml
+ echo "baseurl: ${{ steps.configure-pages.outputs.base_path }}" >> _config_ci.yml
+ - name: Build site
+ env:
+ JEKYLL_ENV: production
+ run: bundle exec appraisal jekyll build --future --config _config_ci.yml,_config.yml
+ - name: Upload artifact
+ uses: actions/upload-pages-artifact@v3
\ No newline at end of file
diff --git a/Appraisals b/Appraisals
new file mode 100644
index 0000000..7b4a0ed
--- /dev/null
+++ b/Appraisals
@@ -0,0 +1,6 @@
+appraise "jekyll-3" do
+ gem "jekyll", "3.9.4"
+end
+appraise "jekyll-4" do
+ gem "jekyll", "4.3.3"
+end
\ No newline at end of file
diff --git a/README.md b/README.md
index 825a342..5c53fa0 100644
--- a/README.md
+++ b/README.md
@@ -1,236 +1,11 @@
-# Beautiful Jekyll
+Dieses repo enthält die Website des CoderDojos potsdam. [coderdojopotsdam.github.io](https://coderdojopotsdam.github.io/)
-[](https://badge.fury.io/rb/beautiful-jekyll-theme)
+Die Seite ist mit beautifull jekyll gebaut.
-> By [Dean Attali](https://deanattali.com) · [Demo](https://beautifuljekyll.com/)
+## Seiten ändern/anlegen
-**Beautiful Jekyll** is a ready-to-use template to help you create a beautiful website quickly. Perfect for personal sites, blogs, or simple project websites. [Check out a demo](https://beautifuljekyll.com) of what you'll get after just two minutes. You can also look at [my personal website](https://deanattali.com) or [my consulting website](https://attalitech.com) to see it in use, or see [examples of websites](http://beautifuljekyll.com/examples) other people created using this theme.
+Die homepage und alle unterseiten sind als markdown Dateien im root folder zu finden. Es dauert einen Moment bis Änderungen auf der Seite sichtbar werden.
-**If you enjoy Beautiful Jekyll, please consider [supporting me](https://github.com/sponsors/daattali). You'll also gain access to office hours and more features! ❤**
-
-## Table of contents
-
-- [Features](#features)
-- [Sponsors 🏆](#sponsors)
-- [**Build your website in 3 steps**](#build-your-website-in-3-steps)
-- [Plans](#plans)
-- [Add your own content](#add-your-own-content)
-- [Customizing parameters for each page](#customizing-parameters-for-each-page)
-- [Supported parameters](#supported-parameters)
-- [Featured users (success stories!)](#featured-users-success-stories)
-- [Next steps](#next-steps)
-- [Getting help](#getting-help)
-- [Credits and contributions](#contributions)
-
-# Features
-
-__Check out [*What's New?*](https://beautifuljekyll.com/updates/) to see the latest features!__
-
-- **SIMPLE**: The primary goal of Beautiful Jekyll is to allow literally *anyone* to create a website in a few minutes.
-- **Modern**: Uses the latest best practices and technologies to achieve nearly perfect scores on Google Chrome's Audit.
-- **Mobile-first**: Designed to look great on both large-screen and small-screen (mobile) devices.
-- **Highly customizable**: Many personalization settings such as changing the background colour/image, adding a logo.
-- **Flexible usage**: Use Beautiful Jekyll directly on GitHub or via a Ruby gem - choose the best [development method](#build-your-website-in-3-steps) for you.
-- **Battle-tested**: By using Beautiful Jekyll, you'll be joining 50,000+ users enjoying this theme since 2015.
-- **SEO and social media support**: Customize how your site looks on Google and when shared on social media.
-- **Comments support**: Add comments to any page using either [Disqus](https://disqus.com/), [Facebook comments](https://developers.facebook.com/docs/plugins/comments), [Utterances](https://utteranc.es/), [Staticman](https://staticman.net), [giscus](https://giscus.app), or [CommentBox](https://commentbox.io/).
-- **Tags**: Any blog post can be tagged with keywords, and an index page is automatically generated.
-- **Analytics**: Easily integrate Google Analytics, or other analytics platforms, to track visits to your website.
-- **Search**: Let users easily find any page using a Search button in the navigation bar.
-- **Photos support**: Any page can have a full-width cover photo and thumbnail.
-- **RSS**: An RSS feed is automatically created, so you can even host a podcast easily with Beautiful Jekyll.
-
-
-
-Developing and maintaining Beautiful Jekyll takes a lot of time and effort - thank you to anyone who helps fund this effort!
-
-- [DoFollow](https://dofollow.co.uk/)
-- [\_hyp3ri0n](https://hyperiongray.com)
-- [Varna Sri Raman](https://about.me/varna)
-
-**[Become a sponsor for Beautiful Jekyll and unlock new features\!](https://github.com/sponsors/daattali/sponsorships?tier_id=39856)**
-
-# Build your website in 3 steps
-
-There are a few different ways to build a website using Beautiful Jekyll, and this document will go through the simplest one: using a fork on GitHub. For most people (including myself!), this easy method is the recommended one.
-
-Even if you choose to use one of the [advanced installation methods](https://beautifuljekyll.com/getstarted/#install-steps-hard), I still suggest you read through the easy method first.
-
-## The easy way (recommended!)
-
-Getting started is *literally* as easy as 1-2-3 :smile:
-
-Scroll down to see the steps involved, but here is a 30-second video just as a reference as you work through the steps. If you don't already have a [GitHub account](https://github.com), you'll need to sign up.
-
-
-
-### 1. Fork this project
-
-Click on the __*Fork*__ button at the top right corner of this page. Forking means that you're copying this entire project and all its files into your account. Do not click on the __*Create fork*__ button on the next page yet.
-
-### 2. Rename the repository to `YOURUSERNAME.github.io`
-
-You'll see the word "repository" used a lot in GitHub - it simply means "project". Under __*Repository name*__ you should see the name `beautiful-jekyll`, this is where you need to rename your project to `YOURUSERNAME.github.io` (replace `YOURUSERNAME` with your GitHub user name). It's important to use this exact name so that GitHub will recognize it and automatically create a website for this project.
-
-> Tip: If you want to use a different URL for your website, check out the [FAQ](https://beautifuljekyll.com/faq/#custom-domain)
-
-### 3. Customize your website settings
-
-Edit the `_config.yml` file to change any settings you want. To edit the file, first click on it to view the file, and on the next page click on the pencil icon to edit it (watch the video tutorial above if you're confused). The settings in the file are self-explanatory and there are comments inside the file to help you understand what each setting does. Any line that begins with a hashtag (`#`) is a comment, and the other lines are actual settings. After changing the settings, click the green __*Commit changes*__ button to save these edits.
-
-> Note: In the video above, only one setting in the `_config.yml` file is edited, but you should go through the rest of the settings as well.
-
-### 4. Congratulations! You have a website!
-
-If you named your project correctly and made an edit to the config file, your website should be ready in a minute or two at `https://YOURUSERNAME.github.io`. Every time you make a change to any file, your website will get rebuilt and should be updated in about a minute or so. Your website will be initialized with several sample blog posts and a couple other pages.
-
-## The harder way (for advanced users)
-
-The instructions above explain how to use Beautiful Jekyll in the easiest way: by forking on GitHub. There are more [advanced installation methods](https://beautifuljekyll.com/getstarted/#install-steps-hard) that include either using GitHub Pages with remote themes, or using Ruby gems. They provide you with more control, but are only intended for advanced users.
-
-> Note: Beautiful Jekyll was primarily designed to be used as a GitHub theme, so you will not get any support if you use this theme via Ruby gems.
-
-# Plans
-
-Beautiful Jekyll is, and always will be, free. But if you want to remove the Beautiful Jekyll ad from your website, use a Dark Mode skin, access office hours, or simply support the development efforts, [check out the different plans](https://beautifuljekyll.com/plans).
-
-# Add your own content
-
-To add pages to your site, you can either write a markdown file (`.md`) or you can write an HTML file. It's much easier to write markdown than HTML, so that's the recommended approach ([here's a great tutorial](https://markdowntutorial.com/) if you need to learn markdown in 5 minutes).
-
-To see an example of a markdown file, click on any file that ends in `.md`, for example [`aboutme.md`](./aboutme.md). On that page you can see some nicely formatted text (there's a word in bold, a link, a few bullet points), and if you click on the pencil icon to edit the file, you'll see the markdown code that generated the pretty text. Very easy!
-
-In contrast, look at [`tags.html`](./tags.html). That's how your write HTML - not as pretty. So stick with markdown if you don't know HTML.
-
-Any markdown or HTML file that you create will be available on your website under `https://.github.io/`. For example, if you create a file `about.md` (or `about.html`) then it'll exist at `https://.github.io/about`.
-
-Files you create inside the [`_posts`](./_posts) directory will be treated as blog entries. You can look at the existing files there to get an idea of how to write blog posts. Note the format of the blog post files - they must follow the naming convention of `YEAR-MONTH-DAY-title.md`. After you successfully add your own post, you can delete the existing files inside [`_posts`](./_posts) to remove the sample posts, as those are just demo posts to help you learn.
-
-# Customizing parameters for each page
-
-**One last important thing**: In order to have your new pages use this template and not just be plain HTML pages, **you must add [YAML front matter](https://jekyllrb.com/docs/front-matter/) to the top of each page**:
-
-
-```
----
----
-```
-
-This is where you'll be able to give each page some extra parameters (such as a title, a subtitle, an image, etc - [below is a list of all parameters](#supported-parameters)). Add any parameters you want between these two dashed lines, for example:
-
-```
----
-title: Contact me
-subtitle: Here you'll find all the ways to get in touch with me
----
-```
-
-If you don't want to use any parameters on a page, you still need to use the two dashed lines. If you don't, then your file will be shown as-is without the Beautiful Jekyll template.
-
-You can look at the top of [`aboutme.md`](https://raw.githubusercontent.com/daattali/beautiful-jekyll/master/aboutme.md) as an example.
-
-**Important takeaway: ALWAYS add the YAML front matter, which is two lines of three dashes, to EVERY page. If you have any parameters, they go between the two lines.**
-
-# Supported parameters
-
-Below is a list of the parameters that Beautiful Jekyll supports (any of these can be added to the YAML front matter of any page). Remember to also look in the `_config.yml` file to see additional site-wide settings.
-
-## Main parameters
-
-These are the basic YAML parameters that you are most likely to use on most pages.
-
-Parameter | Description
------------ | -----------
-title | Page or blog post title
-subtitle | Short description of page or blog post that goes under the title
-tags | List of tags to categorize the post. Separate the tags with commas and place them inside square brackets. Example: `[personal, analysis, finance]`
-cover-img | Include a large full-width image at the top of the page. You can either provide the path to a single image (eg. `"/path/to/img"`) , or a list of images to cycle through (eg. `["/path/img1", "/path/img2"]`). If you want to add a caption to an image, then you must use the list notation (use `[]` even if you have only one image), and each image should be provided as `"/path/to/img" : "Caption of image"`.
-thumbnail-img | For blog posts, if you want to add a thumbnail that will show up in the feed, use `thumbnail-img: /path/to/image`. If no thumbnail is provided, then `cover-img` will be used as the thumbnail. You can use `thumbnail-img: ""` to disable a thumbnail.
-comments | If you want do add comments to a specific page, use `comments: true`. Comments only work if you enable one of the comments providers (Facebook, disqus, staticman, utterances, giscus, CommentBox) in `_config.yml` file. Comments are automatically enabled on blog posts but not on other pages; to turn comments off for a specific post, use `comments: false`.
-
-## Parameters for SEO and social media sharing
-
-These parameters let you control what information shows up when a page is shown in a search engine (such as Google) or gets shared on social media (such as Twitter/Facebook).
-
-Parameter | Description
------------ | -----------
-share-title | A title for the page. If not provided, then `title` will be used, and if that's missing then the site title (from `_config.yml`) is used.
-share-description | A brief description of the page. If not provided, then `subtitle` will be used, and if that's missing then an excerpt from the page content is used.
-share-img | The image to show. If not provided, then `cover-img` or `thumbnail-img` will be used if one of them is provided.
-
-## Less commonly used parameters
-
-These are parameters that you may not use often, but can come in handy sometimes.
-
-Parameter | Description
------------ | -----------
-readtime | If you want a post to show how many minutes it will take to read it, use `readtime: true`.
-show-avatar | If you have an avatar configured in the `_config.yml` but you want to turn it off on a specific page, use `show-avatar: false`.
-social-share | By default, every blog post has buttons to share the page on social media. If you want to turn this feature off, use `social-share: false`.
-nav-short | By default, the navigation bar gets shorter after scrolling down the page. If you want the navigation bar to always be short on a certain page, use `nav-short: true`
-gh-repo | If you want to show GitHub buttons at the top of a post, this sets the GitHub repo name (eg. `daattali/beautiful-jekyll`). You must also use the `gh-badge` parameter to specify what buttons to show.
-gh-badge | Select which GitHub buttons to display. Available options are: [star, watch, fork, follow]. You must also use the `gh-repo` parameter to specify the GitHub repo.
-last-updated | If you want to show that a blog post was updated after it was originally released, you can specify an "Updated on" date.
-layout | What type of page this is (default is `post` for blog posts and `page` for other pages). See _Page types_ section below for more information.
-
-## Advanced parameters
-
-These are advanced parameters that are only useful for people who need very fine control over their website.
-
-Parameter | Description
------------ | -----------
-footer-extra | If you want to include extra content below the social media icons in the footer, create an HTML file in the `_includes/` folder (for example `_includes/myinfo.html`) and set `footer-extra` to the name of the file (for example `footer-extra: myinfo.html`). Accepts a single file or a list of files.
-before-content | Similar to `footer-extra`, but used for including HTML before the main content of the page (below the title).
-after-content | Similar to `footer-extra`, but used for including HTML after the main content of the page (above the footer).
-head-extra | Similar to `footer-extra`, but used if you have any HTML code that needs to be included in the `` tag of the page.
-language | HTML language code to be set on the page's <html> element.
-full-width | By default, page content is constrained to a standard width. Use `full-width: true` to allow the content to span the entire width of the window.
-js | List of local JavaScript files to include in the page (eg. `/assets/js/mypage.js`)
-ext-js | List of external JavaScript files to include in the page (eg. `//cdnjs.cloudflare.com/ajax/libs/underscore.js/1.8.2/underscore-min.js`). External JavaScript files that support [Subresource Integrity (SRI)](https://developer.mozilla.org/en-US/docs/Web/Security/Subresource_Integrity) can be specified using the `href` and `sri` parameters eg.
`href: "//code.jquery.com/jquery-3.1.1.min.js"`
`sri: "sha256-hVVnYaiADRTO2PzUGmuLJr8BLUSjGIZsDYGmIJLv2b8="`
-css | List of local CSS files to include in the page
-ext-css | List of external CSS files to include in the page. External CSS files using SRI (see `ext-js` parameter) are also supported.
-
-## Page types
-
-- **post** - To write a blog post, add a markdown or HTML file in the `_posts` folder. As long as you give it YAML front matter (the two lines of three dashes), it will automatically be rendered like a blog post. Look at the existing blog post files to see examples of how to use YAML parameters in blog posts.
-- **page** - Any page outside the `_posts` folder that uses YAML front matter will have a very similar style to blog posts.
-- **home** - The home layout is meant to act as the homepage of your blog posts - it will display all your blog posts, sorted from newest to oldest. A file using the `home` layout must be named `index.html` (not `index.md` or anything else!).
-- **minimal** - If you want to create a page with minimal styling (ie. without the bulky navigation bar and footer), assign `layout: minimal` to the YAML front matter.
-- If you want to completely bypass the template engine and just write your own HTML page, simply omit the YAML front matter. Only do this if you know how to write HTML!
-
-# Featured users (success stories!)
-
-Visit the [Official website](http://beautifuljekyll.com/examples) to see sample websites using Beautiful Jekyll.
-
-If you'd like to showcase yourself and join this list, [upgrading to the Individual plan](https://github.com/sponsors/daattali/sponsorships?&tier_id=7362) will give you that publicity plus some other rewards!
-
-# Next steps
-
-Congratulations on making it this far! You now have all the tools to easily build a beautiful website for free.
-
-- After you get comfortable with the basics of writing in markdown, I suggest taking a look at this [sample post](https://beautifuljekyll.com/2020-02-28-sample-markdown/) and [the code that created it](https://raw.githubusercontent.com/daattali/beautiful-jekyll/master/_posts/2020-02-28-sample-markdown.md) to learn some more advanced tips about markdown.
-
-- I highly recommend going over the [*Frequently Asked Questions*](https://beautifuljekyll.com/faq/) to find out answers to questions you may not even know you have. Every few months I suggest checking the [*What's New?*](https://beautifuljekyll.com/updates/) page to see if there are new features, and learn [how to update your site to the newest version](https://beautifuljekyll.com/faq/#updating) when it's time.
-
-- You can also check out the [advanced installation methods](https://beautifuljekyll.com/getstarted/#install-steps-hard) that give you a little more control but are harder to use. Keep in mind that Beautiful Jekyll was primarily designed to be used as a GitHub theme, so you will not get any support if you choose one of the Ruby installation methods.
-
-# Getting help
-
-Visit the [FAQ page](https://beautifuljekyll.com/faq) for answers to commonly asked questions.
-
-**If you choose to [become a sponsor](https://beautifuljekyll.com/plans/), you'll have access to my [office hours](https://beautifuljekyll.com/officehours/) where you can ask for help.** You can also use the [Discussions](https://github.com/daattali/beautiful-jekyll/discussions) area to try and get help from the community.
-
-Beautiful Jekyll is used by 50,000+ people with wildly varying degrees of web skills, so it's impossible to answer all the questions that may arise. For any question that's not specifically related to Beautiful Jekyll and is more about Jekyll or web development in general, the answer can often be found on Google, in the [Jekyll documentation](https://jekyllrb.com/), or on the [Jekyll support forum](https://talk.jekyllrb.com/).
-
-# Contributions
-
-Thank you to [all past contributors](https://github.com/daattali/beautiful-jekyll/graphs/contributors). If you find any problems or would like to contribute in any way, feel free to create a pull request/open an issue/send me a message.
-
-You can also contribute by becoming an [official sponsor](https://github.com/sponsors/daattali/sponsorships?tier_id=39856) to help keep Beautiful Jekyll well-maintained!
-
-# Credits
-
-This template was not made *entirely* from scratch. I'd like to give special thanks to [Jekyll Now](https://github.com/barryclark/jekyll-now) and [Bootstrap Clean Blog](https://github.com/IronSummitMedia/startbootstrap-clean-blog), from whom I've taken several ideas initially.
-
-I'd also like to thank [Dr. Jekyll's Themes](https://drjekyllthemes.github.io/), [Jekyll Themes](http://jekyllthemes.org/), and another [Jekyll Themes](http://jekyllrc.github.io/jekyllthemes/) for featuring Beautiful Jekyll in their Jekyll theme directories.
+## eine Seite zur Nav hinzufügen
+In der _config.yml Datei im root folder sind unter navbar-links: alle Links der Navbar mit den jeweiligen Unterseiten zu finden.
diff --git a/anmeldung.md b/anmeldung.md
index 470b839..6cf10ec 100644
--- a/anmeldung.md
+++ b/anmeldung.md
@@ -7,5 +7,6 @@ permalink: /anmeldung/
diff --git a/assets/Teilnahmebedingungen-CoderDojo-Potsdam.pdf b/assets/Teilnahmebedingungen-CoderDojo-Potsdam.pdf
new file mode 100644
index 0000000..2eba306
Binary files /dev/null and b/assets/Teilnahmebedingungen-CoderDojo-Potsdam.pdf differ
diff --git a/assets/img/2022-weihnachtsmelodie.jpg b/assets/img/2022-weihnachtsmelodie.jpg
new file mode 100644
index 0000000..d254b4f
Binary files /dev/null and b/assets/img/2022-weihnachtsmelodie.jpg differ
diff --git a/assets/img/2022-weihnachtsmelodie2.jpg b/assets/img/2022-weihnachtsmelodie2.jpg
new file mode 100644
index 0000000..cf2a755
Binary files /dev/null and b/assets/img/2022-weihnachtsmelodie2.jpg differ
diff --git a/assets/img/2024-01-13-Winterprojekt.jpeg b/assets/img/2024-01-13-Winterprojekt.jpeg
new file mode 100644
index 0000000..4d8ea4b
Binary files /dev/null and b/assets/img/2024-01-13-Winterprojekt.jpeg differ
diff --git a/assets/img/2024-01-13-Winterprojekt2.jpeg b/assets/img/2024-01-13-Winterprojekt2.jpeg
new file mode 100644
index 0000000..bdeeef9
Binary files /dev/null and b/assets/img/2024-01-13-Winterprojekt2.jpeg differ
diff --git a/assets/img/2024-12-15-weihnachtsbox.jpg b/assets/img/2024-12-15-weihnachtsbox.jpg
new file mode 100644
index 0000000..c706c09
Binary files /dev/null and b/assets/img/2024-12-15-weihnachtsbox.jpg differ
diff --git a/assets/img/2024-12-15-weihnachtsboxen.jpg b/assets/img/2024-12-15-weihnachtsboxen.jpg
new file mode 100644
index 0000000..fa95b18
Binary files /dev/null and b/assets/img/2024-12-15-weihnachtsboxen.jpg differ
diff --git a/assets/img/crepe.jpg b/assets/img/crepe.jpg
deleted file mode 100644
index 301fa18..0000000
Binary files a/assets/img/crepe.jpg and /dev/null differ
diff --git a/assets/img/rotes_Weihnachtslicht.jpg b/assets/img/rotes_Weihnachtslicht.jpg
new file mode 100644
index 0000000..f2ab706
Binary files /dev/null and b/assets/img/rotes_Weihnachtslicht.jpg differ
diff --git a/assets/img/weihnachten_2023.jpg b/assets/img/weihnachten_2023.jpg
new file mode 100644
index 0000000..b0bcc6b
Binary files /dev/null and b/assets/img/weihnachten_2023.jpg differ
diff --git a/assets/img/weihnachtsdeko.jpeg b/assets/img/weihnachtsdeko.jpeg
new file mode 100644
index 0000000..0540628
Binary files /dev/null and b/assets/img/weihnachtsdeko.jpeg differ
diff --git a/beautiful-jekyll-theme.gemspec b/beautiful-jekyll-theme.gemspec
index 93f54d9..acbd2a0 100644
--- a/beautiful-jekyll-theme.gemspec
+++ b/beautiful-jekyll-theme.gemspec
@@ -17,13 +17,14 @@ Gem::Specification.new do |spec|
"documentation_uri" => "https://github.com/daattali/beautiful-jekyll#readme"
}
- spec.add_runtime_dependency "jekyll", "~> 3.9.3"
+ spec.add_runtime_dependency "jekyll", ">= 3.9.3"
spec.add_runtime_dependency "jekyll-paginate", "~> 1.1"
spec.add_runtime_dependency "jekyll-sitemap", "~> 1.4"
spec.add_runtime_dependency "kramdown-parser-gfm", "~> 1.1"
- spec.add_runtime_dependency "kramdown", "~> 2.3.2"
+ spec.add_runtime_dependency "kramdown", "~> 2.3"
spec.add_runtime_dependency "webrick", "~> 1.8"
spec.add_development_dependency "bundler", ">= 1.16"
spec.add_development_dependency "rake", "~> 12.0"
-end
+ spec.add_development_dependency "appraisal", "~> 2.5"
+end
\ No newline at end of file
diff --git a/eindruecke.md b/eindruecke.md
index 23f3eda..31501de 100644
--- a/eindruecke.md
+++ b/eindruecke.md
@@ -1,9 +1,42 @@
---
layout: page
title: Eindrücke
-subtitle: wirf einen Blick in unsere Treffen
+subtitle: Wirf einen Blick in unsere Treffen
---
+### Weihnachtsevent 2024
+
+
+
+
+Anleitung und Ressourcen findet ihr hier: [https://github.com/CoderDojoPotsdam/AdventBox](https://github.com/CoderDojoPotsdam/AdventBox)
+
+
+### Projekt Winterlichter 2024
+
+Im Januar konnte das Weihnachtsevent 2023 mit geändertem Motiv noch einmal gemacht werden:
+
+
+
+
+
+### Weihnachtsevent 2023
+
+
+
+
+Anleitung und Ressourcen findet ihr hier: [https://github.com/CoderDojoPotsdam/ChristmasLight](https://github.com/CoderDojoPotsdam/ChristmasLight)
+
+### Weihnachtsevent 2022
+
+
+
+
+Anleitung und Ressourcen findet ihr hier: [https://github.com/CoderDojoPotsdam/ChristmasMelody](https://github.com/CoderDojoPotsdam/ChristmasMelody)
+
+
+### Ältere Eindrücke
+



diff --git a/faq.md b/faq.md
index 9d19f9d..aec5707 100644
--- a/faq.md
+++ b/faq.md
@@ -6,7 +6,7 @@ subtitle: Häufig gestellte Fragen
## Was ist das Coder Dojo Potsdam?
-CoderDojo ist ein Club für Kinder und Jugendliche im Alter von 5 bis 17 Jahren, die programmieren lernen und Spaß haben wollen. Freiwillige Mentor_innen helfen den Kindern, ihre Ideen umzusetzen. Dabei lernen sie spielerisch die Grundlagen des Programmierens. Und auch wenn sie die Grundlagen schon kennen, gibt es noch mehr als genug neue Konzepte zu lernen oder Technologien.
+CoderDojo ist ein Club für Kinder und Jugendliche im Alter von 5 bis 17 Jahren, die programmieren lernen und Spaß haben wollen. Freiwillige MentorInnen helfen den Kindern, ihre Ideen umzusetzen. Dabei lernen sie spielerisch die Grundlagen des Programmierens. Und auch wenn sie die Grundlagen schon kennen, gibt es noch mehr als genug neue Konzepte zu lernen oder Technologien.
Hier gibt es mehr Informationen: [https://coderdojo.com/about](https://coderdojo.com/about)
## Wie läuft es ab?
@@ -17,10 +17,11 @@ Nach einer kurzen Begrüßung beginnen wir mit dem Programmieren. Nach etwa 2,5h
Zeit und Ort der nächsten Dojos geben wir immer auf unserer Hauptseite bekannt.
Die Dojos finden i.d.R. im Hauptgebäude des Hasso-Plattner-Instituts statt.
-Wir versuchen sie alle zwei Wochen stattfinden zu lassen.
+Wir versuchen sie mindestens jeden zweiten Samstag im Monat stattfinden zu lassen.
## Was muss ich mitbringen?
+- die ausgefüllten und unterschriebenen [Teilnahmebedingungen](/assets/Teilnahmebedingungen-CoderDojo-Potsdam.pdf).
- Was zum Essen.
- Laptop(s) oder leihe dir einen im Dojo. Alte Laptops können wir fit machen, sodass sie später im Dojo verwendet werden können.
- Wenn du 12 und jünger bist, einen Begleiter für die gesamte Zeit.
@@ -28,9 +29,9 @@ Wir versuchen sie alle zwei Wochen stattfinden zu lassen.
## Wie alt sind die anderen?
-Die Teilnehmer sind im Alter bis 18 Jahren. Die Mentoren dementsprechend meistens älter. Es ist bestimmt jemand anderes in deinem Alter ± ein Jahr da. Es gibt das [Material von der OpenTechSchool](http://learn.opentechschool.org/), das Erwachsene verwenden, und mit [code.org](http://code.org/) können sich sehr junge Teilnehmer beschäftigen, selbst für Vorschulkinder gibt es ScratchJr und Lightbot. Das waren die beiden Extreme. Auf der [Website](https://CoderDojoPotsdam.github.io) steht das gesamte Material. Es zählt das Interesse, es mal auszuprobieren.
+Die Teilnehmenden sind im Alter bis 18 Jahren. Die Mentoren dementsprechend meistens älter. Es ist bestimmt jemand anderes in deinem Alter ± ein Jahr da. Es gibt das [Material von der OpenTechSchool](http://learn.opentechschool.org/), das Erwachsene verwenden, und mit [code.org](http://code.org/) können sich sehr junge Teilnehmende beschäftigen, selbst für Vorschulkinder gibt es ScratchJr und Lightbot. Das waren die beiden Extreme. Auf der [Website](https://CoderDojoPotsdam.github.io) steht das gesamte Material. Es zählt das Interesse, es mal auszuprobieren.
-# Fragen von Teilnehmern
+# Fragen von Teilnehmenden
## Können auch Tablets verwendet werden?
@@ -38,13 +39,13 @@ Ja. Mitbringen. Für IPads und IPhones gibt es [Hopscotch](http://www.gethopscot
## Kann ich meinen Laptop mitbringen?
-Ja. Programmiert werden kann auf allen Betriebssystemen. Egal, ob es ein Mac, Windows, Linux oder anderes ist. Bestimmt kennt sich ein Mentor auch mit deinem Betriebssystem aus.
+Ja. Programmiert werden kann auf allen Betriebssystemen. Egal, ob es ein Mac, Windows, Linux oder anderes ist. Bestimmt kennt sich ein Mentor oder eine Mentorin auch mit deinem Betriebssystem aus.
Wenn du ihn mitbringst, kannst du auf ihm zu Hause weiter machen. Dadurch entfällt das Aufsetzen und Kopieren des Arbeitsstandes, welche die Hälfte der Arbeit sind.
## Ich habe noch mehr Fragen. Wie kann ich euch kontaktieren?
-Es gibt die Mailingliste [coderdojopotsdam-discuss](https://groups.google.com/forum/#!forum/coderdojopotsdam-discuss). Dort können Fragen gepostet werden, per Email an coderdojopotsdam-discuss⍟googlegroups⚜com (Zeichen entsprechend ersetzen).
+Es gibt die Mailingliste [coderdojopotsdam-discuss](https://groups.google.com/forum/#!forum/coderdojopotsdam-discuss). Dort können Fragen gepostet werden, per Email an coderdojopotsdam-discuss⍟googlegroups⚜com (Zeichen entsprechend ersetzen). Alternative schreibe eine [Nachricht](mailto:klub-coderdojo-sprecher@hpi.de) an die Klubsprechenden.
## Wie bekomme ich mit, wann das nächste Dojo ist?
@@ -65,4 +66,4 @@ Darauf weisen wir explizit hin.
## Darf ich auch programmieren lernen?
-Ja. Du kannst das selbe ausprobieren, aber auch schon was anderes. Sprich uns darauf an, was es gibt und sei bei der Vorstellungsrunde dabei. Es wäre schade, wenn wir Verständnislosigkeit der Eltern fördern würden. Deswegen kannst du mitmachen und auch was lernen und so dein Kind besser untersützen.
+Ja. Du kannst das selbe ausprobieren, aber auch schon was anderes. Sprich uns darauf an, was es gibt und sei bei der Vorstellungsrunde dabei. Es wäre schade, wenn wir Verständnislosigkeit der Eltern fördern würden. Deswegen kannst du mitmachen und auch was lernen und so dein Kind besser unterstützen.
diff --git a/index.md b/index.md
index 7db4f85..637061a 100644
--- a/index.md
+++ b/index.md
@@ -4,28 +4,30 @@ title: CoderDojo Potsdam
subtitle:
---
-> ### nächstes Dojo am 11.11.2023
+> ### nächstes Dojo am 14.06.2025 14:00 - 17:00 H-E.51/52
{: .center }
[zur Anmeldung](/anmeldung){: .btn .center}
-Ein Dojo ist ein freier, von Freiwilligen geleiteter, Community-basierter Computerclub für junge Menschen. Jeder im Alter von 7 bis 17 Jahren kann ein Dojo besuchen und Programmieren lernen, eine Website erstellen oder eine App oder ein Spiel erstellen. Dojos sind ein Ort, an dem Kinder und Jugendliche Technologie in einer informellen, kreativen, sicheren und sozialen Umgebung erkunden können.
+Ein Dojo ist ein freier, von Freiwilligen geleiteter, Community-basierter Computerclub für junge Menschen. Jeder im Alter von 5 bis 17 Jahren kann ein Dojo besuchen und Programmieren lernen, eine Website erstellen oder eine App oder ein Spiel erstellen. Dojos sind ein Ort, an dem Kinder und Jugendliche Technologie in einer informellen, kreativen, sicheren und sozialen Umgebung erkunden können.

### Unsere nächsten Dojos
-**11.11.2023** offenes Dojo \
-**09.12.2023** Weihnachsspecial
+**14.06.2025**, 14-17 Uhr: offenes Dojo + Lego Mindcub3r \
+**12.07.2025**, 14-17 Uhr: offenes Dojo
Falls du immer die neuesten Termine und Infos bekommen willst, kannst du dich in unseren [E-Mail-Verteiler](https://groups.google.com/forum/#!forum/coderdojopotsdam) eintragen.
### Was solltest du mitbringen:
+- die ausgefüllten und unterschriebenen [Teilnahmebedingungen](/assets/Teilnahmebedingungen-CoderDojo-Potsdam.pdf)
- Du kannst gerne deinen eigenen Laptop oder dein Tablet mitbringen, ansonsten können wir dir aber auch einen Laptop stellen.
-- Wenn du 12 oder jünger bist, einen Begleiter für die gesamte Zeit (darf auch programmieren).
+- Wenn du 12 oder jünger bist, eine erwachsene Begleitung für die gesamte Zeit (darf auch programmieren).
- Bring gerne auch etwas zu Essen für dich und andere mit.
+
Du hast noch weitere Fragen? Dann schau in unserem [FAQ](/faq.md) vorbei oder schreibe uns eine [Nachricht](mailto:klub-coderdojo-sprecher@hpi.de).
[](https://www.google.com/maps/search/?api=1&query=52.39362999999999,13.13175){:width="100%"}
diff --git a/material.md b/material.md
index 804c434..8d33cdf 100644
--- a/material.md
+++ b/material.md
@@ -22,15 +22,17 @@ Schreibe eigene Programme, indem du Blöcke zusammen steckst.
- [Blockly-Spiele](https://blockly-games.appspot.com/?lang=de) - Puzzle, navigiere durch ein Labyrinth oder bewege Vögel - mit Blockly lernst du die Grundlagen der Programmierung.
- [Labyrinth](https://blockly-games.appspot.com/maze?lang=de)
- [code.org](https://code.org/learn) - Minecraft, Star Wars, Anna und Elsa, Angry Birds, Flappy Bird - lerne Programmieren, indem du Rätsel löst.
-- [Snap](http://snap.berkeley.edu/index.html) - Baue dein eigenes Spiel oder eine Geschichte, indem du Blöcke zusammen steckst und malst.
- [Scratch](https://scratch.mit.edu/) - Erstelle eigene interaktive Geschichten und Spiele mit der App.
- [Invent with Scratch](https://inventwithscratch.com/book/)
- [Version 1.4](https://scratch.mit.edu/scratch_1.4/)
+- [Snap](http://snap.berkeley.edu/index.html) - Baue dein eigenes Spiel oder eine Geschichte, indem du Blöcke zusammen steckst und malst. Bringe Scratch zum nächsten Level, z.B. mit Funktionen zum Verfremden von Fotos.
- [App Inventor](http://appinventor.mit.edu/) - Erstelle eigene Android Apps. Es gibt eine Reihe von Tutorials, die du benutzen kannst.
- [Hour of Code Tutorial](http://tinyurl.com/AI-tutorial-untertitel)
- [Ardublocks](http://schuelerlabor.informatik.rwth-aachen.de/modulmaterialien/ardublock) - Programmiere den Arduino mit Blöcken, steuere LEDs und andere Bauteile an.
- [Programmieren mit der Maus](https://programmieren.wdrmaus.de/) - Programmiere mit der Maus aus der Wissenssendung "Sendung mit der Maus" des WDR
- [Paper-IO-Bot](https://niccokunzmann.github.io/paper-io-bot/) - Programmiere einen Bot für das Spiel Paper.io.
+- [Turtle Stich](https://www.turtlestitch.org/) - Turtlestich - Muster mit Blöcken programmieren, die mit Stickmaschinen gestickt werden können
+- [MIT App Inventor](https://appinventor.mit.edu/) - MIT App Inventor - mit Blöcken Android/ iPhone Apps programmieren
### Syntax
@@ -38,6 +40,8 @@ In textbasierten Programmiersprachen schreibst du dein Programm mit der Tastatur
- [Hamstermodell](http://www.boles.de/hamster/index2.html) - Steuere einen Hamster durch eine eckige Welt und hilf ihm, alle Körner zu finden.
- [Tutorial](http://freizeitkreis-bl.de/hamster/)
+- [Hedy](https://hedy.org/) - Hedy, Textprogrammierung für Klassenzimmer: Schritt für Schritt, Level für Level Richtung Python Syntax.
+- [Karel](https://web.stanford.edu/~cpiech/karel/learn.html) - Steuere Karel den Roboter über ein zweidimensionales Feld und schreibe C-ähnliche Funktionen, um verschiedene Aufgaben zu lösen
- [Go-Tour](https://go-tour-de.appspot.com/welcome/2) - Willkommen zu einer Einführungstour in die Programmiersprache Go.
- [Reguläre Ausdrücke](https://coderdojopotsdam.github.io/regex-tutorial/) - Mit regulären Ausdrücken kannst du Texte durchsuchen. Ein regulärer Ausdruck ist ein Muster, das in einem Text gefunden werden soll. In vielen Programmiersprachen kannst du reguläre Ausdrücke verwenden, um Zeichenketten zu durchsuchen. Man kann mit regulären Ausdrücken auch testen, ob die Eingabe von Programmen korrekt ist und ob Nutzer sich vertippen.
- [Project Euler](https://projecteuler.net/) - Project Euler is a series of challenging mathematical/computer programming problems that will require more than just mathematical insights to solve. Although mathematics will help you arrive at elegant and efficient methods, the use of a computer and programming skills will be required to solve most problems.