search

opengovfoundation / madison

Madison is a platform for lawmakers to share legislation with their citizens, allowing the community to add comments and suggest improvements.
GNU General Public License v3.0
684 stars 108 forks source link

Add Inspectlet Heat-Mapping #185

Closed seamuskraft closed 9 years ago

seamuskraft commented 10 years ago

@bryanconnor do you think this is our best option? Thanks!

bryanconnor commented 10 years ago

Would this be for general analytics across the site? I suppose it couldn't hurt but one consideration is that elements on the site will be changing position somewhat rapidly for the foreseeable future. I don't know if you've defined certain success metrics you want to get out of analytics generally but that might be a worthwhile exercise. What useful info do you want to get out of the heat-map?

seamuskraft commented 10 years ago

We'll have Google analytics on there either way, but in my mind, the heat map would first and foremost help us understand where users are spending the most time on the page, and secondarily where they are getting stuck and bouncing.

Good point on the moving pieces, but the thought is that the heat map would help us figure out what pieces need to be moved. What do you think?

Seamus Kraft Executive Director 760-659-0631 OpenGovFoundation.org @SeamusKraft http://Twitter.com/SeamusKraft

On Tue, Apr 1, 2014 at 5:20 PM, Bryan notifications@github.com wrote:

Would this be for general analytics across the site? I suppose it couldn't hurt but one consideration is that elements on the site will be changing position somewhat rapidly for the foreseeable future. I don't know if you've defined certain success metrics you want to get out of analytics generally but that might be a worthwhile exercise. What useful info do you want to get out of the heat-map?

Reply to this email directly or view it on GitHubhttps://github.com/opengovfoundation/madison/issues/185#issuecomment-39260638 .

cmbirk commented 10 years ago

@bryanconnor 's point is a good one. We aren't going to get anything useful out of this until our pages settle down. That being said, it doesn't hurt to plug it in.

This will only be on OpenGov instances, just an FYI.

seamuskraft commented 10 years ago

Agreed. - Seamus

On Tue, Apr 1, 2014 at 6:46 PM, Chris Birk notifications@github.com wrote:

@bryanconnor 's point is a good one. We aren't going to get anything useful out of this until our pages settle down. That being said, it doesn't hurt to plug it in.

This will only be on OpenGov instances, just an FYI.

Reply to this email directly or view it on GitHub: https://github.com/opengovfoundation/madison/issues/185#issuecomment-39270267

cmbirk commented 10 years ago

I'm setting this up to automatically include all js files in the /public/private directory. Our deployments right now will only link the following in that folder:

ga.js uservoice.js addthis.js inspectlet.js

But this will get changed with the build branch to concatenate these files to /public/private.js . This is so that any install-specific js files can just be dropped in this folder and excluded from the repos.

cmbirk commented 9 years ago

Closing this, as it's an organizational-level installation.