Website repository setup and workflow

[skrings]

Website repository setup and workflow

This is a proposal for a website repository setup that should make our life a bit easier.

Repository

For each conference we should create a dedicated repository named <year>.rubyunconf.eu for the website.

DNS

Setup a subdomain for each conference with the year https://<year>.rubyunconf.eu
Redirect from https://rubyunconf.eu to the current conference subdomain https://2019.rubyunconf.eu

Workflow

• Create a new repository 2020.rubyunconf.eu
• Push code from 2019.rubyunconf.eu to 2020.rubyunconf.eu
• Setup DNS for https://2020.rubyunconf.eu
• Start over and edit the website as you want

Advantages

• We will gain stable links - shared links will continue to work next year
• Keep it simple - we don't have to fiddle around with last years decisions
• The old conference website stays available in its original form

Action Items

• Push old website to new repository rubyunconfeu/2018.rubyunconf.eu
  • Delete repository contents but keep a README
• Setup DNS for 2018.rubyunconf.eu
• Rename website repository to rubyunconfeu/2019.rubyunconf.eu
  • Remove contents of subpage /2018
• Setup DNS for 2019.rubyunconf.eu
• Setup redirect from https://rubyunconf.eu to https://2019.rubyunconf.eu
• Party on 🎉

Acknowledgement

Most of this was proudly found elsewhere.

Examples

JSUnconf

https://github.com/jsunconf

http://jsunconf.eu
https://2019.jsunconf.eu
https://2018.jsunconf.eu
https://2017.jsunconf.eu

The Conference

https://theconference.se/
https://2019.theconference.se/
https://2018.theconference.se/
https://2017.theconference.se/