diff --git a/Gemfile.lock b/Gemfile.lock index f8186a86..b1fbf4a4 100755 --- a/Gemfile.lock +++ b/Gemfile.lock @@ -1,33 +1,33 @@ GEM remote: https://rubygems.org/ specs: - activesupport (4.2.10) - i18n (~> 0.7) + activesupport (5.2.3) + concurrent-ruby (~> 1.0, >= 1.0.2) + i18n (>= 0.7, < 2) minitest (~> 5.1) - thread_safe (~> 0.3, >= 0.3.4) tzinfo (~> 1.1) - addressable (2.5.2) + addressable (2.6.0) public_suffix (>= 2.0.2, < 4.0) colorator (1.1.0) - concurrent-ruby (1.0.5) + concurrent-ruby (1.1.5) em-websocket (0.5.1) eventmachine (>= 0.12.9) http_parser.rb (~> 0.6.0) - eventmachine (1.2.5) - eventmachine (1.2.5-x64-mingw32) - ffi (1.9.18) - ffi (1.9.18-x64-mingw32) + eventmachine (1.2.7) + eventmachine (1.2.7-x64-mingw32) + ffi (1.11.1) + ffi (1.11.1-x64-mingw32) forwardable-extended (2.6.0) - gemoji (3.0.0) + gemoji (3.0.1) hash-joiner (0.0.7) safe_yaml - html-pipeline (2.7.1) + html-pipeline (2.11.1) activesupport (>= 2) nokogiri (>= 1.4) http_parser.rb (0.6.0) - i18n (0.9.1) + i18n (0.9.5) concurrent-ruby (~> 1.0) - jekyll (3.7.0) + jekyll (3.8.6) addressable (~> 2.4) colorator (~> 1.0) em-websocket (~> 0.5) @@ -40,55 +40,53 @@ GEM pathutil (~> 0.9) rouge (>= 1.7, < 4) safe_yaml (~> 1.0) - jekyll-last-modified-at (1.0.1) - jekyll (~> 3.3) + jekyll-last-modified-at (1.1.0) + jekyll (>= 3.7, < 5.0) posix-spawn (~> 0.3.9) - jekyll-mentions (1.2.0) - activesupport (~> 4.0) + jekyll-mentions (1.5.1) html-pipeline (~> 2.3) - jekyll (~> 3.0) - jekyll-redirect-from (0.13.0) - jekyll (~> 3.3) - jekyll-sass-converter (1.5.1) + jekyll (>= 3.7, < 5.0) + jekyll-redirect-from (0.15.0) + jekyll (>= 3.3, < 5.0) + jekyll-sass-converter (1.5.2) sass (~> 3.4) - jekyll-watch (2.0.0) + jekyll-watch (2.2.1) listen (~> 3.0) - jemoji (0.9.0) - activesupport (~> 4.0, >= 4.2.9) + jemoji (0.11.0) gemoji (~> 3.0) html-pipeline (~> 2.2) - jekyll (~> 3.0) - kramdown (1.16.2) - liquid (4.0.0) + jekyll (>= 3.0, < 5.0) + kramdown (1.17.0) + liquid (4.0.3) listen (3.1.5) rb-fsevent (~> 0.9, >= 0.9.4) rb-inotify (~> 0.9, >= 0.9.7) ruby_dep (~> 1.2) mercenary (0.3.6) - mini_portile2 (2.3.0) - minitest (5.11.1) - nokogiri (1.8.1) - mini_portile2 (~> 2.3.0) - nokogiri (1.8.1-x64-mingw32) - mini_portile2 (~> 2.3.0) - pathutil (0.16.1) + mini_portile2 (2.4.0) + minitest (5.11.3) + nokogiri (1.10.3) + mini_portile2 (~> 2.4.0) + nokogiri (1.10.3-x64-mingw32) + mini_portile2 (~> 2.4.0) + pathutil (0.16.2) forwardable-extended (~> 2.6) posix-spawn (0.3.13) - public_suffix (3.0.1) - rb-fsevent (0.10.2) - rb-inotify (0.9.10) - ffi (>= 0.5.0, < 2) - redcarpet (3.4.0) - rouge (3.1.0) + public_suffix (3.1.1) + rb-fsevent (0.10.3) + rb-inotify (0.10.0) + ffi (~> 1.0) + redcarpet (3.5.0) + rouge (3.7.0) ruby_dep (1.5.0) - safe_yaml (1.0.4) - sass (3.5.5) + safe_yaml (1.0.5) + sass (3.7.4) sass-listen (~> 4.0.0) sass-listen (4.0.0) rb-fsevent (~> 0.9, >= 0.9.4) rb-inotify (~> 0.9, >= 0.9.7) thread_safe (0.3.6) - tzinfo (1.2.4) + tzinfo (1.2.5) thread_safe (~> 0.1) PLATFORMS @@ -106,4 +104,4 @@ DEPENDENCIES rouge BUNDLED WITH - 1.16.2 + 1.17.3 diff --git a/PRODUCT_TEAM.md b/PRODUCT_TEAM.md new file mode 100644 index 00000000..3f7de883 --- /dev/null +++ b/PRODUCT_TEAM.md @@ -0,0 +1,21 @@ +# 18F Methods Product Team + +As a member of the 18F Methods Product Team, you will be expected to spend an average of two hours a week working towards the following objectives: + +## Objective A: Maintain the 18F Methods + +- Collaboratively set an achievable, year-long vision for the 18F Methods +- Identify, prioritize, and address short-term goals and known issues +- Establish a decision-making process(es) for merging contributions into the Methods + +## Objective B: Ensure the 18F Methods support and reflect 18F’s current practices + +- Collect data around the value 18F Methods provides across the organization +- Revise and augment the Methods as needed, to keep in sync with 18F’s practice +- Add to and maintain the connections between the Methods and other content (such as other guides and resources produced by 18F or issued by the government) + +## Objective C: Ensure usability and encourage adoption of the 18F Methods + +- In collaboration with TTS Outreach, promote the methods outside of 18F +- Offer periodic support and solicit input for methods on venues like the UX-COP Mailing list +- Optional: Conduct research around the use of the Methods in order to increase usability. diff --git a/README.md b/README.md index 7ddc43f3..6dfa225d 100755 --- a/README.md +++ b/README.md @@ -1,14 +1,18 @@ The CDS Method Cards (“CDS Methods”) describe how the CDS puts human-centered design into practice. While this is primarily maintained as an internal resource, we hope it can help *everyone* adopt the methods of human-centered design. It has been forked from 18F's method cards, and contains modifications meant to better fit the City of Chicago. Any organization or municipality is free to use this as a base for their own work, as it is under the [CC0 1.0 License](https://creativecommons.org/publicdomain/zero/1.0/). -### Why methods? +## Why methods? In order to function well within cross-functional teams, designers need to know a few things: which methods they might choose from, why one particular method makes more sense than another at any given moment, and, once they’ve picked a method, how to actually execute it. 18F Methods collects this essential information as a series of cards. In practice, we’ve found the Methods can provide folks with a gateway into our work and build internal alignment around a shared vocabulary. ## Getting started + ### Reading the Methods online -You’re presently looking at the Methods’ GitHub (code) repository. Please [visit our homepage](https://methods.18f.gov) to read the Methods online. + +You’re presently looking at the Methods’ GitHub (code) repository. Please [visit our homepage](https://methods.chicagodesignsystem.org) to read the Methods online. + ### Printing the Methods -To print a copy of the Methods for offline use, simply visit the [Methods homepage](https://methods.18f.gov) and select `file → print…` from your web browser. +To print a copy of the Methods for offline use, visit the [Methods print page](https://methods.chicagodesignsystem.org/print/). You may need to select `file → print…` from your web browser. + ### Running the Methods website on your local machine You will need [Ruby](https://www.ruby-lang.org) ( > version 2.1.5 ). You may consider using a Ruby version manager such as [rbenv](https://github.com/sstephenson/rbenv) or [rvm](https://rvm.io/) to help ensure that Ruby version upgrades don’t mean all your [gems](https://rubygems.org/) will need to be rebuilt. @@ -32,8 +36,9 @@ jekyll serve ``` You should be able to see the site at: `http://localhost:4000/` + ### Contributing to the Methods -For more information on contributing to the Methods (or even making a suggestion), see [CONTRIBUTING.md](https://github.com/chicago/design-methods/blob/staging/CONTRIBUTING.md). +For more information on contributing to the Methods (or even making a suggestion), see [CONTRIBUTING.md](https://github.com/chicago/design-methods/blob/master/CONTRIBUTING.md). ## CDS contributors - Design Director: Jason Kunesh @@ -44,18 +49,7 @@ For more information on contributing to the Methods (or even making a suggestion - Product owner: Eric Ronne - Designer (researcher): Andrew Maier - Designer (front-end developer): Scott Weber -- Melissa Braxton -- Jeremy Canfield -- Erica Deahl -- Carolyn Dew -- Andre Francisco -- James Hupp -- Nicky Krause -- Colin MacArthur -- Brad Nunnally -- Jennifer Thibault -- Russ Unger -- Victor Zapanta + ## Public domain diff --git a/_config.yml b/_config.yml index 7e48446c..2c0bb0a1 100755 --- a/_config.yml +++ b/_config.yml @@ -18,9 +18,6 @@ sass: style: compressed collections: - pages: - output: true - permalink: /:path/ methods: output: true permalink: /:path/ diff --git a/_data/categories.yml b/_data/categories.yml new file mode 100644 index 00000000..b91739b5 --- /dev/null +++ b/_data/categories.yml @@ -0,0 +1,46 @@ +- category_name: Discover + category_description: Build a greater understanding of your problem and the people it impacts. + category_info: Use the Discover Methods to build context for the problem you’re investigating. Get to know your potential users better and understand your stakeholders’ main concerns. The work you do during this phase will inform everything that follows, so take your time. + methods: + - Cognitive walkthrough + - Contextual inquiry + - Design studio + - Dot voting + - KJ method + - Stakeholder and user interviews + +- category_name: Decide + category_description: Elaborate on research from your Discovery phase. + category_info: The Decide Methods help you derive insights from the information gathered during the Discovery phase. You’ll validate initial assumptions, develop a deeper understanding of workflows and processes, and develop design hypotheses. + methods: + - Affinity diagramming + - Comparative analysis + - Journey mapping + - Personas + - Task flow analysis + - User scenarios + +- category_name: Make + category_description: Create a testable solution. + category_info: Once you’ve learned more about your users’ expectations, use the Make Methods to create testable designs. Sketching, wireframing, and prototyping will help you ensure your product reflects your users’ needs. + methods: + - Design pattern library + - Prototyping + - Wireframing + +- category_name: Validate + category_description: Test a design hypothesis. + category_info: Testing (and re-testing) your designs with users will help you build the best possible product. Our Validate Methods cover varied testing scenarios and potential user groups. + methods: + - Card sorting + - Multivariate testing + - Usability testing + - Visual preference testing + +- category_name: Fundamentals + category_description: Foundational methods for practicing design research. + category_info: Our Fundamentals Methods, which combine government-specific protocols and industry best practices, lay the groundwork for successful research, no matter what you’re testing. For best results, review them before you start recruiting. + methods: + - Incentives + - Privacy + - Recruiting diff --git a/_includes/head.html b/_includes/head.html index b4542658..2079f73c 100755 --- a/_includes/head.html +++ b/_includes/head.html @@ -2,8 +2,8 @@ - {% if page.title %}{{ page.title }}{% else %}{{ site.title }}{% endif %} - CDS Method Cards + @@ -32,14 +32,22 @@ + {% if page.layout == "page" %} - {% else %} - + {% endif %} diff --git a/_includes/header-18f-example.html b/_includes/header-18f-example.html deleted file mode 100644 index c4fa8778..00000000 --- a/_includes/header-18f-example.html +++ /dev/null @@ -1 +0,0 @@ -

Example from 18F

diff --git a/_includes/header.html b/_includes/header.html index e2fbe483..2bdc27d5 100755 --- a/_includes/header.html +++ b/_includes/header.html @@ -5,23 +5,23 @@ Skip to main content -
+