codeforboston / cambridge_voting_locations Goto Github PK

Only votecambridge.com is working at the moment.

Since this app was created, the internets have progressed, and you don't need Ruby anymore to build stylesheets. https://github.com/sass/node-sass exists, and there's https://github.com/sindresorhus/grunt-sass if we want to bind this via Grunt (which this app does right now, oh how times change). Removing multiple language dependencies FTW.

Should have a reasonable way to view the dates/hours each location is open. This uses the data that resolves #30

We should add Google analytics before launch. @beechnut, you should have access to the CfB Google account, otherwise tell me and I'll generate the code.

I created these UI concepts for mobile quite some time ago (two stylistic versions of the same interface), feel free to take or leave them - you'll have the call if you like, @EmilyDirsh.

I was using the Lato typeface from Google Fonts, but open to others - might be better to use something native to each platform like Roboto / Helvetica Neue.

The latest version of chrome does not support location tracking without using secure HTTPS for user safety.

We should consider setting up a free reverse proxy with https://www.cloudflare.com/ and moving the domain. @WheresHJ, can you please comment on where the DNS is hosted for this for our memory.

The site looks a bit dated. Let's update it 💃

It should support the features described by #31 and possibly #32

Steps to reproduce:

• Find an address and get result
• Click "back"
• Modal pops up and I can't change my mind and close it to get back to my results

When searching for the polling location of 1654 Massachusetts Avenue, Cambridge, MA, the precinct for the displayed polling place is not the same as the one shown. This location happens to be on the border between two precincts. See screenshot!

address autocomplete suggestions are hidden behind the main modal view (combination of z-index and absolute position issues)

Right now they open in the same tab, which isn't great since a user might click into one of them first thing on arriving. Both links should open in _blank.

When a street name in Boston is entered and the same street exists in Cambridge, the polling place for the location in Cambridge is displayed.

Example:
10 Pearl St., Boston --> 10 Pearl St., Cambridge
200 Mass. Ave., Boston --> 200 Mass. Ave., Cambridge

Try 14 Centre St. It's a real address, I promise.

examples:
52 Church St, Cambridge, MA 02138 (works. this is the sinclair)

Harvard Square (does not work. example of neighborhood)

(minimize all hours and address information into an accordion)

In the course of working on the styling and layout, I put in a few test addresses, including my own, and was directed to the wrong polling location.

You can see in the following two screenshots that the polling locations are very clearly outside of the correct prrecinct.

I will continue to work on this tonight

each ward/precinct has its own ballot. residents should be able to view their sample ballot based on where they live.

If the app is just for Cambridge, it would be nice to just have the Google search autocomplete scoped for only Cambridge addresses, without cluttering the results with other municipalities.

When obtaining directions for election day voting, the precinct polygon obscures visuals on the map.
Do we need to show the polygon at all?

In addition to the walking directions, not as a substitute

I'm getting the following console error on votecambridge.com

"Mixed Content: The page at 'https://votecambridge.com/' was loaded over HTTPS, but requested an insecure stylesheet 'http://fonts.googleapis.com/css?family=Open+Sans:400,300,600,600italic,700,800|Rokkitt:400,700'. This request has been blocked; the content must be served over HTTPS."

The font for the headings isn't loading

After going over the code in module findPollingLocationsFor (polling_location_finder.js) I noticed that after the (lat, lng) coordinates from the user location are found in one of the Cambridge precincts (districts). The precinct code property name (.WardPrecinct) is used to find a polling location with the same precinct code (hence the nearest polling location). However, this property is missing in the Early Voting Polling location geojson file and a few key property names like pollingLocation.geojsonProperties.LOCATION, pollingLocation.geojsonProperties.Address changed so the module will not work with this new geojson unless we standardize the property names in both files. Since the early voting locations are just 5, I will be adding the percincts code manually and standardizing property names in both geojson files in my own fork of the project. I will also be working on adding the polling hours and other features I have in mind in a secondary branch.

I think it would be great to see a link back to CFB and any feature or issues link to github.

This year the City of Cambridge is doing early voting, for the first time ever. We need to add these locations to our data sources.

See #29

The right side being covered:

There should be some map space between the map buttons and the right edge of the map. You can see that the "Report a map error" link is cut off.

Because the map is the full page width, one can't scroll past it on desktop without a drastic zoom out/in.

A media query should fix this.

When the app can't determine an exact address, it places the alternatives in the "directions" box, which is good. However, it doesn't close the modal window and so those options are inaccessible, which is bad.

We should close the modal window in this case.

Include a link for Cambridge MA election information: http://www.cambridgema.gov/election

Right now there's a long pause before it takes me to the location result. It should have some sort of indication that it is loading/searching for data...

Early voting locations are on the data portal: https://data.cambridgema.gov/General-Government/Early-Voting-for-2016-Presidential-Election/xd4d-326b

The recently added data is https://github.com/codeforboston/cambridge_voting_locations/blob/2016/app/scripts/vendor/EARLY_VOTING_AddressPoints.geojson?short_path=e049801

Just want to make sure the listed dates and hours still match.

Steps to reproduce:

1. Create production build (npm run build)
2. Open website (e.g., cd dist && python -m SimpleHTTPServer)
3. Perform some kind of action that uses GeoJSON, for example, find an election day polling location
4. Verify that a JavaScript error occurs

I've narrowed it down to GeoJSON by modifying the uglify config in Grunt:

grunt.initConfig({
  uglify: {
    options: {
      mangle: false,
      compress: false
    }
  }
  /* ... */
});

As noted on that repo, Google Maps API now supports GeoJSON.