Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Civic hacking: build your cred while doing good

856 views

Published on

Delivered at Write/Speak/Code 2016. @fureigh

Published in: Software
  • Be the first to comment

  • Be the first to like this

Civic hacking: build your cred while doing good

  1. 1. Civic hacking: Build your cred while doing good @fureigh
  2. 2. Hi, I’m Fureigh! @fureigh
  3. 3. 18F is a digital consultancy for the U.S. government, inside the U.S. government. WHAT? @fureigh
  4. 4. Just start. MVP. Learn and iterate. Delivery is the strategy.
  5. 5. 180+ people 45% DC 55% everywhere else
  6. 6. Making an impact while building your open source portfolio @fureigh
  7. 7. Why contribute to open source? @fureigh
  8. 8. ● Share your work and express yourself. ● Develop new skills. ● Build community, learn from others. ● Build your portfolio. ● Some of us just like to be helpful. @fureigh
  9. 9. And why civic tech? @fureigh
  10. 10. IMPACT @fureigh
  11. 11. @fureigh
  12. 12. @fureigh
  13. 13. @fureigh
  14. 14. @fureigh
  15. 15. community-minded @fureigh
  16. 16. You are uniquely qualified. @fureigh
  17. 17. Okay, but also... @fureigh
  18. 18. @fureigh
  19. 19. @fureigh
  20. 20. Open source is your friend @fureigh
  21. 21. There’s a world out there @fureigh
  22. 22. This is 18F!
  23. 23. We are 18F!
  24. 24. We are 18F!
  25. 25. And many cities and states. @fureigh
  26. 26. There’s also Code for America. @fureigh
  27. 27. ex: Adopt-a-Hydrant @fureigh
  28. 28. So how do you find these people? @fureigh
  29. 29. @fureigh
  30. 30. Meetups (find one or start one) @fureigh
  31. 31. Civic Tech Issue Finder codeforamerica.org/geeks/civicissues @fureigh
  32. 32. @fureigh
  33. 33. @fureigh
  34. 34. @fureigh
  35. 35. @fureigh
  36. 36. I can haz issue? @fureigh
  37. 37. @fureigh
  38. 38. Code contributions are not the only contributions. @fureigh
  39. 39. Back to finding issues. @fureigh
  40. 40. Cloud.gov Analytics.USA.gov College Scorecard Every Kid in a Park Identity Management beta.FEC.gov + FEC’s first API Some 18F projects
  41. 41. So many technical options!
  42. 42. The U.S. Web Design Standards PART ZERO
  43. 43. We're designing for 320 million people The population of the United States
  44. 44. This is Joanne.
  45. 45. 1/ But wait — there’s more PART ONE
  46. 46. 1 2 3 $86 billion is spent a year on federal IT projects 94% of federal IT projects are over budget and behind schedule Just to show how this scales... Why this matters 40% of them never see the light of day — they’re scrapped or abandoned
  47. 47. 2/ Why it’s like this PART TWO
  48. 48. Buying IT is not the same as buying pencils and tanks. Our work happens in silos. Bureaucracy over human needs. Forced to comply with outdated regulations.
  49. 49. It became clear that if we wanted to help Joanne, we had to help the people making these digital services.
  50. 50. 1 2 3 The question in front of us became: Is it possible to create a shared set of tools to provide consistent, effective, and easy-to-use government websites? Could we build easy-to- use tools that serve the public’s need? We think this is possible.
  51. 51. Here are the principles that guided us: Flexible: Create a design system for wide use across agencies and brands Accessible: They must work for everybody, regardless of abilities Reusable: Save time and money – there’s no need to reinvent the wheel Open source: Increase knowledge, shared understanding, and practices across projects
  52. 52. A consistent look and feel with common design elements will feel familiar, trustworthy, and secure.
  53. 53. We built the Standards to be lightweight ● Just HTML, CSS, and JavaScript ● Sass preprocessor language ○ Sass add-ons (thoughtbot’s Bourbon and Neat) ● Component-based design
  54. 54. 3/ Accessibility PART THREE
  55. 55. Accessible out of the box ● Start with HTML5 with ARIA ● Testing Section 508 features ● Developed with WCAG 2.0 AA in mind
  56. 56. 4/ In the wild PART FOUR
  57. 57. “I like the clean format. I like that it shows me all the things I need to fill out all at once. I can read it fine. Sometimes I need my reading glasses because of the colors, but this is good because it's got sharp contrast.”
  58. 58. Good civic design is about access It means that people can get the right help, sooner, with less stress.
  59. 59. 5/ Open source from day one PART FIVE
  60. 60. We <3 our contributors
  61. 61. What if I want to work on something else? @fureigh
  62. 62. Start your own band. @fureigh
  63. 63. @fureigh
  64. 64. 18F.gsa.gov join.18F.gov @fureigh
  65. 65. codeforamerica.org/geeks/civicissues github.com/18F/web-design-standards/issues github.com/18F @fureigh

×