GithubHelp home page GithubHelp logo

codeforamerica / codeforamerica.org-archive Goto Github PK

View Code? Open in Web Editor NEW
176.0 118.0 139.0 458.52 MB

The (former) @codeforamerica website

Home Page: http://archive.codeforamerica.org

License: Other

Python 0.51% Shell 0.02% HTML 92.60% Ruby 0.07% CSS 4.98% JavaScript 1.82% PHP 0.01%

codeforamerica.org-archive's Introduction

Build Status

Code For America Dot Org

This repository holds the source code and static assets for the last version of codeforamerica.org, which can be found at archive.codeforamerica.org. 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:

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/

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://0.0.0.0:4000.

Editing stylesheets

All CSS and stylesheets are hosted in the pattern-library repository, and served lived from http://style.codeforamerica.org.

Technology Patterns

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

Copyright

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

codeforamerica.org-archive's People

Contributors

aatwong avatar alanjosephwilliams avatar alexischarles avatar alukomnik avatar ashleymmeyers avatar beccablazak avatar brendastone avatar brielleplump avatar danhon avatar dharmishta avatar dschrimmer avatar ewee avatar fureigh avatar gjacobs86 avatar hannahyoung avatar jaime-alexis avatar jmadans avatar ladyson avatar lanebecker avatar mattboitan0 avatar matthewloveless avatar meghanreilly avatar mettabel avatar migurski avatar moniquebt avatar msantus avatar ondrae avatar phae avatar prestonrhea avatar zoeblumenfeld avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

codeforamerica.org-archive's Issues

class="page-title" is lost in image

Right now the text for class="page-title" get lost in the image. Either make the text pop or get rid of it all together and just use class="global header" to identify where you are on the site.

Lots of fellows links incorrect

Not all github links are github links (some are the twitter link).

Lots of linkedin links are broken.

Might want to verify the twitter handles are correct (mine got changed incorrectly a couple months ago, and had to change it).

CTA on /apps is broken link

the "let us know" link at the end of the top paragraph of the apps page goes no where - looks like it's intended to go to a form of some kind?

Summit County Page - List of Fixes Needed

Brigade Section

  • We have three links to the same destination. Should probably reduce that.

Last graf of the "2013 Fellowship in Summit County" Section

  • All URLs should be updated to tothetrails.com
  • Ohio & Erie Canalway Coalition (rather than ...Canal Coalition)

Articles & Videos Section

  • The use of the present tense is weird.
  • There is a dead and perhaps extraneous shortened URL at the end of the last graf "kng.ht/VeQgic"

Caption does not match photo

On http://www.codeforamerica.org/cities/louisville/, the photo of Shaunak, Laura and Marcin with the two prison officials is accompanied by this caption:

(L-R) Fellows Shaunak Kashyap, Marcin Wichary and Laura Meixell visit the prison guided by two prison guards..

The order of the fellows in the caption does not match the order of the fellows in the photo. Also, while we are changing it, these were Corrections officials, not prison guards. The caption should read:

(L-R) Fellows Shaunak Kashyap, Laura Meixell and Marcin Wichary visit the prison guided by two Corrections officials.

Citizens Page: What's Happening Links

On the citizens page under "What's Happening", the featured events and items like "Nov 19: Bike Hack NYU Rudin" need to be links but they are currently just text. When you create a link at that level, the CSS forces a new style. Can we keep the existing featured event style but leave room for those to be links?

Fix the CTA on /2013-partners

The list page of 2013 cities has a call to " if your city is interested in joining the 2014 program, apply here" - we should probably change these calls to action to something like "if you're interested in bringing the fellowship to your city, find out more" and then the /apply-now page should explain more thoroughly the current status of the application cycle.

Change Email Alias on Cities Page

  • Ask Santus to create new email alias -- [email protected] that goes to Luke, Jack, Dana, LD.
  • Add it to the Muni Innovation email alias
  • Test it on the page (Must be done during working session as Wufoo breaks form when changes are made after it's already been embedded)

Main Nav/IA

Going with the current proposed home page concept, we still need to sort out a main nav scheme for subordinate pages. One thought I have is that we keep the Programs nav but move it under "About" and simplify the rest of the navset to go with our cities, citizens, and donors CTAs. Like this:

About | Cities | Citizens | Supporters | Apps | Blog and then events/video/search as a little bloc in a corner?

About would then be:

Mission (landing page) | Team | Programs | Press | Jobs | Contact or something like that

Maybe About would be footer only though. Interesting question. This scheme privileges donors by pulling them out of About, and pushing Programs down.

This needs more thought but just getting it started.

CONTENT: Take Inventory of Geek Experience

Take inventory of the geek experience. Collect up:

CODE WE HAVE: Apps, API, Repo

EVENTS: From the Fellowship, Brigade, Startups, Mentoring

OUR GEEKS: Captains, Fellows, Founders, Mentors

Resolve text size differences in bio snippets & people pages

From Cyd: I'm not famous for my great eye, but to me the text styling for people cards in the pattern library looks different from how it comes out on the actual built version. Smaller type size and correspondingly smaller line spacing - the pattern library version looks much better to me (in particular the centering works better); do you see the same thing & can you tell what's going on?

Pasting text from the site adds crap

There's some odd little bit of code - no idea where such a thing would live - that causes text copied & pasted from our site to append a cluttering "see more at URL" string. It's not a huge use case, but it's super stupid. If we can find it and kill it, awesome. Like so - I will now paste some text from the site using ctrl-C ctrl-V:

if your city is interested in joining the 2014 program, apply here. - See more at: http://www.codeforamerica.org/2013-partners/#sthash.E0k1KUZe.dpuf

Google calendar widget - improve look & feel

In the interim, the google calendar widget is being used to display public events. It would be nice to dress this a bit to match the styleguide pattern for calendars.

Later, build something better for events.

Blog & site bios

Looks like many blog authors don't have bios in WP, even if they have bios elsewhere on the site. (Many current fellows & staff fall in this category.) This means their author page comes up without a bio at the top. A different and I think larger set of people doesn't have the right credentials (gravatar?) to have the summary bio show up on individual posts. This could be a good one to tackle in conjunction with alumni bios, since a lot of alumni are affected.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.