Initial Jekyll setup with separate source folder for the content

- Copy data, learning materials, templates, assets and styles from
the current website.
- Keep JS out for now.
- Only material and index page copied/created for now.
- See README for more on what this is about and the current steps.

Author: katrin-k

.gitignore

@@ -1,59 +1,12 @@
-# Logs
-logs
-*.log
-npm-debug.log*
-yarn-debug.log*
-yarn-error.log*
-
-# Runtime data
-pids
-*.pid
-*.seed
-*.pid.lock
-
-# Directory for instrumented libs generated by jscoverage/JSCover
-lib-cov
-
-# Coverage directory used by tools like istanbul
-coverage
-
-# nyc test coverage
-.nyc_output
-
-# Grunt intermediate storage (http://gruntjs.com/creating-plugins#storing-task-files)
-.grunt
-
-# Bower dependency directory (https://bower.io/)
-bower_components
-
-# node-waf configuration
-.lock-wscript
-
-# Compiled binary addons (http://nodejs.org/api/addons.html)
-build/Release
-
-# Dependency directories
-node_modules/
-jspm_packages/
-
-# Typescript v1 declaration files
-typings/
-
-# Optional npm cache directory
-.npm
-
-# Optional eslint cache
-.eslintcache
-
-# Optional REPL history
-.node_repl_history
-
-# Output of 'npm pack'
-*.tgz
-
-# Yarn Integrity file
-.yarn-integrity
-
-# dotenv environment variables file
-.env
-
+# Jekyll
+_site
+.sass-cache
+.asset-cache
+.jekyll-metadata
+
+# Git
+.git
+
+# Local files
+.DS_Store
+.vscode

.ruby-version

@@ -0,0 +1 @@
+2.3.3

Gemfile

@@ -0,0 +1,36 @@
+source "https://rubygems.org"
+
+# Hello! This is where you manage which Jekyll version is used to run.
+# When you want to use a different version, change it below, save the
+# file and run `bundle install`. Run Jekyll with `bundle exec`, like so:
+#
+#     bundle exec jekyll serve
+#
+# This will help ensure the proper Jekyll version is running.
+# Happy Jekylling!
+gem "jekyll", "~> 3.8.5"
+
+# This is the default theme for new Jekyll sites. You may change this to anything you like.
+# gem "minima", "~> 2.0"
+
+# CSS related gems
+gem 'sassc'
+gem "autoprefixer-rails"
+gem 'rouge', '~> 3.1.1'
+
+# If you want to use GitHub Pages, remove the "gem "jekyll"" above and
+# uncomment the line below. To upgrade, run `bundle update github-pages`.
+# gem "github-pages", group: :jekyll_plugins
+
+# If you have any plugins, put them here!
+group :jekyll_plugins do
+  gem "jekyll-livereload"
+  gem 'jekyll-seo-tag'
+end
+
+# Windows does not include zoneinfo files, so bundle the tzinfo-data gem
+gem "tzinfo-data", platforms: [:mingw, :mswin, :x64_mingw, :jruby]
+
+# Performance-booster for watching directories on Windows
+gem "wdm", "~> 0.1.0" if Gem.win_platform?
+

Gemfile.lock

