Website for SRCCON:POWER
Clone or download
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
_config initial commit Sep 19, 2018
_data add transcript for Emmanuel/Julia session Jan 18, 2019
_includes add documentation page Dec 19, 2018
_layouts add support button Dec 19, 2018
_site catch up the site dir Dec 1, 2018
_transcripts add transcript for Emmanuel/Julia session Jan 18, 2019
media update nii logo Dec 7, 2018
schedule add transcript for Emmanuel/Julia session Jan 18, 2019
.travis.yml update travis notifications for slack Sep 20, 2018
LICENSE initial commit Sep 19, 2018
README.md initial commit Sep 19, 2018
_config.yml add talks transcripts to repo Dec 21, 2018
childcare.md update childcare page Nov 13, 2018
conduct.md go live update! Dec 12, 2018
dinner.md typo fix Dec 6, 2018
documentation.md add link to docs page Jan 15, 2019
facilitator_guide.md fix link typo Nov 20, 2018
homepage.md update homepage message Dec 19, 2018
logistics.md adding accessibility details Dec 11, 2018
participation.md updating hotel, removing CFP link Nov 27, 2018
participation_form.md updating hotel, removing CFP link Nov 27, 2018
participation_thanks.md update participation language Oct 27, 2018
program.md add a couple transcript links Dec 4, 2018
resources.md add volunteer page Oct 11, 2018
scholarships.md update text after deadline for session proposals Oct 27, 2018
sessions.md edits for sessions and program page launch Nov 13, 2018
sessions_about.md staging for listing accepted sessions, adding program page Nov 12, 2018
sessions_proposal_faq.md update text after deadline for session proposals Oct 27, 2018
sponsors.md update text after deadline for session proposals Oct 27, 2018
sponsors_list.md add sponsor links Nov 29, 2018
support.md go live update! Dec 12, 2018
transcription.md add transcript for Emmanuel/Julia session Jan 18, 2019
volunteer.md add volunteer page Oct 11, 2018

README.md

SRCCON:POWER

This is the website for SRCCON:POWER, a new OpenNews event for 2018.

Build Status

How to update the SRCCON site

Testing changes locally

  • Clone this repository to your local machine.
  • For minor updates, work directly in the staging branch. For major updates, or if you're working on long-term changes to the site, create a new feature branch.
  • To test your work locally, run jekyll serve or jekyll build, and view the site in a browser.

Pushing to staging

  • When you're ready to have someone review a site update, update the staging branch in GitHub. If you're working in staging locally, you just need to push your code changes. If you're working in a separate feature branch, push that branch to GitHub and then open a pull request into staging and merge it.
  • NOTE: You do not need to commit updates to your local _site directory after you run jekyll build or jekyll serve. You only need to commit new or updated markdown documents and templates, and new or updated static media files.
  • A commit to the staging branch on GitHub will trigger an automatic build of the SRCCON staging site. This runs its own jekyll build process before copying everything to S3. (So any changes to the repo's _site directory will be ignored.)
  • The Travis CI process that handles this can take a minute or two to complete. Your changes will not be visible on the staging site immediately, but they'll be there quickly.

Pushing to production

  • Review your changes on the staging site, and if everything looks OK, come back to this repo and open a pull request from staging into master.
  • Merging a pull request into master, or pushing any commit to the master branch, will trigger an automatic build of the production site at work.srccon.org. Again, this runs its own jekyll build process before copying to S3, ignoring any changes to the repo's _site directory.
  • The production site is delivered through Amazon CloudFront so that we can serve a secure, https-enabled power.srccon.org. CloudFront also caches everything for performance. The rebuild process triggers an invalidation of the entire cache, but it still may take up to 10 minutes for site changes to be reflected on production.