clojurebridge / clojurebridge.github.io

Global ClojureBridge website, built with Jekyll/GitHub Pages.

ClojureBridge Website

Welcome! This is the repository for the clojurebridge.org website. We are happy to receive your contributions.

How to get started

You can either create and modify files here on GitHub or clone the repository and view the website on your computer.

The website is powered by Jekyll, GitHub pages and Markdown. Jekyll is a Ruby gem that lets you create simple blogs that are easy to maintain.

You might have to install a new version of Ruby, if you don't have it yet. After that you can run the following command in the Terminal:

gem install jekyll

Clone the repository, cd into it, pull the latest changes and enter bundle install in your Terminal. Once you are done with that you can run Jekyll locally with bundle exec jekyll serve and see it running in your browser at http://localhost:4000/.

If you run into problems with bundler/nokogiri etc. please checkout this PR thread.

Workshops

Jekyll has posts and we decided to make a workshop a post for convenience. Every post has its own markdown file. So just head over, create a new workshop post and send us a pull request.

Issues

We collect issues about things we still need to do. Please let us know in the issue if you want to start working on it.

Contact

If you have any questions please don't hesitate to contact us at [email protected].

clojurebridge.github.io's Issues

Make headline smaller on mobile

Should be like on the right.

Underline current-page-link in header

If a visitor clicks one of our pages (about, donate, get-involved etc.) on the website the item on the header should stay underlined.

Update nokogiri

The nokogiri dependency defined in Gemfile.lock has a known critical severity security vulnerability in version range < 1.8.1 and should be updated.

Google Maps error

The following error displays when trying to display google maps in the blog posts: this page didn’t load google maps correctly.

Minnesota workshop

subscribe to Travis CI

I just received this message:

Your Travis CI Trial

The trial for your Travis CI account "ClojureBridge (GitHub login: ClojureBridge)" is close to running out.

But not to worry, you have 10 builds left!

To ensure uninterrupted service, sign the account up for a subscription before the trial runs out. Note that you need to be an owner of the account to sign up for a subscription.

If you need more trial builds, simply reply to this email, and we can add more builds for you!

And if you have any questions, just shoot us an email, we are here to help :)

Thank you and have a great day!

The Travis CI Team

Rewrite the README and give contributing advice

Navigation bar - bottom bar

The navigation bar should have a bottom bar as before. Needs to be implemented.

Ups... Screwed up some margin at the homepage

I did this with my last PR. I am sorry, I will adjust this again.

Add more spacing or a picture on the single sites

We should add more spacing between the header and the content.
Or a picture on the single sites like at /donation.

⚠️ If we add more spacing then we need to see it the /donation page with the picture still looks good.

Add photo credit to the website

Since we use photos from flickr, we need to credit photo owners.

Old website will have small flickr icon(s) on the bottom of the top page. Each of those are links to the photo website on flickr.

Maybe, we should add another page to address credits? If a bunch of icons are lined up on the bottom, it would be ugly.

Pay Pal button on mobile/small screen

Pay Pal button on mobile should be adjusted.

Fix path of images and javascripts

If we use a relative path like ../assets that will only work on the startpage, because the other pages have other links and apparently everything gets rerendered completely if a user goes to a subpage.

Add 2018-12-01 Bilbao event

Write a script to update site.time and add TRAVIS CI

Jekyll would usually show old posts(=workshops) and no posts that have a future date. We turned the behavior around with these code lines:

{% assign curDate = site.time | date: '%s' %}
    {% for post in site.posts %}
        {% assign postStartDate = post.date | date: '%s' %}
        {% if postStartDate >= curDate %}
          <li>
            <span class="post-meta">{{ post.date | date: "%b %-d, %Y" }}</span>

            <h2>
              <a class="post-link" href="{{ post.url | prepend: site.baseurl }}">{{ post.title }}</a>
            </h2>
          </li>
        {% endif %}
    {% endfor %}

This works fine. The only problem is that site.time only gets updated once we deploy. And we might not deploy everyday. (A deploy happens everytime we push to gh-pages branch.)

💡 The idea is to write a script that updates site.time everyday.

Make a "there are no upcoming workshops" note

