Figure out how non-dev staff can make session data changes - Githubissues

mozilla / hive-chicago-buzz

http://schedule.hivechicagobuzz.org

Mozilla Public License 2.0

1 stars 5 forks source link

Figure out how non-dev staff can make session data changes #43

Open mmmavis opened 7 years ago

mmmavis commented 7 years ago

Unlike MozFest we don't have a pipeline system set up to automate the deployment flow.

For devs to update this app, they

manually update session data
update master branch
run npm run stage https://github.com/mozilla/hive-chicago-buzz.git command to automatically delete and recreate gh-pages branch (changes made to gh-pages updates the production site).

For non-devs it would be tricky as they don't have dev environment set up

there's no way for them to test before pushing the changes. (accidental human errors will break the app)
they'll probably have to make changes directly to gh-pages branch. If devs uses the npm run stage command at a later time it will wipe out everything on the existing gh-pages and recreate gh-pages based on things on master branch - changes non devs made directly to gh-pages will not be reserved.

hannahkane commented 7 years ago

@annmarie123 - can you describe the process for finalizing the program? Once the sessions are decided later this month, do you expect to have any changes after the fact?