Create /analytics page about 18f.gsa.gov HOT 23 CLOSED

P.S. I'm happy to take a first pass at this page.

from 18f.gsa.gov.

Can we talk through what makes sense here at the time you set up for next Friday?

from 18f.gsa.gov.

That'd be great. Thanks!

from 18f.gsa.gov.

Just realized that I'm out on Friday. Discuss this anyway -- I don't want to be a blocker. You can catch me up next week.

from 18f.gsa.gov.

I'm OOO, too, on Friday. Perhaps a reschedule?

Nevermind. Looks like several ppl have replied yes. Didn't realize it was a wide invite. Don't let me be a blocker either. Excited to see what y'all come up with!

from 18f.gsa.gov.

Don't worry - it's a recurring scheduler for each Friday to work on a wide range of website analytics projects. We won't get everything done in the first session. :)

from 18f.gsa.gov.

FWIW, it's not a recurring event on my cal. But maybe that's because I declined?

from 18f.gsa.gov.

Oy - sorry, my bad. Addressed.

c - 205.541.2245
Sr. API Strategist
Team 18F - GSA

• /Developer Program https://18f.github.io/API-All-the-X/
• US Government APIs listserve
  https://groups.google.com/forum/?fromgroups#!forum/us-government-apis

On Fri, Jun 27, 2014 at 12:02 AM, Hillary Hartley [email protected]
wrote:

FWIW, it's not a recurring event on my cal. But maybe that's because I
declined?

—
Reply to this email directly or view it on GitHub
#90 (comment).

from 18f.gsa.gov.

Ideas include:

• use the opensourced code from the gov.uk team
• host csv and pdf exports from GA

from 18f.gsa.gov.

Created a first pass at this - https://github.com/18F/18f.gsa.gov/tree/adding-analytics-page (specific page here)

Any thoughts? At issue would be sharing analytics from April, May, and June for:

• 18f.gsa.gov
• /Developer Program
• api.data.gov

@jpyuda, @quepol, @cscairns, @konklone - Any thoughts, questions, concerns? Otherwise, I'll upload those data files and propose this as a pull request.

from 18f.gsa.gov.

to put it in visual context:

Looks good to me as a start.

from 18f.gsa.gov.

Idea I had while in San Francisco... for stuff like this, where we have a larger vision of what this page/functionality could eventually be, does it make sense to create a "sandbox" where we can put our MVPs? Or, does it make sense to label it somehow as "MVP" or "Alpha," and we could do a link to a "What's an MVP/Alpha" page?

Also, @gbinal -- are you volunteering to keep this up-to-date until it is API-ified?

from 18f.gsa.gov.

@quepol - I am.

from 18f.gsa.gov.

To your other point, I'm not against a sandbox but it seems like that's already what our website is. My hope is that getting our MVPs up on the site is strong incentive for all of us to work on them more and iterate. If we keep our alpha projects too far out of sight, we as a team might not be driven to ever graduate them.

That said, one thing I'd definitely be in favor of would be 'beta' labels across a bunch of this stuff on our site.

from 18f.gsa.gov.

@gbinal I have been promoting to @quepol and @dutchashell that we should have a "GDS style" set of labels that describes expectations for the product. They call them Service Design Phases.

• discovery
• alpha
• beta
• production/live (no label)
• retirement/decommissioned

This is important for a number of reasons, like for example with MyUSA -- because it is alpha -- it may not offer telephone support at that service delivery phase.

Being consistent about these labels and what they mean is very very important so that a user knows where a product stands and what expectations they should have of it.

from 18f.gsa.gov.

Sounds good to me. Perhaps everything we do has a ribbon in the top right with one of those terms.

I'm not sure that would be in conflict with anything I offered in my last comment.

from 18f.gsa.gov.

Checking in on this again. Any problems with going live with this as a version 1 to build upon? If not, I can prep and build out a pull request directly.

@quepol, @konklone, @polastre, @jpyuda

from 18f.gsa.gov.

Quick sidenote, I'd also add a link the metrics page for api.data.gov.

from 18f.gsa.gov.

Another idea is to include an Analytics Policy or Standards

from 18f.gsa.gov.

I think I would make this part of the proposed /how-we-work page ( #131 ). That page could be a short
summary of all our policies and practices plus links to the actual documents on Github.

Note: this was in reply to analytics policy stuff.

On Fri, Aug 22, 2014 at 12:34 PM, Gray Brooks [email protected]
wrote:

Another idea is to include an Analytics Policy or Standards

—
Reply to this email directly or view it on GitHub
#90 (comment).

from 18f.gsa.gov.

This may be addressed by https://github.com/18F/Dashboard

from 18f.gsa.gov.

@gbinal, you have a branch with some work done, or it may appear in the Dashboard -- so I'm going to close this issue, but feel free to give it life again with a PR on your branch if you still want it in the site. (Though, you may want to revisit that branch and update it to pull in the Jekyll changes since it was first made -- and if you want to do that, and it's trouble, I'm happy to help make it work.)

from 18f.gsa.gov.

Preserving here and deleting the branch, probably worth resubmitting in the new Jekyll framework:

  <div class="container section">
    <div class="row">
      <div class="col-md-2"><a href="index.html" style="text-decoration:none;"><i class="icon-18f-logo" style="font-size:7em; color:#18f;"></i></a></div>
      <div class="col-md-10">
        <h1>Web Analytics</h1>
        <p class="lead">We strongly believe in using website analytics to better understand the needs of our customers and to drive decision-making.</p>
        <h2>18F.GSA.gov</h2>
        <ul>
        <li>June 2014 - <a href="">PDF</a>, <a href="">CSV</a></li>
        <li>May 2014 - <a href="">PDF</a>, <a href="">CSV</a></li>
        <li>June 2014 - <a href="">PDF</a>, <a href="">CSV</a></li>
        </ul>
        <h2>/Developer Program</h2>
        <ul>
        <li>June 2014 - <a href="">PDF</a>, <a href="">CSV</a></li>
        <li>May 2014 - <a href="">PDF</a>, <a href="">CSV</a></li>
        <li>June 2014 - <a href="">PDF</a>, <a href="">CSV</a></li>
        </ul>
        <h2>API.Data.gov</h2>
        <ul>
        <li>June 2014 - <a href="">PDF</a>, <a href="">CSV</a></li>
        <li>May 2014 - <a href="">PDF</a>, <a href="">CSV</a></li>
        <li>June 2014 - <a href="">PDF</a>, <a href="">CSV</a></li>
        </ul>
      </div>
    </div>

from 18f.gsa.gov.