Skip to content

la2050/challenge

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

LA2050 Grants Challenge

This is a website for the My LA2050 Grants Challenge.

https://challenge.la2050.org/

Deployment status

staging-challenge.la2050.org

Netlify Status

challenge.la2050.org

github.com/la2050/challenge/deployments

How to make changes

The website is published with GitHub Pages & Netlify, and the files are generated with Jekyll.

Proposal images for the challenge are stored in the images.la2050.org repository and published separately.

As you make changes and commit/push them to GitHub, the website will automatically update.

For example, if you edit the about page on GitHub, and then press the “Commit changes” button–you should see your changes on the about page of the website within a few minutes.

How to switch between contest phases

The website is set up to show different content based on the current phase of the contest. To change which phase is active, you can follow these steps…

  1. Open the configuration file

  2. Find the current phase, and comment it out by placing a # sign in front of it.

For example, change this…

# New challenge announced: 
# February 1
phase: 1

…into this…

# New challenge announced: 
# February 1
# phase: 1
  1. Find the phase you’d like to switch to, and do the opposite (remove the # in front of it).

For example, change this…

# Entries being accepted: 
# March 1
# phase: 2

…into this…

# Entries being accepted: 
# March 1
phase: 2
  1. Commit your changes.

How to see a preview of your changes

If you’d like to see how your changes will look on the website before making them public, you can work in the staging branch–a copy of the website files, that’s published at https://staging-challenge.la2050.org

staging

You can make edits in the staging branch and commit them just as you would normally. They’ll automatically appear on the staging website within a few minutes.

Once you’re happy with how your changes look on the staging website, you can copy them over to the public website (the main branch) using a pull request. Here are the steps:

  1. Press the “new pull request” button.

https://github.com/la2050/challenge/pull/new/staging

1-new-pull-request-button

  1. Write a title for your pull request (this is optional).

  2. Press the “create pull request” button.

  3. And then, press the “merge pull request” button.

  4. And lastly, press the “confirm merge” button.

3-merge-pull-request

How to develop locally

If you want to see a preview of your changes while you work, you can run a Jekyll server on your local machine. Installing Ruby and Jekyll is a good place to start.

After you have Jekyll installed, you can clone this project with Git or GitHub Desktop

git clone https://github.com/la2050/challenge.git

And then start running the Jekyll application like this...

jekyll serve

Generating responsive images

Some of the images on the website are available in multiple sizes, to save bandwidth. For example, you can regenerate the “goals” images by following these steps…

  1. Install Node.js and NPM

  2. Run this command to install the dependencies for this project

npm install
  1. Place your images in the assets/images/goals/original folder
/assets/images/goals/original/connect.jpg
/assets/images/goals/original/create.jpg
/assets/images/goals/original/learn.jpg
/assets/images/goals/original/live.jpg
/assets/images/goals/original/play.jpg
  1. Switch to the _node directory and then run this command, to generate the images
npm run images:create

If you want to generate a different set of images, you can edit the gulpfile and then repeat the steps above.

Handy guides