GithubHelp home page GithubHelp logo

de-rse / de-rse.github.io Goto Github PK

View Code? Open in Web Editor NEW
14.0 14.0 52.0 194.5 MB

Web repository

Home Page: https://de-rse.org/

HTML 3.55% JavaScript 90.70% CSS 3.76% Ruby 1.31% Dockerfile 0.03% TeX 0.65%

de-rse.github.io's Introduction

www.de-rse.org hosting repository

This repository contains the source files for the de-RSE website. Its official hosting URL is https://www.de-rse.org.

The site is made to be built with Jekyll >= 3.4.1.

You can use RVM to install and use a suitable Ruby version, e.g., rvm use 2.7.

To build, run bundle install once (or skip that if you have dependencies already installed and bundler does not work for you) and then bundle exec jekyll build. To preview locally, run bundle exec jekyll serve --incremental and browse to http://localhost:4000. The --incremental flag helps speeding up the previews. To include drafts and future blog posts in the preview add the --drafts and --future flags. To see where exactly something breaks or takes long, add the --verbose flag. For all flags use the --help flag.

Contributions

To contribute, please fork, change, test locally (see above) and create a pull request against master.

You can use rake to comfortably create content.

Create content with rake

To create content, run one of the following commands from the repository root. Rakefile has been created by Ellen Gummesson and is hosted at https://github.com/gummesson/jekyll-rake-boilerplate.

rake post["Title"] creates a new blog post in _posts.

rake draft["Title"] creates a new blog post draft in _drafts

rake publish publishes blog post drafts from _drafts to _posts (interactive CLI-based picking of drafts to publish).

rake page["Title"] creates a new page (in the root folder).

rake page["Title","Path/to/folder"] creates a new page in the respective folder. E.g., to add a page to the English version of the site, use rake["Title","en"].

YAML headers for pages and posts

The repository contains minimal templates for pages and posts, _page.txt and _post.txt.

These are used when creating content with rake and include the minimal YAML headers needed for the content to show properly.

Pages

---
title:
layout: default
weight:
---

