-
Notifications
You must be signed in to change notification settings - Fork 5
Set up Hive Chicago Buzz 2017 app #38
Comments
Regarding archiving 2016 scheduleWe probably don't have time to get the archived 2016 app live before mid-March. Let's create a Get 2016 content off http://schedule.hivechicagobuzz.org/@hannahkane can you check with the team and see when we can replace/update http://schedule.hivechicagobuzz.org/ with 2017 app? http://schedule.hivechicagobuzz.org/ is tied to the |
And I just renamed this repo from |
Thanks, @mmmavis. This sounds like a good plan. @annmarie123 - can we go ahead and publish the content you have so far (detailed in #39) so that that's what people would see when the go to the site now, or would you prefer we wait until you have all of the content finalized? |
Go ahead and publish the content I sent. Thank you @hannahkane! |
kk I'll aim to have some basic stuff set up tomorrow. |
Got something working last night: http://mozilla.github.io/hive-chicago-buzz/ I'm working with DevOps to sort out some deployment problems as http://schedule.hivechicagobuzz.org/ doesn't reflect the changes I made still. There are still things I need to refine and think about, especially about the updating last minute session data changes. |
Thanks, @mmmavis. Please let me know when I can go in and update a json file to reflect the current schedule. |
@hannahkane for now let's file new ticket for new session info changes. I need to find a solution for non-devs to update the app. |
@mmmavis - thanks for your speedy work on this! I think this is fine, but I'm going to comment on the new ticket you just opened. In the meantime, do you think we're okay to close this ticket? |
heh this has already been closed. 😉 |
lol |
From @samueledyson: By early March we would like to update the content within the version of the schedule app that we used last year, http://schedule.hivechicagobuzz.org/. Ideally last year's content could be archived to http://schedule.hivechicagobuzz2016.org/.
@ScottDowne and @mmmavis - can you please advise on the best way to meet the requirement of maintaining last year's content in an archive?
The text was updated successfully, but these errors were encountered: