The plan is changing the way we deploy the conferences static sites. Currently we deploy conferences like "Elixir Conferences" that have many events (2015, 2016, etc) when we deploy all the events are updated with new info and new styles.
This workflow makes all the conference pages look the same (except for some embedded images) making it impossible to make deep changes without impact on old conference pages.
To ease the migration of the old pages and to make the work-flow better the proposal is to change how to deploy the site.
Instead of deploying conferences, we would deploy just events, that will make it possible to update one event without touching older events, making it possible to keep past conferences just as they are now (like frozen in time).
This change will be made application wide, not just for erlang-factory.
With that change in place, migrating old pages would not require the migration of all the data as we will just migrate the static sites as is.
Modify rules in nginx to point everything to a single location.
Change view: Events/index to allow deploy of event.
Remove deploy option from: Conferences/edit.
Check where is it used the conference info (header, urls, ask, etc) and move properly.
Remove option to deploy full conferences on conferences/edit.
Add script to fill past conferences with info from json. (to make it possible to update data on old webs)
Merge assets to make possible to have different versions of them.
Overwrite index only when appropiate.
Add file with info about events to be used in every conference. (json)
Make backup of the folder before the deploy and remove old backups.
Take all the static site info, copy and backup to make it possible to use everything together.
Fix assets links.
Test everything works properly.