@@ -0,0 +1,84 @@
+GEM
+  remote: https://rubygems.org/
+  specs:
+    addressable (2.5.2)
+      public_suffix (>= 2.0.2, < 4.0)
+    autoprefixer-rails (9.4.0)
+      execjs
+    colorator (1.1.0)
+    concurrent-ruby (1.1.3)
+    em-websocket (0.5.1)
+      eventmachine (>= 0.12.9)
+      http_parser.rb (~> 0.6.0)
+    eventmachine (1.2.7)
+    execjs (2.7.0)
+    ffi (1.9.25)
+    forwardable-extended (2.6.0)
+    http_parser.rb (0.6.0)
+    i18n (0.9.5)
+      concurrent-ruby (~> 1.0)
+    jekyll (3.8.5)
+      addressable (~> 2.4)
+      colorator (~> 1.0)
+      em-websocket (~> 0.5)
+      i18n (~> 0.7)
+      jekyll-sass-converter (~> 1.0)
+      jekyll-watch (~> 2.0)
+      kramdown (~> 1.14)
+      liquid (~> 4.0)
+      mercenary (~> 0.3.3)
+      pathutil (~> 0.9)
+      rouge (>= 1.7, < 4)
+      safe_yaml (~> 1.0)
+    jekyll-feed (0.11.0)
+      jekyll (~> 3.3)
+    jekyll-livereload (0.2.2)
+      em-websocket (~> 0.5)
+      jekyll (~> 3.0)
+    jekyll-sass-converter (1.5.2)
+      sass (~> 3.4)
+    jekyll-seo-tag (2.5.0)
+      jekyll (~> 3.3)
+    jekyll-watch (2.1.2)
+      listen (~> 3.0)
+    kramdown (1.17.0)
+    liquid (4.0.1)
+    listen (3.1.5)
+      rb-fsevent (~> 0.9, >= 0.9.4)
+      rb-inotify (~> 0.9, >= 0.9.7)
+      ruby_dep (~> 1.2)
+    mercenary (0.3.6)
+    pathutil (0.16.2)
+      forwardable-extended (~> 2.6)
+    public_suffix (3.0.3)
+    rake (12.3.1)
+    rb-fsevent (0.10.3)
+    rb-inotify (0.9.10)
+      ffi (>= 0.5.0, < 2)
+    rouge (3.1.1)
+    ruby_dep (1.5.0)
+    safe_yaml (1.0.4)
+    sass (3.7.2)
+      sass-listen (~> 4.0.0)
+    sass-listen (4.0.0)
+      rb-fsevent (~> 0.9, >= 0.9.4)
+      rb-inotify (~> 0.9, >= 0.9.7)
+    sassc (2.0.0)
+      ffi (~> 1.9.6)
+      rake
+
+PLATFORMS
+  ruby
+
+DEPENDENCIES
+  autoprefixer-rails
+  jekyll (~> 3.8.5)
+  jekyll-feed (~> 0.6)
+  jekyll-livereload
+  jekyll-seo-tag
+  rouge (~> 3.1.1)
+  sassc
+  tzinfo-data
+
+BUNDLED WITH
+   1.17.1

README.md

@@ -1,2 +1,54 @@
 # next