Pages always have the default layout. They must also have a (short) title (in double quotes preferably, so it doesn't mess with the YAML), which will be used for the main menu as item texts. weight determines the position of the respective menu item in the menu (ascending order).

Posts

---
title:
layout: post
author:
menulang: en
---

Blog posts will be displayed ordered by publication date on blog.html. They always have a post layout and must have a title and an author, both of which will be displayed on the blog index and the post page itself. Publication date is automatically added via rake publish. Do not start blog posts with headers (#), as the title will be displayed as header.

menulang determines the language of the main menu as displayed on the post page (default: en). The language menu items ("Deutsch", "English") link back to the blog index page in the respective language.

Redirects

You can also redirect pages to another URL by using the layout: redirect and defining a page to redirect to using a meta refresh.

---
title:
layout: redirect
redirect_page_to: https://xkcd.com
---

kramdown

For help on syntax have a look at:

Map

The map is fed by mapdata.js. Adding someone to the map is as simple as adding a new section in this geoJSON file. Coordinates are available from http://geojson.io/ . Right now pictures should be 75px high. Inspiration for a nice testimonial can be found at Stephan Druskat's entry.

The map appeared on Dec 6th 2017 on the website. It's based on leaflet v1.2 and Leaflet.markercluster

Events

Events are included per year from https://github.com/DE-RSE/de-rse.github.io/tree/master/_includes/events. No language specific remarks in favor of maintainability.

Converting slack signup domain list

Direct sign up domain list from https://de-rse.slack.com/admin/settings#signup_mode. Domains get added as people request invites.

echo "mpi-cbg.de,mpg.de,tu-dresden.de,crt-dresden.de,hu-berlin.de,tib.eu,dlr.de,gfz-potsdam.de,fmp-berlin.de,rfii.de,uni-goettingen.de,gcdh.de,uni-bielefeld.de,uni-bonn.de,dfg.de,awi.de,geomar.de,uni-muenster.de,helmholtz-hzi.de,tu-berlin.de,pik-potsdam.de,leibniz-fli.de,uni-wuerzburg.de,helmholtz.de,uni-konstanz.de,ac.uk,tu-braunschweig.de,sub.uni-goettingen.de,gwdg.de,fu-berlin.de,hzdr.de" | tr "," "\n" | sort | awk '{print "<li>"$1"</li>" ;}'

de-rse.github.io's People

Contributors

beastyblacksmith avatar bfrit avatar caha42 avatar dependabot[bot] avatar dfsp-spirit avatar diegosiqueir4 avatar eckhrd avatar fiveop avatar florianthiery avatar fsimonis avatar greatfireball avatar heidiseibold avatar iimog avatar janwieners avatar jlinx avatar jwuttke avatar katrinleinweber avatar knarrff avatar led02 avatar lutzbrusch avatar mahermanns avatar makish avatar mrtnhmtz avatar nuest avatar renefritze avatar schildwaechter avatar schlauch avatar sdruskat avatar stephanjanosch avatar tscheypidi avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

de-rse.github.io's Issues

Delete gh-pages branch

As user pages (such as this) must be built from master, it should be safe to delete gh-pages.

List Rocket Chat channels

There's a variety of channels on the GWDG Rocket Chat. Due to the structure of the instance, all channels live in the same namespace and may be hard to find (apart from the derse prefix).

We should list all channels on the website somewhere.

add different icons for chapters vs. people

I'm happy to make that change, any svg will do, but first:

Any ideas for icons?

  • just do different colours and add a small legend
  • use the RSE logo for chapters, keep the "markers" for people
  • combine RSE logo with flag for national chapters
  • combine RSE logo with X for local/regional groups

Decide on tracker loading strategy

Google recommends placing the tracking script call in the header rather than the footer. It's async, so that shouldn't be much of a problem (some false positives vs. loads of missing links).

Piwik also recommends to put the code in the header (I guess using the PHP tracker instead of the JS one doesn't make an awful lot of difference here?).

Hence, I'm inclined to put all tracking in the header. Don't wanna do it without polling the stakeholders for opinions though :).

@StephanJanosch @knarrff @mrtnhmtz , opinions?

Move conf2019 (and future confs) to new repository

This is to be tested, but in theory, if we created a repo per conference subsite, e.g., de-RSE/conf2019 and pushed all the content from that year's confreence there, it should resolve to https://de-rse.org/conf2019.

We would have to swap the language logic to the end of the path (https://de-rse.org/conf2019/en/...).

This way, we may lose some incoming links along the way. IMHO, this is fine for the one conference site, as the de-rse.org main site would still resolve fine, and people could track back the conf page from the main site...

This would make it much easier to create new conf subsites (i.e., create a new GH pages repo, perhaps we can build a template to fork), and would also probs bring down compile times for the sites, as the complicated logic in, e.g., <includes/_navbar.html> wouldn't be needed.

All we would need, then, would be a hard link in the navbar to the current (upcoming) conf, and a link on the events page to past confs.

What do you think, @knarrff @caha42 @nuest @StephanJanosch @mrtnhmtz @BFrit et al., have I overlooked something?

Gemfile.lock

Since @nuest checked in the "windows-compatibility version" we have a Gemfile.lock in the repo. Is that needed? I am not enough educated in ruby to fix this. I deleted the file locally and since then jekyll works again.

https?

No really needed, but nice to have

Categorize existing blos posts

Categorize for News and Blog, and also for German and English.

This will be re-used in the two submenus for the "News & Blog" top menu, which should link to a categories page for each of the categories.
Need to figure out cross-cat search for, e.g., News items in English only...

Update navigation for RSE 2019 conf

The website shall be extended by information regarding the RSE 2019 conference. The current navigation does not provide enough space to include all of these. Therefore the navigation shall be modified so that it contains a single link to the conference. Following this link will lead to the conference section of the page with different navigation elements.

Collect testimonials

In order to help people evaluate whether they "are an RSE", it'd be great to have a prominent definition (" What is an RSE") as well as testimonials ("I do this and that, etc. ... I am an RSE.") on the homepage.

Please use the following form if possible:

"[Description of tasks, field, and possibly position]. I am an RSE."
[Full name, first name, Blockchain hash, or whatever you'd like to appear here]

For example:
"I work in a linguistic research project where I develop scripts, plugins and complete apps so that the linguistic researchers can access, process and analyze their data. I am an RSE."
Stephan Druskat

host query on our own

after migration to jekyll host query by our own. From _includes/head.html

<script src="https://ajax.googleapis.com/ajax/libs/jquery/1.11.3/jquery.min.js"></script>

Update "Gemeinnützigkeit"

The association.html page states that non-profit status has been applied for, but IIRC it has been granted in the meantime. This should be updated.

comments in the blog

I looked up discuss alternatives. There are a few.

We would need a docker-instance for running our own comment service.

Translations of blog posts not linked to its original version

In case that blog posts exist in more than one language it is currently not possible to identify the corresponding post in the other language as no link between these posts exists.
As a consequence, you will be brought back to the main page when switching the language, while watching a specific post, instead of getting to that post in the other language. Following solutions could be possible:

  • Use identical file names with a 2-letter suffix for the language used (e.g. 2018-09-05-my-entry-en.md and 2018-09-05-my-entry-de.md)
  • add a unique identifier to the metadata of each blog post which is the same for all translations of the same article (e.g. blog-id=myentry1)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.