cfarm

GDI Town Hall
QUESTIONS

GDI Town Hall
Jan 9 – 11, 2019
#8688
 
46 questions

Popular

cfarm

In this article:

• Screen reader overview
  • Commonalities
  • Differences
    • Interaction modes
• Lessons

Overview

cfarm

Resources for Learning Git and Github workflows

• https://twitter.com/girlie_mac/status/905270297128865792
• Github flow https://gist.github.com/cfarm/80c953351da16604792c
• Intro to Git and Github Girl Develop It class http://cfarm.github.io/gdi-core-git-github

cfarm

Getting the data from Github

I am using d3's built in .csv method to get the data.

I save the data file url directly as a constant for right now. Later, I'm planning to provide an array or object with data urls (or use Github API to get them) so we can loop through each data file and generate the graph for each.

Formatting the data

I update some of the fields in the JS (not the original file) to make them easier to work with:

1. make the number fields number type
2. Change 'seasonally adjusted' to true and 'unadjusted' to false for easy conditionals

cfarm

front end walk through notes

• frontend.sh setup script running locally to build front end

• scripts.js - builds bundles including modernizr, es-5.shim in global header

• base.html: base HTML template

-webpack to bundle stuff. webpack-config.js.

• common_bundle used on all pages

cfarm

1. Show hidden files on your Mac. Open Terminal and run these commands (doesn't matter in what folder): (ref):

defaults write com.apple.finder AppleShowAllFiles YES
killall Finder

2. In Finder, go to your user directory and open the .bash_prompt file with Sublime Text. Note: if you don't have any fancy .bash_prompt stuffs you can steal mine from here. It will give you pretty colors + a kitten emoji to start with.
3. Go to line 57 and find the emoji that's there. Click on line 59 and go to "Edit > Special Characters."
4. Click the little keyboard icon in the top right window that pops up.
5. Choose your emoji and right click it to "Copy character info"
6. Paste that business into line 59 of the file.

cfarm

javascript:!function(){for(var c=document.getElementsByClassName("IssueLabel"),a=0,d=0;d<c.length;d++){var b=c[d].innerText;-1!=b.indexOf("points: 13")?a+=13:-1!=b.indexOf("points: 8")?a+=8:-1!=b.indexOf("points: 5")?a+=5:-1!=b.indexOf("points: 3")?a+=3:-1!=b.indexOf("points: 2")?a+=2:-1!=b.indexOf("points: 1")&&(a+=1)}document.querySelector(".progress-bar").style.marginRight="10px";c=document.createElement("span");a=document.createTextNode(" "+a+" points!");c.appendChild(a);document.querySelector(".js-project-header h3").appendChild(c)}();

cfarm

javascript:!function(){

    var labels=document.getElementsByClassName("IssueLabel");
    var pointsCount = 0;

    for (var i=0; i < labels.length; i++) {
        var label = labels[i],
            labelText = label.innerText;

        if (labelText.indexOf("points: 13") != -1) {

cfarm

javascript:!function(){var a=document.getElementById("pull_request_body");a&&(a.value+="Short description explaining the high-level reason for the pull request\n\n## Additions\n\n- \n\n## Removals\n\n- \n\n## Changes\n\n- \n\n## Testing\n\n- \n\n## Review\n\n- @user\n\n## Screenshots\n\n## Todos\n\n- \n\n## Checklist\n\n* [ ] Changes are limited to a single goal (no scope creep)\n* [ ] Code can be automatically merged (no conflicts)\n* [ ] Code follows the standards laid out in the [front end playbook](https://github.com/cfpb/front-end)\n* [ ] Passes all existing automated tests\n* [ ] New functions include new tests\n* [ ] New functions are documented (with a description, list of inputs, and expected output)\n* [ ] Placeholder code is flagged\n* [ ] Visually tested in supported browsers and devices \n* [ ] Project documentation has been updated (including the \"Unreleased\" section of the CHANGELOG)\n\n")}();

cfarm

javascript:!function(){var a=document.getElementById("new_comment_field");a&&(a.value+="### Code Review Checklist\n\n\* [ ] Do the changes address the project's needs?\n* [ ]  Do the changes respect the project's existing style?\n* [ ] Does the new code avoid reproducing existing functionality?\n* [ ] Are functions as simple as possible?\n* [ ] Is the code as efficient as possible?\n* [ ] Is the usage of each function clear?\n* [ ] Have edge cases been considered and tested for?\n")}();