Skip to content


Switch branches/tags

Name already in use

A tag already exists with the provided branch name. Many Git commands accept both tag and branch names, so creating this branch may cause unexpected behavior. Are you sure you want to create this branch?

Latest commit


Git stats


Failed to load latest commit information.
Latest commit message
Commit time


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 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 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.


Website for SRCCON:POWER







No releases published


No packages published