Need help with
Click the “chat” button below for chat support from the developer who created it, or find similar developers for support.

About the developer

179 Stars 144 Forks Other 10.0K Commits 60 Opened issues


The (former) @codeforamerica website

Services available


Need anything else?

Contributors list

Build Status

Code For America Dot Org

This repository holds the source code and static assets for the last version of, which can be found at Learn more about what Code for America does on our About page.

Note: Code for America's site is no longer built using the files in this repository. We've moved to another system (more details on that soon). If you want to report a bug or issue with the current site, please send an email to [email protected] or visit the site and use the live chat support feature in the bottom right of the page.

How It Works

We use Github like a content management system -- all our templates and content are collaboratively edited by staff and external contributors on Github. We use Jekyll to generate everything into static HTML files that are served using Apache.

How We Built it

Our technology and communications teams built the site in partnership with Brighton web design firm Clearleft and Colorado branding firm Dojo4. Ongoing maintenance and improvements on the site are done collaboratively with internal staff and external volunteers. Members of the CfA community are welcomed to provide their input using Github issues, or help make improvements by submitting a Pull Request.

Who’s Working On It

... and many more CfA staff members and community contributors.

How to contribute

Submitting a Pull Request

An easy way to submit a pull request for just simple text changes is to:

  1. Find the page you'd like to edit on the master branch.
  2. Use GitHub's built in editor to make your changes.
  3. Down below the editor window, include a brief one sentence description of what you changed. Something like "Updated Andrew Hyder's bio".
  4. Click the green Propose File Change button.
  5. You'll get to review your changes. If everything looks right, click the green "Send pull request" button.

If you need to add or replace an image, you'll need to:

  1. Fork the project.
  2. Create a topic branch.
  3. Add the image in the correct directory.
  4. Commit and push your changes.
  5. Submit a pull request.

Submitting an Issue

We use the GitHub issue tracker to track bugs and features. Before submitting a bug report or feature request, check to make sure it hasn't already been submitted. You can indicate support for an existing issue by voting it up. When submitting a bug report, please include a screenshot and any additioanl details that can help us debug, such as your operating system and browser version.

Previewing 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:

For a basic example of its usage, if GitHub user @lolname has made changes to the /people/dave-guarino page on their fork (on the

branch), they can preview their changes using Jekit by going to:

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


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

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

Editing stylesheets

All CSS and stylesheets are hosted in the pattern-library repository, and served lived from

Technology Patterns

Uses Jekyll for templating – converted HTML files are in the _site folder.


Copyright (c) 2009-2014 Code for America. See LICENSE for details.

We use cookies. If you continue to browse the site, you agree to the use of cookies. For more information on our use of cookies please see our Privacy Policy.