codefordc / codefordc.github.com Goto Github PK

We have .css and .js files in several different root folders. Is there a reason why they shouldn't all be in the same folder?

Pull navbar code out into a separate file and include via JQuery so that it stays standard across pages

The help wanted page isn't visited nearly as much as the projects page itself, so it might be useful to put the help wanted issues on there, instead. It might actually be more useful than the Needs section that we're currently using.

Along these lines, we could also add in a beginner or entry-level tag to more clearly identify issues for people who are new to the project or new to coding.

Why don't we pull the upcoming events onto the site instead of just having a link to Meetup page? Meetup's API could work well for this (http://www.meetup.com/meetup_api/console/?path=/2/events). We could also create a second calendar with upcoming events for like-minded groups.

• Should civic.json have it's own repo? Maybe in collaboration with the Beta folks? I don't know if they're actively developing/using it; @stvnrlly?
• Would it be better to change the spec to not encode information in keys? This would mean changing politicalEntity, governmentPartner, communityPartner, and data to be more like needs; perhaps like "an array of politicalEntity objects, each of which has keys name and url."
• Right now the item numbered 12 is really a sub-point of its predecessor; can the structure of the document show this? (Also, I think the text in 12 doesn't make it clear that it expects these needs and wants to be objects with a single key, either need or want.
• The needs and wants are likely to change frequently and might be better left to an issue management system such as github's no?
• Could the text explaining categories more clearly state that its expecting an array of objects with a certain structure?

There is none, but there should be.

As in https://18f.gsa.gov/2015/12/15/how-bot-named-dolores-landingham-transformed-18fs-onboarding/, a bot would help people with Code for DC-specific orientation and help them figure out how to use Slack.

• contributing.md
• ISSUE_TEMPLATE.md
• PR_TEMPLATE.md

Add a page that explains how to pitch a project; provide a form to the Code for DC website that allows outside individuals or organizations that ability to submit project ideas.

suggested questions:

• what is your name?
• what is the name and URL of organization (if any)?
• describe your organization?
• what is the issue or problem?
• what would you like to see done?
• how would this help?
• is there any code or data available?
• can you commit to participating as a partner?

http://wamu.org/news/15/03/16/why_buy_a_book_when_you_can_go_to_dc_public_library_theres_an_app_for_that

For consistency of layout across the site, the layout-related divs could be moved into default.html.

Add information about community partners, municipal partner, other core volunteers to about page

It's a sorry state of affairs. Metadata cures all.

Right now, the description of the link to our google group is "An open conversation online about DC, what we're doing now, and what's next." This is great, but it's not really clear that this is the way to join our email listserv.

I suggest we change this to: "Join our email listserv or just browse our open conversation online about DC, what we're doing now, and what's next."

@stvnrlly I took a quick stab at some instructions in readme.md. I'm sure these are at least a little inaccurate. Could you take a look? Then we should probably link to these or include similar content on /projects.html as well.

that's not what they are supposed to do..

I don't know how things work, but it seems like the projects info pulls from the local data/projects.csv file rather than the spreadsheet. Am I missing an intermediary step where the Google spreadsheet becomes projects.csv?

It's one of two fields that CfA pulls, along with status, which we already have: https://github.com/codeforamerica/cfapi#civicjson

http://codefordc.org/guides/projectguide.html

Starting with the "To submit edits or issues, go here" at the top and all the links in the section titled "Put a civic.json file in that repo"

need to set up an account and add tracking code.

The Github API only provides the activity for the default branch (usually master), so the graph and ranking are not totally accurate. Some projects might be actively developing on more than one branch, or have separate tracks for master and gh-pges.

It seems that this is something that will have to be handled with a shell script, using something like git log and/or git shortlog.

We should provide content on how, specifically, to submit a blog post. This should happen at a minimum on the wiki for the repo or a .md file, but ideally somewhere on the site as well for less technical users.

A few points to keep in mind:
-like, what sort of stuff are you looking for?
-what exactly is the editorial process? what changes will you make to my post? will you ask my permission first?
-if submitting a pull request, what branch should I submit to and should it go in ../_posts or ../_drafts?
-if submitting non-html, who should I send it to and what do I need besides my text? (headshot dimensions, twitter handle, ...)

(feature request)

There's a ton of information there, and the gems are buried with a lot of rubble. It has good resources, e.g., for mapping. It will soon (Nov 18th!) have all the OCF data in json/xml/csv. It has tons of transit information. Each of these things is useful to multiple projects, and it seems like we end up sharing that knowledge in fairly informal ways. If there were a section on mapping, I know I'd use it! (And if there were a section for campaign contributions, I'd be happy to contribute to it.)

Additionally, it would be a great place to host a list of important data missing from the District's open data site.

The resources page should include information on various hosting options and how-tos on using them.

• AWS
• Heroku
  Any others???

For new and nascent projects

The link to index.html for the logo in the banner is broken on individual blog post pages (ex: http://codefordc.org/blog/2013/12/12/techlady-hackathon-recap.html).

I can't find the issue anywhere but the post pages. Maybe the link should be "/index.html" instead of just "index.html"? The other links in the header work fine.

It seems like everything is in the gh-pages branch, so why not delete master and just push to gh-pages?

In case people still use RSS feeds?

• http://www.washingtonpost.com/news/local/wp/2015/02/06/at-risk-funding-in-the-district-school-by-school/
• http://nextcity.org/features/view/open-data-cities-mark-headd-philadelphia-michael-nutter
• http://technical.ly/dc/2014/10/01/applying-low-income-housing-pain-code-dc-building-hack/

Shall we migrate to civic.json? BetaNYC is using it and while the standard is still in development, the new CfA API is building on it. Also, it's pretty well thought out.

We could slightly revise our spreadsheet to make it a superset of the civic.json keys and then write a script that translates it. @stvnrlly @justgrimes

The hyperlink to Code for DC Slack is missing....

As more projects start to use the "First-time contributor" label, those issues should get pulled into the site

A variety of good open source solutions have been employed by teams and there should be links and how-tos for them on the site

• Tabula
• Vagrant
• Libre Office
• Waffle.io
• Trello

Pepper Code for DC website with information from this document docs.google.com/document/d/1Fxab6rkoH9BmEfIJyF-YzW6tvkDHQPvH6OQvzpR8pQU/edit

It appears that the API call that we're using to send Slack invites doesn't send one if the email address had previously been entered. This is confusing for people who, for example, may have requested an invite months ago but didn't get around to signing up.

Using https://github.com/18F/analytics-reporter, we can show some stats for our main site and various projects.

This could be useful for people wondering about use cases and adoption for what we do, as well as monitoring the progress and health of projects.

e.g., http://codefordc.org/blog/2014/10/30/project-district-housing.html

May just be weirdness with subdirectory - see if it fixes itself on move to root path.

Add a donate button to the Code for DC website; Link: https://secure.codeforamerica.org/page/contribute/default?custom1=Code%20For%20DC

Similar to Code for Boston http://www.codeforboston.org/

There are a variety of online tools to do this. It may also be worthwhile to have pa11y check the website listed in any project on the projects page and include that in the display.

We should include something in the code of conduct explaining the essential details to give us. That will make sure that we know what's going on, but also gives a defined structure that might make it easier for people to report issues.

What should we encourage people to include?

Since it takes a second or two to get confirmation, people using our contact form often submit multiple times. This could be helped by making the button give an indication of submission, and then return it to its original state once the confirmation alert pops up.