• Show a note that there are no upcoming workshops on home page
• sort posts in correct order
• desktop: make the whole event div clickable/link

support HTTPS

Malwine, could you comment on why supporting HTTPS has suddenly become very important?

CloudFlare is probably the best option:

Whilst GitHub Pages doesn't ordinarily support SSL on custom domains, CloudFlare's Universal SSL allows your users to access your site over SSL

The free plan should satisfy our requirements.

Update paypal button

https://github.com/ClojureBridge/board-private/issues/12

determine whether "map error" is detectable

#33 (comment):

If they forget latitude and longitude or don't know how to do it: Could we display a grey area/div? Because otherwise we get this "map error" thing which is not so nice 😰 :

Add the PayPal button to the donate and homepage(index.html)

We haven't yet moved the PayPal button to the donate page and the homepage.
We need to figure out a way to show the button in a nice way.

Set up Travis

If there is a way to prebuild Jekyll in Jekyll it would be nice to set it up for future contributors.

Dump sponsor logo images to this repo

While I have access to the S3 bucket, I'll pull all past sponsor logos from S3. Then, I'll dump those images in this repo. This is to rebuild past workshop websites. The directory will be assets/images/sponsors.

Adjust the ratio of the homepage

Version on the current website:

Version on our new repo:

On a large screen we probably want the ratio with the info text bigger. So the ratio looks more pleasant like on the current website.

[reminder] website needs google-site-verification meta tag

This meta tag is for our Google apps, precisely, emails of [email protected]. It sounds puzzled, but actually Google does verify by the meta tag in the http://clojurebridge.org website.

https://support.google.com/a/answer/63026?visit_id=1-636108722998863157-2696176997&rd=1

This change is required because our Google apps account became subdomain under Bridge Foundry.

The meta tag is below:

<meta name="google-site-verification" content="yGlpL-CQA6xFu5ZjUZDrh4YYbVXBkdMuKIQXLZx0Dwk" />

Links to Mailing List and prominent "Mail us" section

We should discuss and add the "Sign up for newsletter"-section to our homepage.

BEFORE:

At the moment the data goes to a huge spreadsheet and the data has to be retrieved from that sheet manually. I am not sure if submitting the form will sign one up to the newsletter automatically.

💡 Could we use a simple mail-chimp signup (with mail only) and send a global newsletter?

Update March 2017:

• Link to Workshop mailing list (for organizers)
• Link to Announcement mailing list (we need to create that one)
• Link to Curriculum mailing list
• "Mail us" section

Change DNS

Change the DNS to point clojurebridge.org to this GitHub Pages repository

default Gravatar is always used

When I run the site locally I see personal Gravatars, but at clojurebridge.org I see only the default image. Looking at the page source I noticed that we're including email addresses rather than MD5 hashes of email addresses. This suggests to me that GitHub is ignoring md5.rb, perhaps for security reasons.

Make the repository public once we are done moving it

In order to let people contribute to our website we should make the repository public once we are done with all basic changes.

• This includes setting up a file or a link to our code of conduct.

security vulnerabilities

https://github.com/ClojureBridge/clojurebridge.github.io/network/dependencies

ffi / ffi

jekyll / jekyll

rubyzip / rubyzip

Navigation bar

Before we used to have a navigation for smaller screen (e.g. mobile devices):

Expanded view:

💡 It would be nice if we implement that again.

TODO

• Make page links display nicely on mobile devices
• Make navigation bar stick to top on desktop
• Between 800px - 858px the nav links behave strange. They are a bit too low. Fix required.

make entire "card" link to event details page

#33 (comment):

Should the whole event div on the front page be clickable like on the current website? And should we add the hover text?

Style the workshop event page

The single event page should be styled like the old one 😄
⚠️ we need to figure out if there is a gem or library for the map.

Change wording on the whole page and explain the term "underrepresented groups in tech"

In the about page and all over the page we should have consistent wording. Instead of women we decided that chapter can choose a underrepresented group in tech to focus on. We should explain that term and make clear who that is.

Add a code of conduct for contributing

It is a good thing to have.
E.g. http://rubyonrails.org/conduct/

Links in normal text body should be underlined to make them visible