Add a list of all upcoming events (and past events).

A short version (next event only) could live on the front page.
The complete list could live under a new page "/events"/

minimum data per event:

• date
• start time
• end time
• city
• venue
• sign up link attendees
• sign up link coaches

Each list item should include:

• name of workshop (e.g. "CSSclasses", "CSSclasses with RailsGirls")
• date
• location
• if future event: Button "Register as Learner"
• if future event: Link "Sign up as Coach"

It is currently hard to find where to sign up for the next upcoming workshop.
Let's add a visible Call to Action (e.g. red button) in e.g. the sidebar navigation, and on the main landing page.

Subj.

Because the site is served via Github Pages, we have to use the gh-pages branch to push our changes. Building the site is done manually and the build is then pushed to gh-pages branch. The master branch should always represent the actual site and deploys should be done automatically after you commit to the master.

Furthermore, as CSSclasses grows, what do you think about having one or two maintainers per city to become faster in approving pull requests and deploying the site? Of course, code quality is very important, so I would suggest to have multiple reviewers if the pull request is more than fixing a typo.

At Hamburg workshops, we noticed that many people do not scroll through all the learning materials and therefore think, they are only relevant for beginners although they offer great challenges and links to useful external resources. I do not want to change the order of the chapters since this is an event focussed on beginners. Mentioning at the beginning of the learning materials that there are challenges and links to external resource down below would help to make this event more interesting for experienced attendees.

Whenever you make changes to any of the JavaScript source files and merge the changes to master, those files are not being overwritten when delpoying via Travis CI. Initial investigation suggested adding concat:development task to the build task.

Should give guidance on how to do it, and communicate a few base rules:

• CoC must be enforced
• OTS guidelines must be followed
• events must be free (or optional: donation-based)
• Organizers must actively work on inclusivity
• New organizers should have attended an existing event

Some inspiration here: http://cssconf.org/

For some reason our main font is loaded from localStorage only in Safari.

I assume the social media icons on the page are supposed to be displayed round, but they are displayed oval. This affects the icons in the footer but also the about page.

Browser: Firefox 52.0.1
OS: Windows 10 Pro (14393.953)

We got nice feedback from someone on Twitter https://twitter.com/TinaHolmboe/status/778150112254132228 . Tina is also right about the fact that the devdocs.io page completely relies on JS to display their content. I propose the find these links and replace them with something similar e.g. Mozilla's Developer Network.

Since we are organising CSSclasses in more than 1 city, it would be great to have a clean "About" page explaining in more details the concept and "why" CSSclasses take place, and list of all of the team members and coaches helping in each of the cities.

My suggestion is to replace the hero image on the subpages with a smaller top bar containing only the logo e.g. centre aligned logo with a transparent background.

With this approach we can improve the UX of presenting the people immediately with the context of the selected page :-)

Quite edge case-y, but here's a screen shot if you wanna know what it looks like:

I assume the sidebar introduces a second scroll layer once the viewport height is too low, causing this issue.

Whenever building the page (without running the local server via grunt serve), the minified JS code for CSSclasses doesn't show up. It seems like there might have been something missing in the config of the build job.

The jump marks inside our materials section do not work anymore.
Might be related to the JS error we're currently having?

It would be great to define a list of things/suggestions for other people on how to run an event like CSSclasses in their city. This will help us stay aligned and promote the idea even more.

cssconf/CSSclasses--old#85

Please collect your suggestions, observations, ideas 👻

I got some interest by people who might want to run a CSSclasses in their city. The guide should include:

• core values that are not to be messed with to be an "official" CSSclasses
• what do i need (room, coaches)
• how to i coach
• how can i engage people
• how to get help from us

cssconf/CSSclasses--old#42

Thanks to @radibit a page change between subpages is now noticeable. Personally I'm not entirely happy with the looks yet. Therefore I would be super thankful if someone comes up with another proposal. A quick sketch would be enough to discuss it further.

After @katrin-k split up the materials in #90 and not everything is in one page anymore, we'll need next/prev links at the end of the page (or somewhere).

During the CSSclasses today in Hamburg we got some feedback about the usability of the materials page, specifically the code view and its theme switcher.

Current behaviour

• First: Non-Coders are not used to dark/light themes or mostly have no preference. So the prominentely placed switcher may confuse ("Why dark/light, whats 'better'?")
• Second: The activated state of the theme switcher (for light theme a white dot in red box) looks more like the learned "empty checkbox". So a click on the assumed "unactive" element has no effect so it seems broken or useless and leads to the feeling of "Am I doing something wrong?"

Proposed behaviour

Either the checked state should be inverted or made clearer (hook, dot etc.)

What do you think?

The homepage is an important page for us. It should give a clear understanding for the user what CSSclasses is about and where events are taking place. Any ideas on how it should look are welcome. ;)

The learning materials are great but I think they lack of a section to show how to build a basic website layout. I am thinking of a website with a full width header, main content on the left, sidebar on the right and a full width footer. A tutorial on this topic could be especially interesting/helpful for attendees there for the second time or those who have some foreknowledge.

We at OpenTechSchool Berlin like and have used this workshop a lot in the past. As part of our efforts to make our events more inclusive, we'd like to translate it into other Languages so as to provide an entry to programming for people not entirely fluent in the English language.

We also have a Git workshop, in which we have participants make PRs to a not-so-useful repo.

With @bastianalbers we're contemplating running a Git workshop in which we ask participants to create PRs for translating the CSS classes.

Now, there's a range of technical options for including translations on Jekyll pages:

We could use Sphinx, which would require all content to be converted to reStructuredText, but would allow the repo to be translated using Transifex, which is much easier to use for non-Coders in the future.

Another good option would be using https://github.com/screeninteraction/jekyll-multiple-languages-plugin to translate stuff. It fits in better with the Ruby/Rails way of doing things (.yml files instead of .po files for translations, markdown support).

I don't have a strong opinion on using either of these options or even a third one, as long as it allows

• Interaction with the repository using git
• All translations are kept in the master branch (and ideally synchronized so there's a way of knowing whether a translation is out of date).

What do you think? I'd be happy to provide a PR that prepares the repo for being translated.

Update the README.md file so it reflects the current status.

Add a favicon to the website.

Dear CSSClasses team,
I wanted to share your website link http://cssclasses.cssconf.eu/ on Facebook but I saw that until now there is no thumbnail pic for preview. As we all know people love to see images on social media before they click on a link, I wanted to suggest this. :)

Cheers,
Thuy

I noticed that the navigation menu is not scrollable when the viewport height is not enough to display all items. This is really important for its usage, especially on mobile devices in landscape view.

I will purpose a small PR which is fixing that problem by making the navigation_element scrollable when it's needed :)

Some of the gems used by our project have vulnerabilities and we should upgrade them ASAP to the latest possible version.

Gems affected:

• yajl-ruby

Subj.