Updates don't show up

[gchrupala]

I updated my info in the source files, but according to the README someone has to manually run Jekyll to make the changes live on the website. (That seems like a weird setup BTW, is this on purpose?)

[wzuidema]

Ho Grzegorz, This is an feature inherited from my lab's website, from which many files were copies, where my PhD student Bas set it up in this way in order to be able to host it on the ILLC-server. I should probably simplify things, but problem is: I don't fully understand how it works. I'll check with Bas & Marianne. Best Jelle Op wo 9 dec. 2020 om 14:27 schreef Grzegorz Chrupała < notifications@github.com>:

…

I updated my info in the source files, but according to the README someone has to manually run Jekyll to make the changes live on the website. (That seems like a weird setup BTW, is this on purpose?) — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#5>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABGKAC7P2WYV622RPK6I7F3ST53NPANCNFSM4UTPTBGA> .

[mdhk]

Hi,

I found out that I still had this repo (and the right jekyll settings) locally, so I pushed a new website build with the updates (also for @dieuwkehupkes who e-mailed me earlier).

Indeed I think this setup is because I copied most things from the clc lab page when I made the website last year, but I agree it's not the best long-term plan if I need to always do the updates :) What I did are the three steps under 'Technicalities' in the README, so someone else could do it, though there were also problems last year. Tbh maybe the best solution is to make a new website, but I leave that to Jelle!

Marianne

[gchrupala]

For BlackboxNLP we have a website also hosted on Github pages, and also implemented with markup, but the HTML is generated automatically by Github every time there is a new commit. It shouldn't be too hard to switch interpretingDL to this kind of setup.

…

On Wed, Dec 9, 2020 at 5:34 PM Marianne ***@***.***> wrote: Hi, I found out that I still had this repo (and the right jekyll settings) locally, so I pushed a new website build with the updates (also for @dieuwkehupkes who e-mailed me earlier). Indeed I think this setup is because I copied most things from the clc lab page when I made the website last year, but I agree it's not the best long-term plan if I need to always do the updates :) What I did are the three steps under 'Technicalities' in the README, so someone else could do it, though there were also problems last year. Tbh maybe the best solution is to make a new website, but I leave that to Jelle! Marianne — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe.

[dieuwkehupkes]

Hey there, Both my personal website <https://dieuwkehupkes.nl/> and my i-machine-think website <https://i-machine-think.github.io/> run with jekyll. My personal website even uses the same template as the interpretable DL. I find it very convenient to use and it looks good on both browser and phone. I never have to compile anything, because this is done by github pages, but I do have a local setup so that I can locally view the changes that I am doing. I quickly tried to set this up for the interpreting DL website, but I'm getting a few errors (even for the jekyll build). There seems to be something wrong with the css file. Anyways, in general I would really recommend jekyll templates, and I like the template that you used for this website. It looks good both in different browsers and on phones (which only markup does not always) and liquid (the scripting language that is used) is fairly easy. Once you set it up, you should not have to do any complicated things. I do not know what is off with the current website (which looks fine online, btw), that would take me some more time to figure out. D. Op wo 9 dec. 2020 om 18:13 schreef Grzegorz Chrupała < notifications@github.com>:

…

For BlackboxNLP we have a website also hosted on Github pages, and also implemented with markup, but the HTML is generated automatically by Github every time there is a new commit. It shouldn't be too hard to switch interpretingDL to this kind of setup. On Wed, Dec 9, 2020 at 5:34 PM Marianne ***@***.***> wrote: > > Hi, > > I found out that I still had this repo (and the right jekyll settings) locally, so I pushed a new website build with the updates (also for @dieuwkehupkes who e-mailed me earlier). > > Indeed I think this setup is because I copied most things from the clc lab page when I made the website last year, but I agree it's not the best long-term plan if I need to always do the updates :) What I did are the three steps under 'Technicalities' in the README, so someone else could do it, though there were also problems last year. Tbh maybe the best solution is to make a new website, but I leave that to Jelle! > > Marianne > > — > You are receiving this because you authored the thread. > Reply to this email directly, view it on GitHub, or unsubscribe. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#5 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAV23YBY2TS3ABQVKSTETVDST6V2TANCNFSM4UTPTBGA> .