Skip to content
This repository was archived by the owner on Jul 11, 2023. It is now read-only.

Code4HR/code4hr

This branch is 99 commits ahead of, 567 commits behind sfbrigade/sfbrigade.github.io.2017-11-05:gh-pages.

Folders and files

NameName
Last commit message
Last commit date

Latest commit

457d979 · Nov 14, 2017
Nov 14, 2017
Oct 10, 2014
Oct 16, 2017
Sep 5, 2014
Apr 13, 2016
Sep 19, 2013
Aug 28, 2017
Sep 26, 2016
Jul 28, 2014
Oct 2, 2014
Oct 29, 2015
Oct 23, 2014
Oct 29, 2015
Sep 6, 2014
Feb 17, 2017
Sep 23, 2017
Sep 17, 2017
Aug 19, 2017

Repository files navigation

code4hr.org

The website for the Code for Hampton Roads Brigade

Goals

  1. Explain what Code for HR is and the type of work we do.
  2. To celebrate our events, projects, and discussions!
  3. Encourage current and new members to participate with clear ways to get involved.
  4. To have this site be easily reused by other Brigades just starting out.

Tech

Built using Jekyll, Bootstrap, and the CfAPI.

Contributing

Submitting an Issue

We use GitHub Issues to track bugs and features. We've included several of our open GitHub Issues right on our homepage using the Civic Tech Issue Finder.

Running the Site Locally on Your Computer

To run the site locally on your own computer (most helpful for previewing your own changes), you will need Jekyll installed (click here for Jekyll installation instructions.)

Fork and clone the repository, then run the following command in the root directory of the repo:

jekyll serve

or

jekyll serve --watch which will watch for changes to files.

Your computer should now be serving your local copy of the site at:

http://localhost:4000.

Sharing Your Changes Using Jekit

You can use the nifty Jekit app to preview changes you make to this site.

To do this, fork this repo, and commit your changes on a branch to your fork. You can then preview what your changes look like by navigating to:

https://jekit.codeforamerica.org/USERNAME/code4hr/BRANCHNAME/

For a basic example of its usage, if GitHub user @lolname has made changes to the projects page on their fork (on the master branch), they can preview their changes using Jekit by going to:

https://jekit.codeforamerica.org/lolname/code4hr/master/projects

Submitting a Pull Request

  1. Fork the project.
  2. Create a topic branch.
  3. Implement your feature or bug fix.
  4. Commit and push your changes.
  5. Submit a pull request.

Releases

No releases published

Packages

No packages published

Languages

  • HTML 83.6%
  • CSS 14.3%
  • JavaScript 2.1%