Skip to content

lacrone/civic-project-mapping

 
 

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

36 Commits
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

This code is based of of Tom Kompare's https://github.com/tkompare/flushots2013.

This is a volunteer effort of the Kansas City Brigade of Code for America. http://codeforkc.org

The data behind this site is a Google Fusion Table

Problem Statement

Need for a community project map: The Community Capital Fund and our partners have realized through our work that a map of existing community-based projects does not exist and that often, neighborhood associations and organizations are not aware of projects/programs occurring near them, and often do not know of other organizations doing similar work. CCF believes that neighborhoods that partner with and learn from others doing similar work will have greater capacity, opportunities, and resources to carry out their work; will have a greater impact on community development and revitalization than when working in a silo; and will have a more sustained, long-term impact.

Running the Site Locally on Your Computer

To run the site locally on your own computer (most helpful for previewing your own changes),

Fork and clone the repository to a directory on your computer. Open the index.html file in your browser.

Technology Patterns

This a HTML/CSS/JavaScript web application.

Contributing

The list of beginner friendly issues is a great place to start!

In the spirit of free software, everyone is encouraged to help improve this project.

Here are some ways you can contribute:

  • by adding locations, see below
  • by reporting bugs
  • by suggesting new features
  • by writing or editing documentation
  • by writing code (no patch is too small: fix typos, add comments, clean up inconsistent whitespace)
  • by refactoring code
  • by closing issues
  • by reviewing patches

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 Gist that includes a stack trace and any details that may be necessary to reproduce the bug.

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.

Copyright

Copyright (c) 2014 Code for America Kansas City Brigade. See [LICENSE][] for details.

Releases

No releases published

Packages

No packages published

Languages

  • JavaScript 98.8%
  • CSS 1.2%