For the past few months, we’ve worked with Colorado branding firm Dojo4, Brighton web design firm Clearleft, and our own internal communications and technology teams on a new visual design and front-end for the Code for America website. Today, we’re making the first of this work public and asking for input from the CfA community to ensure that the information presented on the site is accurate and up-to-date.
- Michal Migurski: code, hosting, copy/paste
- Cyd Harrell: information architecture, design
- Dana Oshiro: content, copy/paste
- Andrew Hyder: feedback
We need your help to keep our content accurate and up to date. The easiest way for to help is to submit a pull request with one of the below:
- For members of the community — including fellows, brigade captains, civic startups, and mentors — find yourself and your friends on one of the lists of civic hackers and let us know if your bio is correct and photo current. For staff, find yourself on the staff page and let us know if your bio is correct and photo current. Personal photos should be about 200 x 200px.
- If you built an app or project as part of the fellowship or accelerator programs, find it on the apps page and verify that we’ve got it described accurately.
- Check government information for brigades and fellowships on the 2015 government partners and alumni government partners pages and fill in any blanks you might find.
- We need quality photos for page headers. Should be about 1200 x 500px, JPG compressed to 150kb max.
An easy way to submit a pull request for just simple text changes is to:
- Find the page you'd like to edit on the master branch.
- Use Github's built in editor to make your changes.
- Down below the editor window, include a brief one sentence description of what you changed. Something like "Updated Andrew Hyder's bio".
- Click the green Propose File Change button.
- 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:
- Fork the project.
- Create a topic branch.
- Add the image in the correct directory.
- Commit and push your changes.
- Submit a pull request.
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.
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/codeforamerica.org/BRANCHNAME/
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 master branch), they can preview their changes using Jekit by going to:
https://jekit.codeforamerica.org/lolname/codeforamerica.org/master/people/dave-guarino/
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:
All CSS and stylesheets are run from the pattern-portfolio branch,
and served lived from http://style.codeforamerica.org.
Uses Jekyll for templating – converted HTML files are in the _site folder.
Copyright (c) 2009-2014 Code for America. See LICENSE for details.