Use Jekyll to generate the meeting list #8
Conversation
In order to take advantage of Jekyll on GitHub, simulate the version and configuration used there.
Switch to using Liquid templates for the homepage and move the actual meeting information into a Jekyll data file. At the moment, this isn't hugely different to the static version but with the data and presentation separated, we can hopefully start to do more interesting things (particularly if we attach more metadata to the meetings such as books discussed).
|
Is it practical to preserve more of the original formatting? For example, we used to have “Tuesday 14th October 2014”, whereas we now have “Tuesday, 14 October 2014”. (I’ve never used Jekyll.) |
|
Although of course what I meant to say is: this is totally brilliant. Thank you! |
|
Upsettingly, it doesn't seem like we can do ordinals with vanilla Liquid and Jekyll (there are plugins to provide it but GitHub Pages don't allow us to add any). I can definitely get rid of the comma however. |
|
It might also be worth adding a |
|
Ordinals: fair enough, it doesn’t matter anyway. I was also originally upset by the whitespace changes in the generated HTML but I really need to get a grip. |
|
Yes, a |
|
There is this work of insanity/genius: https://gist.github.com/rickydazla/5668017 Will add a README and Procfile, etc. |
|
Files added and date format tweaked. |
|
Actually, we might be able to automatically figure out the past and future meetings by comparing the meeting date with Still, worth getting this in first so other people can start using Jekyll features. |
Introduce Jekyll and Liquid templating to help with the later issues which will likely require using layouts and includes. The main example here is lifting the actual meeting information into a separate Jekyll data file [1] which is then used to automatically generate the list on the front page. I was hoping that we could even dynamically separate past and future meetings with a filter [2] but alas that doesn't seem possible and it would only change when we pushed changes to the site anyway. We can then use a similar pattern for a list of members and make it trivial to add yourself without having to get involved in the actual page design. Closes #8. [1] http://jekyllrb.com/docs/datafiles/ [2] http://jekyllrb.com/docs/templates/#filters
Introduce Jekyll and Liquid templating to help with the later issues which will likely require using layouts and includes.
The main example here is lifting the actual meeting information into a separate Jekyll data file which is then used to automatically generate the list on the front page. I was hoping that we could even dynamically separate past and future meetings with a filter but alas that doesn't seem possible and it would only change when we pushed changes to the site anyway.
We can then use a similar pattern for a list of members and make it trivial to add yourself without having to get involved in the actual page design.