Making past editions accessible about hackdelft-website HOT 13 CLOSED

Agreed! A couple of remarks:

• I'd propose to redirect hackdelft.nl to 2018.hackdelft.nl instead, similar to how bapc.eu is handled. This way the website's URL never changes.
• We'd need to split up GitHub repositories for each year, similar to WISVCH/symposium-201{7,8}.

DNS and other infrastructure is managed by CH Beheer.

from hackdelft-website.

• I don't think redirecting hackdelft.nl to 2018.hackdelft.nl is very nice because people sharing the current year's event will end up using both links across social media etc. and seeing 2018.hackdelft.nl doesn't look as nice in text IMO.
• Agreed!

Who do we @ for CH Beheer? 😅

from hackdelft-website.

To me, not breaking any links would be a priority. That's why a redirect to the canonical URL (2018.hackdelft.nl) would be needed. Of course any marketing material could still use hackdelft.nl.

You can e-mail us (beheer@ch) or mention @WISVCH/beheer.

from hackdelft-website.

Okay, redirection sounds good then! 👀 @WISVCH/beheer

from hackdelft-website.

Done: WISVCH/web-01-nginx@a3441df

from hackdelft-website.

2017.hackdelft.nl is forwarding me to ch.tudelft.nl right now, but 2018 is working!

from hackdelft-website.

If you could create a 2017 repo then we can deploy that one as well :)

from hackdelft-website.

I forked this repository to my own account and reset it to the 2017 version, but GitHub won't let me transfer ownsrship back to WISVCH because it doesn't want to have multiple forks of the same repo on one account / organization (I think).

Should I just create a new repository for 2017 and upload all the files in there? We'd lose the history, but I can't think of another way of doing it.

(The 2018 site should've probably been made in a different repo than the 2017 site. We should make sure an eventual 2019 version does not continue on this repo as well, I think, so I propose renaming this repo to hackdelft-2018.)

from hackdelft-website.

Yes, you should be creating a new repository (hackdelft-2017) instead of forking. We can then rename this repository to hackdelft-2018 and remove the 2017 commits (making 3f7469e the actual first commit in this repository).

from hackdelft-website.

I created a new repository, hackdelft-2017 and copied the history of HackDelft-website to it. It needs to be reset to commit 736550e, but I don't think I'm authorized to force push, so I can't do it myself. Can you do that?

from hackdelft-website.

You're set up as an admin of the repository and branch protection is disabled. What's the error you're getting?

from hackdelft-website.

Hmm looks like my remote wasn't set; fixed that and it's up now at WISVCH/hackdelft-2017! I'm not sure if renaming this repo will break any deployment stuff, so I'll leave that to you.

from hackdelft-website.

Done: https://2017.hackdelft.nl/

2018 website without full 2017 history is now at https://github.com/WISVCH/hackdelft-2018, so I'll archive this repository. Feel free to open an issue in either repository if you have any more comments!

from hackdelft-website.