-The next version of CSSclasses’ website.
+The next version of CSSclasses’ website - continuously in draft mode (as of December 2018).
+The website is built using [Jekyll](https://jekyllrb.com/).
+
+## what?!?!
+One dark November evening, Bastian and Katrin sat together wondering how we could enhance the material section of our website. And while having a look into the current website's code we realized: Quite a bit of the setup is outdated (hi Bower), some not really necessary, barriers are quite high for external contributors, let alone people who only just started web development, the material section is not really scalable. Quite a few things came together. 
+Now, we don't want to be those folks who overthrow all and start everything from scratch. Yet, here we are… 
+
+We have a few goals and ideas:
+- Better readability/usability of the materials. Hence, we want to start with a skeleton that puts the (scalable) material section into the center of attention.
+- Split existing material content into several pages or sections by using post cetagories (such as the basics, the html, the css). The nodeschool website has been an inspiration here. 
+- Add challenges and resources to each chapter as they fit. 
+- We can add more category sections. e.g. tooling/needed software or how to publish a website. 
+- Have a low-barrier setup for external contributors. This means as little as possible software for the setup.
+- As our whole existence is based on the belief that CSS is a simple and low-barrier entry language, why not do as much as possible with (vanilla) CSS. 
+- Reuse layouts and css from the current website while not constraining ourselves (whatever that will mean exactly, pragmatism might rule).
+- Replace screenshots with editor-agnostic images. 
+
+## Work log
+Initial setup (Dec 3, 2018)
+- Copy all posts as is.
+- Copy svg and images as is into assets folder.
+- Copy data directory from the current website as is
+- Copy favicons as is into to assets/favicons subfolder.
+- Copy all layouts and includes as is. Boil down layouts to default, page and post.
+- Copy sass files as is for now. Use jekyll's built-in sass work flow.
+- Missing: all other pages than index.html. 
+- Rework: Materials now is a list page. Categories for the loop can be found in `_config.yml` as well as in the posts.
+
+# Setup
+
+## Requirements
+
+1. Ruby: Ensure you're running ruby 2.3.3. Newer version might have trouble running jekyll.
+2. Bundler: You can test if you have bundler installed by typing (or copy&paste) this command into your terminal: `bundler -v`. If it says "command not found", you need to install bundler with this command:`gem install bundler`.
+3. Git
+
+## Set up for maintainers
+1. Clone the repo: `git clone [email protected]:CSSclasses/next.git`
+2. Change into the repo directory: `cd next`
+2. Run `bundle install` to install dependencies (in case of command not found,
+  install bundler using `gem install bundler`)
+4. Run `bundle exec jekyll serve` to run Jekyll
+5. Open <http://localhost:4000/> to see generated site
+
+## Setup for contributors
+The CSSclasses website is built using Jekyll. In order to set up and run the site locally for development, you'll need the requirements (Ruby, Bundler, git - see above), create a GitHub account, and fork this repo. 
+
+You can read about forking a repo and cloning your fork [in the GitHub docs](https://help.github.com/articles/fork-a-repo/). When forking, you might be asked where you want to fork the repository to; select your own Github profile.
+
+Once you cloned the repo to your local computer and configured the snychronization, run these commands:
+1. Run `bundle install` to install all required packages
+2. Run `bundle exec jekyll serve` to run Jekyll
+3. Open <http://localhost:4000/> to see the generated site

_config.yml

@@ -0,0 +1,76 @@
+# Welcome to Jekyll!
+#
+# This config file is meant for settings that affect your whole blog, values
+# which you are expected to set up once and rarely edit after that. If you find
+# yourself editing this file very often, consider using Jekyll's data files
+# feature for the data you need to update frequently.
+#
+# For technical reasons, this file is *NOT* reloaded automatically when you use
+# 'bundle exec jekyll serve'. If you change this file, please restart the server process.
+
+# Site settings
+# These are used to personalize your new site. If you look in the HTML files,
+# you will see them accessed via {{ site.title }}, {{ site.email }}, and so on.
+# You can create any custom variable you would like, and they will be accessible
+# in the templates via {{ site.myvariable }}.
+title: CSSclasses
+email: [email protected]
+description: >- # this means to ignore newlines until "baseurl:"
+  CSSclasses is a one day event for people who are interested in learning how 
+  they can create and manipulate elements on a website.
+keywords: >-
+  CSS, HTML, learning, co-learning, workshop, frontend, web developement
+baseurl: "" # the subpath of your site, e.g. /blog
+url: "https://cssclass.es/" # the base hostname & protocol for your site, e.g. http://example.com
+faviconurl: "/assets/favicons"
+twitter_username: cssclasses
+github_username:  cssclasses
+
+# Build settings
+markdown: kramdown
+source: source
+sass:
+  sass_dir: assets/sass
+
+kramdown:
+  input: GFM
+  syntax_highlighter: rouge
+
+navigation:
+  - title: Home
+    url: /
+  - title: Learning Materials
+    url: /materials/
+  - title: About
+    url: /about/
+  - title: Coaches
+    url: /coaches/
+  - title: Attendees
+    url: /attendees/
+  - title: Run Your Own Event
+    url: /run-your-own-event/
+  - title: Code of Conduct
+    url: /code-of-conduct/
+
+categories:
+  - basics
+  - html
+  - css
+  - challenges
+  - resources
+
+
+# plugins:
+#   - jekyll-feed
+
+# Exclude from processing.
+# The following items will not be processed, by default. Create a custom list
+# to override the default setting.
+# exclude:
+#   - Gemfile
+#   - Gemfile.lock
+#   - node_modules
+#   - vendor/bundle/
+#   - vendor/cache/
+#   - vendor/gems/
+#   - vendor/ruby/

source/404.html

@@ -0,0 +1,24 @@
+---
+layout: default
+---
+
+<style type="text/css" media="screen">
+  .container {
+    margin: 10px auto;
+    max-width: 600px;
+    text-align: center;
+  }
+  h1 {
+    margin: 30px 0;
+    font-size: 4em;
+    line-height: 1;
+    letter-spacing: -1px;
+  }
+</style>
+
+<div class="container">
+  <h1>404</h1>
+
+  <p><strong>Page not found :(</strong></p>
+  <p>The requested page could not be found.</p>
+</div>

source/_data/cities.yml

@@ -0,0 +1,9 @@
+- name: Berlin
+  key: berlin
+  countryCode: de
+  introduction: CSSclasses was kicked off in Berlin by the teams of CSSconf EU and OpenTechSchool, and regularly offers beginner workshops and expert classes.
+
+- name: Hamburg
+  key: hamburg
+  countryCode: de
+  introduction: Hamburg is the second city where CSSclasses is taking place regularly. Since the first event in May 2016, regular beginner workshops and expert classes have been offered where everyone is encouraged to join.