breaking out #2

• gov.uk/transformation
• pinterest board

breaking out #1

Info related to cost to possibly display for each project

• Cost reimbursable? (yes/no)
• Utilization rate
• #FTEs per week

Capturing a few things before I forget...

• Open Data Biweekly, open-data listserv
• Sunlight
• CFA fuzzies

Is this an issue with how I entered the data?

• Discovery
• Alpha
• Beta
• Live
• Major project milestones

(Similar to gov.uk's -> they also have great descriptions of each stage.)

Something that highlights projects using API-first strategy, api.data.gov, etc.

(breaking out #1 )

Who is working on this project? Little profile images?

breaking out #1

• chevrons aren't working on iPhone/iPad Safari
• text overlapping

• Take out (s) and make it magic (detect number of partners and add)
• Create slot for secondary folks in design.

Basic info to display about each project:

• Name
• Short description
• Date of last public demo/upcoming demo
• Contact info
• Rough start date
• Client
• License(s)
• Blog posts about the project
• API 1st project? (yes/no) (link to API docs)
• IAs/MOUs

Breaking out #1

breaking out #1

• add Sass
• create assets directory
• move appropriate files/directors to assets and update Jekyll to reflect new file structure

inspiration: http://nav.co/company/

ex: "In January, we pushed x # commits."

• Delete old stuff
• Clean to match 18f.gsa.gov structure

• gov.uk

breaking out #1

breaking this out of #17

Goal: https://18f.gsa.gov/dashboard serves this repo.

Possibly analytics to display for each project:

• Visitors
• Bounce rate

Show as graph over time?

breaking out #1

Possible info to display about each project from GitHub

• of commits

• Most recent commit
• Languages

• Stars, Watching

• Pull requests

• of Pull requests from non-18Fers

• Issues, # issues closed

To use the font file on gh-pages, we have to specify the full path to the files. Usually this is done through a Jekyll mustache dealy so it can be easily switched for local versus live. However, for the font as it is currently structured, there is a path in a css file, which Jekyll does not parse. This means we have to hard-code the entire path and choose whether to have it working locally or live. It is currently set to work live.

This deserves further thinking around how to make this better. There may be a way to move the font file to Sass, which Jekyll does parse and compile.

File in question: https://github.com/18F/dashboard/blob/gh-pages/assets/css/fonts.css

breaking out from #4

Info such as:

• total number of projects
• number of projects in each phase

• create a legend for project status (discovery, alpha, beta, etc.)
• color code each status type

If you visit https://18f.github.io/dashboard/, you'll see a ton of warnings in the console - fonts won't load, and the GovCode API can't be hit.

The GovCode API thing is a blocker, unless you proxy it somehow - its URL is http://api.govcode.org and it doesn't respond to https://, so it can't be fetched from an https:// page until it does. You could proxy all requests through nginx or something (like we did for https://18f.gsa.gov/listserv for GSA's Hydra service) but it'd be much better if GovCode added https:// support.

The font links have two problems - they are hardcoded to http://18f.github.io URLs, but even when updated to https://, they will only work for that website exactly. It'd be better to make those URLs relative (starting with a /) if possible.

cc @dlapiduz

Is the project on track? Is it behind? Is something blocking it? red/yellow/green status indicator

breaking out #2

could pull languages from github API, might not want to, though

(breaking out #2)

Ex: 18F/doi-extractives-data uses gh-pages branch

Impact measured by number of [potential?] citizens impacted, e.g. 50 million applicants per year

breaking out #2

The links are going to 18f.github.io/dashboard/[github repo]

Embed civic issues tracker on each project page once they add 18F. ht @codeforamerica @ondrae