diff --git a/.bundle/config b/.bundle/config
deleted file mode 100644
index 2fbf0ffd..00000000
--- a/.bundle/config
+++ /dev/null
@@ -1 +0,0 @@
---- {}
diff --git a/.github/ISSUE_TEMPLATE/18f-team--basic-issue-tracking-template.md b/.github/ISSUE_TEMPLATE/18f-team--basic-issue-tracking-template.md
index 7d5b442c..95cf6f6b 100644
--- a/.github/ISSUE_TEMPLATE/18f-team--basic-issue-tracking-template.md
+++ b/.github/ISSUE_TEMPLATE/18f-team--basic-issue-tracking-template.md
@@ -12,6 +12,17 @@ Before you submit your new issue, add labels so that we know which guide/site th
 While it might seem redundant, we have one team that manages issues across multiple products, and these labels help us keep our wires straight! 
 _______________________________________________________
 
+**Point of contact**
+
+
+**Timeline**
+Does this need to happen in the next two weeks?
+
+- [ ] Yes
+- [ ] No
+
+**How much time do you anticipate this work taking?**
+
 
 **Background**
 _What should we consider when addressing this issue?_
diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md
new file mode 100644
index 00000000..d24fa4c7
--- /dev/null
+++ b/.github/PULL_REQUEST_TEMPLATE.md
@@ -0,0 +1,35 @@
+## Description of changes
+
+> Describe what this pull request is changing. Try to use plain language as much
+> as possible to help teammates understand what they are reviewing.
+
+## Known issues
+
+> If this pull request introduces anything that needs to be addressed later,
+> note it here. Some examples might be if you introduced a new link that fails
+> tests but will work when another pull request is merged; you created a new
+> method placeholder but it does not yet have content; or your change breaks
+> something else that will be removed later. If you create any issues to
+> address issues created by this pull request, this is a good place to list
+> them! You can delete this section if the PR does not introduce any new issues.
+
+## Related issues
+
+> If this pull request is associated with any other issues or pull requests,
+> lis them here. If this PR *closes* an issue, list it as `closes #issue` so
+> the issue will automatically be closed when the PR is merged. If there are no
+> related issues or PRs, you can delete this section.
+
+- 
+- 
+
+## Reviewers:
+
+> In addition to assigning reviewers in the GitHub interface, please also list
+> who you would like a review from here and, if applicable, what kind of review
+> you would like from them. For example, you might ask one person to review
+> content while someone else reviews visual layout.
+
+- [ ] @username: please review content
+- [ ]
+- [ ]
diff --git a/.github/workflows/sync_milestones.yml b/.github/workflows/sync_milestones.yml
new file mode 100644
index 00000000..b8e4c553
--- /dev/null
+++ b/.github/workflows/sync_milestones.yml
@@ -0,0 +1,67 @@
+name: sync milestones
+
+on:
+  milestone:
+    types: [created]
+
+jobs:
+  synchronize:
+    name: synchronize milestones
+    runs-on: ubuntu-latest
+
+    steps:
+      # Rather than use a personal access token to interact with the project, we
+      # can use this GitHub App. There's an API for exchanging app credentials
+      # for a short-term token, and we use that API here.
+      - name: get token
+        uses: tibdex/github-app-token@v1
+        id: app_token
+        with:
+          app_id: ${{ secrets.PROJECT_APP_ID }}
+          installation_id: ${{ secrets.PROJECT_INSTALLATION_ID }}
+          private_key: ${{ secrets.PROJECT_PRIVATE_KEY }}
+      
+      - name: sync milestones
+        uses: actions/github-script@v6
+        with:
+          github-token: ${{ steps.app_token.outputs.token }}
+          script: |
+            // Get the metadata about this repo from the workflow context
+            const { owner, repo } = context.repo;
+            // And remove this repo from the list of repos to sync to. No need
+            // to sync myself with myself.
+            const syncTargets = ["methods", "ux-guide"].filter((r) => r !== repo);
+
+            // Get a list of this repo's milestones
+            const myMilestones = await github
+              .paginate(`GET /repos/${owner}/${repo}/milestones`)
+              .then((milestones) =>
+                milestones.map(({ title, description, due_on, state }) => ({
+                  title,
+                  description,
+                  due_on,
+                  state,
+                }))
+              );
+
+            // Now for each sync target repo...
+            for await (const target of syncTargets) {
+              // Get the titles of their milestones, which we'll use to filter
+              // down to which milestones to synchronize
+              const theirMilestones = new Set(
+                await github
+                  .paginate(`GET /repos/${owner}/${target}/milestones`)
+                  .then((milestones) => milestones.map(({ title }) => title))
+              );
+
+              for await (const milestone of myMilestones) {
+                // If a milestone with this title does NOT exist in the target
+                // repo, then we should create one.
+                if (!theirMilestones.has(milestone.title)) {
+                  // Expand the milestone so we push the title, description, due
+                  // date, and status (open/closed) all at once.
+                  await github.rest.issues.createMilestone({ owner, repo: target, ...milestone });
+                }
+              }
+            }
+
diff --git a/.gitignore b/.gitignore
index d21578bc..69718c3c 100644
--- a/.gitignore
+++ b/.gitignore
@@ -2,5 +2,5 @@ _site/
 .sass-cache/
 .DS_store
 .*.swp
-.ruby-version
 .jekyll-cache/
+.bundle
diff --git a/.jekyll-metadata b/.jekyll-metadata
new file mode 100644
index 00000000..ca152c2f
Binary files /dev/null and b/.jekyll-metadata differ
diff --git a/.ruby-version b/.ruby-version
new file mode 100644
index 00000000..a603bb50
--- /dev/null
+++ b/.ruby-version
@@ -0,0 +1 @@
+2.7.5
diff --git a/.travis.yml b/.travis.yml
deleted file mode 100644
index 36d36c9c..00000000
--- a/.travis.yml
+++ /dev/null
@@ -1,19 +0,0 @@
-language: ruby
-rvm:
-- 2.1
-script: bundle exec jekyll build --config _config.yml,_config-production.yml ./_site
-deploy:
-  provider: cloudfoundry
-  edge: true
-  api: https://api.cloud.gov
-  organization: 18f
-  space: methods
-  username: 18f-methods_deployer
-  password:
-    secure: ZuX5eljwlotWWq+68vzO9yDBObPPf9kv8TN4c/BwNxTONCAhOYNnhrJPvGk7WIdQ1FNd8kYsBmRJeOgf6TZa4W/8yTHqkKAgGMTk5t19A7zU1WUHa+KXgsSOlQT+/00LSMZVvdNtpc1k1Mk5N0a0GJSVVLIWpFscXsN2O5LZTuc=
-  on:
-    repo: 18F/methods
-    branch: master
-branches:
-  only:
-  - master
diff --git a/Gemfile b/Gemfile
index b5bc44f1..f2f7f53e 100644
--- a/Gemfile
+++ b/Gemfile
@@ -1,13 +1,12 @@
 source 'https://rubygems.org'
 
-gem 'jekyll', '>= 4.2.0'
-gem 'redcarpet'
-gem 'rouge'
-gem 'hash-joiner'
-gem 'jekyll-last-modified-at', '>= 1.3.0'
-gem 'jemoji', '>= 0.12.0'
-gem 'jekyll-mentions', '>= 1.6.0'
-gem 'jekyll-redirect-from', '>= 0.16.0'
-gem 'jekyll-sitemap', '>= 1.4.0'
-gem 'jekyll-autoprefixer'
-gem 'jekyll-liquify'
\ No newline at end of file
+gem 'jekyll', '4.2.2'
+
+group :jekyll_plugins do
+  gem 'jekyll-last-modified-at', '>= 1.3.0'
+  gem 'jemoji', '>= 0.12.0'
+  gem 'jekyll-mentions', '>= 1.6.0'
+  gem 'jekyll-redirect-from', '>= 0.16.0'
+  gem 'jekyll-sitemap', '>= 1.4.0'
+  gem 'jekyll-liquify'
+end
\ No newline at end of file
diff --git a/Gemfile.lock b/Gemfile.lock
index 232b68c5..97898f04 100644
--- a/Gemfile.lock
+++ b/Gemfile.lock
@@ -1,28 +1,23 @@
 GEM
   remote: https://rubygems.org/
   specs:
-    activesupport (7.0.3.1)
+    activesupport (7.0.4.3)
       concurrent-ruby (~> 1.0, >= 1.0.2)
       i18n (>= 1.6, < 2)
       minitest (>= 5.1)
       tzinfo (~> 2.0)
-    addressable (2.8.0)
-      public_suffix (>= 2.0.2, < 5.0)
-    autoprefixer-rails (9.8.6.5)
-      execjs
+    addressable (2.8.1)
+      public_suffix (>= 2.0.2, < 6.0)
     colorator (1.1.0)
-    concurrent-ruby (1.1.10)
+    concurrent-ruby (1.2.2)
     em-websocket (0.5.3)
       eventmachine (>= 0.12.9)
       http_parser.rb (~> 0)
     eventmachine (1.2.7)
-    execjs (2.7.0)
     ffi (1.15.5)
     forwardable-extended (2.6.0)
-    gemoji (3.0.1)
-    hash-joiner (0.0.7)
-      safe_yaml
-    html-pipeline (2.14.2)
+    gemoji (4.0.1)
+    html-pipeline (2.14.3)
       activesupport (>= 2)
       nokogiri (>= 1.4)
     http_parser.rb (0.8.0)
@@ -43,8 +38,6 @@ GEM
       rouge (~> 3.0)
       safe_yaml (~> 1.0)
       terminal-table (~> 2.0)
-    jekyll-autoprefixer (1.0.2)
-      autoprefixer-rails (~> 9.3)
     jekyll-last-modified-at (1.3.0)
       jekyll (>= 3.7, < 5.0)
       posix-spawn (~> 0.3.9)
@@ -62,33 +55,33 @@ GEM
       jekyll (>= 3.7, < 5.0)
     jekyll-watch (2.2.1)
       listen (~> 3.0)
-    jemoji (0.12.0)
-      gemoji (~> 3.0)
+    jemoji (0.13.0)
+      gemoji (>= 3, < 5)
       html-pipeline (~> 2.2)
       jekyll (>= 3.0, < 5.0)
     kramdown (2.4.0)
       rexml
     kramdown-parser-gfm (1.1.0)
       kramdown (~> 2.0)
-    liquid (4.0.3)
-    listen (3.7.1)
+    liquid (4.0.4)
+    listen (3.8.0)
       rb-fsevent (~> 0.10, >= 0.10.3)
       rb-inotify (~> 0.9, >= 0.9.10)
     mercenary (0.4.0)
-    mini_portile2 (2.8.0)
-    minitest (5.16.2)
-    nokogiri (1.13.8)
+    mini_portile2 (2.8.1)
+    minitest (5.18.0)
+    nokogiri (1.14.3)
       mini_portile2 (~> 2.8.0)
       racc (~> 1.4)
     pathutil (0.16.2)
       forwardable-extended (~> 2.6)
     posix-spawn (0.3.15)
-    public_suffix (4.0.7)
-    racc (1.6.0)
-    rb-fsevent (0.11.1)
+    public_suffix (5.0.1)
+    racc (1.6.2)
+    rb-fsevent (0.11.2)
     rb-inotify (0.10.1)
       ffi (~> 1.0)
-    redcarpet (3.5.1)
+    redcarpet (3.6.0)
     rexml (3.2.5)
     rouge (3.30.0)
     safe_yaml (1.0.5)
@@ -96,7 +89,7 @@ GEM
       ffi (~> 1.9)
     terminal-table (2.0.0)
       unicode-display_width (~> 1.1, >= 1.1.1)
-    tzinfo (2.0.5)
+    tzinfo (2.0.6)
       concurrent-ruby (~> 1.0)
     unicode-display_width (1.8.0)
 
@@ -104,17 +97,13 @@ PLATFORMS
   ruby
 
 DEPENDENCIES
-  hash-joiner
-  jekyll (>= 4.2.0)
-  jekyll-autoprefixer
+  jekyll (= 4.2.2)
   jekyll-last-modified-at (>= 1.3.0)
   jekyll-liquify
   jekyll-mentions (>= 1.6.0)
   jekyll-redirect-from (>= 0.16.0)
   jekyll-sitemap (>= 1.4.0)
   jemoji (>= 0.12.0)
-  redcarpet
-  rouge
 
 BUNDLED WITH
    2.1.4
diff --git a/README.md b/README.md
index 138e627d..676389d9 100755
--- a/README.md
+++ b/README.md
@@ -4,11 +4,11 @@ The 18F Methods were created to describe how 18F puts human-centered design into
 
 ## 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.
+In order to function well within cross-functional teams, designers and other contributors 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.
 
 ### Specific to 18F, specific to the federal government
 
-It’s important to note that the 18F Methods are designed to account for two things that may not otherwise concern a more generic collection of design methods. First, these methods directly reflect and support 18F’s human-centered work. (They are also continuously updated in a human-centered way — how meta!) Second, 18F Methods are designed to keep federal employees on the happy side of the law. This collection specifically includes helpful information on topics for which designers working in the federal government may need clarification, such as privacy and the [Paperwork Reduction Act](pra.digital.gov).
+It’s important to note that the 18F Methods are designed to account for two things that may not otherwise concern a more generic collection of design methods. First, these methods directly reflect and support 18F’s human-centered work. (They are also continuously updated in a human-centered way — how meta!) Second, 18F Methods are designed to keep federal employees on the happy side of the law. This collection specifically includes helpful information which designers working in the federal government may need, such as privacy and the [Paperwork Reduction Act](pra.digital.gov).
 
 ## Getting started
 
@@ -24,6 +24,8 @@ For more information on contributing to the Methods (or even making a suggestion
 
 Learn more about our goals and the way we work in our [wiki](https://github.com/18F/methods/wiki). 
 
+## Development
+
 ### Running the Methods website on your local machine
 
 #### Using Docker (recommended)
@@ -56,19 +58,24 @@ $ jekyll serve
 
 You should be able to see the site at: `http://localhost:4000/`
 
-## Current team
+### Deploying
+
+The Methods guide uses a webhook to deploy to Cloud.gov pages. When viewing a pull request, expand "Show all checks." If pages/build is complete, click "details" for a link to a preview for that branch.
+
+## Current product owner
+- Melissa Braxton
+
+
+## Past contributors
 
 - Tiffany Andrews
 - Carly Jugler
 - Megan Reed
 - Peter Rowland
 - Julie Strothman
-
-## Past contributors
-
+- Anne Petersen
 - Amirah Aziz
 - Ana Monroe
-- Melissa Braxton
 - Jeremy Canfield
 - Elisa Chen
 - Erica Deahl
diff --git a/_config.yml b/_config.yml
index c359a319..ec75db4e 100755
--- a/_config.yml
+++ b/_config.yml
@@ -43,7 +43,6 @@ plugins:
   - jekyll-mentions
   - jekyll-redirect-from
   - jekyll-sitemap
-  - jekyll-autoprefixer
   - jekyll-liquify
 
 google_analytics_ua: UA-48605964-19
diff --git a/_data/categories.yml b/_data/categories.yml
index ed260b99..6368403c 100644
--- a/_data/categories.yml
+++ b/_data/categories.yml
@@ -12,6 +12,7 @@
     - KJ method
     - Lean coffee
     - Stakeholder and user interviews
+    - Stakeholder influence mapping
 
 - category_name: Decide
   category_description: Elaborate on research from your Discovery phase.
@@ -26,6 +27,7 @@
     - Journey mapping
     - Mental modeling
     - Personas
+    - Service blueprint
     - Site mapping
     - Storyboarding
     - Style tiles
diff --git a/_includes/footer.html b/_includes/footer.html
index 2f072ebe..c2a553ab 100755
--- a/_includes/footer.html
+++ b/_includes/footer.html
@@ -5,8 +5,8 @@
     </div>
     <div class="usa-footer__primary-section site-footer">
         <div class="usa-footer__primary-container">
-            <p>This project is maintained by <a href="https://18f.gsa.gov" class="usa-link">18F</a>. To share your
-                feedback with us, click the <strong>Get in touch</strong> button or open an issue or pull request on our
+            <p>This project is maintained by <a href="https://18f.gsa.gov" class="usa-link">18F</a>. To get in touch with us, head to the <a href="https://18f.gsa.gov/contact/" class="usa-link">18F contact page.</a> 
+To share your feedback about the Methods site, click the <strong>Provide feedback<strong> button or open an issue or pull request on our
                 <a href="https://github.com/18F/methods" class="usa-link">GitHub repository.</a></p>
         </div>
     </div>
@@ -15,9 +15,16 @@
 
 <a id="fba-button" class="fixed-tab-button" href="https://touchpoints.app.cloud.gov/touchpoints/d028f982/submit"
     target="_blank">
-    Get in touch
+    Provide feedback
 </a>
 
+<!--Add SVG for header links-->
+<div style="display: none">
+  <svg xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink">
+    <symbol viewBox="0 0 24 24" id="svg-link" xmlns="http://www.w3.org/2000/svg"><path d="M3.9 12c0-1.71 1.39-3.1 3.1-3.1h4V7H7c-2.76 0-5 2.24-5 5s2.24 5 5 5h4v-1.9H7c-1.71 0-3.1-1.39-3.1-3.1zM8 13h8v-2H8v2zm9-6h-4v1.9h4c1.71 0 3.1 1.39 3.1 3.1s-1.39 3.1-3.1 3.1h-4V17h4c2.76 0 5-2.24 5-5s-2.24-5-5-5z"></path></symbol>
+  </svg>
+</div>
+
 <!--<script src="{{site.baseurl}}/assets/js/site.js"/>-->
 <!-- Digital Analytics Program roll-up, see https://analytics.usa.gov for data -->
 <script id="_fed_an_ua_tag"
diff --git a/_includes/header.html b/_includes/header.html
index 2494ba4b..cc72c8bb 100755
--- a/_includes/header.html
+++ b/_includes/header.html
@@ -12,7 +12,7 @@
     <div class="usa-navbar">
       <div class="usa-logo" id="logo">
         <em class="usa-logo__text">
-          <a href="{{site.baseurl}}/" accesskey="1" title="Home" aria-label="Home">  <img src="{{site.baseurl}}/images/18F.svg" alt="18F logo with white text on a black square background" width="72"> Methods</a>
+          <a href="{{site.baseurl}}/" title="Home" aria-label="Home">  <img src="{{site.baseurl}}/images/18F.svg" alt="18F logo with white text on a black square background" width="72"> Methods</a>
         </em>
       </div>
       <button class="usa-menu-btn">Menu</button>
diff --git a/_layouts/card.html b/_layouts/card.html
index 1c959489..ba6d2b63 100755
--- a/_layouts/card.html
+++ b/_layouts/card.html
@@ -4,11 +4,11 @@
   <body class="layout--card category--{{page.category | downcase }}">
     {% include category-setup.html %} {% include header.html %}
     <main id="main" role="main">
-      <section class="category category--{{page.category | downcase }} usa-section usa-prose" id="{{page.category | downcase }}">
-        <header class="category--header">
+      <section class="category category--{{page.category | downcase }} usa-section usa-prose">
+        <header class="category--header" aria-labelledby="{{method_category.title | downcase }}">
           <div class="grid-container">
             {% assign method_category = site.pages | where: "title", page.category | first %}
-            <h1 class="category--title">{{method_category.title | capitalize }}</h1>
+            <span class="category--title" id="{{method_category.title | downcase }}">{{method_category.title | capitalize }}</span>
             <p class="category--subtitle">{{method_category.description}}</p>
           </div>
         </header>
diff --git a/_layouts/page-full-width.html b/_layouts/page-full-width.html
new file mode 100644
index 00000000..e2eef2b6
--- /dev/null
+++ b/_layouts/page-full-width.html
@@ -0,0 +1,12 @@
+<!DOCTYPE html>
+<html lang='en'>
+  {% include head.html %}
+  <body class="layout--page-full-width layout--{{ page.title | slugify }}">
+    {% include category-setup.html %}
+    {% include header.html %}
+    <main id="main" role="main" class="usa-prose">
+      {{ content }}
+    </main>
+    {% include footer.html %}
+  </body>
+</html>
\ No newline at end of file
diff --git a/_methods/heuristic-evaluation.md b/_methods/heuristic-evaluation.md
index afbc9450..de8815c9 100644
--- a/_methods/heuristic-evaluation.md
+++ b/_methods/heuristic-evaluation.md
@@ -19,7 +19,7 @@ timeRequired: 1–2 hours
 1. Ask each person to individually create a list of "heuristics" or general usability best practices. Examples of heuristics from Nielsen's "10 Usability Heuristics for User Interface Design" include:
     1.  The website should keep users informed about what is going on, through appropriate feedback within reasonable time.
     1.  The system should speak the user's language, with words, phrases and concepts familiar to the user, rather than system-oriented terms.
-1. Consider what hazards the service or product might hold for its users, and nclude heuristics to evaluate whether the site protects against possible harms.
+1. Consider what hazards the service or product might hold for its users, and include heuristics to evaluate whether the site protects against possible harms.
 1. Ask each person to evaluate the website against their list and write down possible problems.
 1. After individual evaluations, gather people to discuss what they found and prioritize potential problems.
 
diff --git a/_methods/personas.md b/_methods/personas.md
index ae3b098f..4f041bec 100755
--- a/_methods/personas.md
+++ b/_methods/personas.md
@@ -23,7 +23,7 @@ timeRequired: 2–3 hours
 
 ## Example
 
-- <a href="https://github.com/18F/federalist-design/wiki/Personas" class="usa-link">Personas for Federalist — 18F GitHub</a>
+- <a href="https://github.com/18F/federalist-design/wiki/Personas" class="usa-link">Personas for Cloud.gov — 18F GitHub</a>
 
 </section>
 
diff --git a/_methods/privacy.md b/_methods/privacy.md
index c59627b0..08e9d048 100755
--- a/_methods/privacy.md
+++ b/_methods/privacy.md
@@ -30,7 +30,7 @@ timeRequired: N/A
 
 ## Considerations for use in government
 
-The government's use of information about people is subject to a number of laws and policies, including: <a href="https://www.justice.gov/opcl/overview-privacy-act-1974-2015-edition" class="usa-link">the Privacy Act of 1974</a>, the Federal Information Security Management Act of 2002, and the eGovernment Act of 2002.
+The government's use of information about people is subject to a number of laws and policies, including: <a href="https://www.justice.gov/opcl/overview-privacy-act-1974-2020-edition" class="usa-link">the Privacy Act of 1974</a>, the Federal Information Security Management Act of 2002, and the eGovernment Act of 2002.
 
 Conduct a Privacy Threshold Analysis in collaboration your agency's privacy office whenever a design calls for the creation of a new data store (for example, a database).
 
diff --git a/_methods/service-blueprint.md b/_methods/service-blueprint.md
new file mode 100644
index 00000000..c1987e11
--- /dev/null
+++ b/_methods/service-blueprint.md
@@ -0,0 +1,45 @@
+---
+layout: card
+title: Service blueprint
+permalink: /decide/service-blueprint/
+redirect_from:
+  - /service-blueprint/
+description: |-
+  A visual representation of the start-to-finish experience of both using and supporting the delivery of a service, including staff interactions and user experience.
+category: Decide
+what: |-
+  A visual representation of the start-to-finish experience of both using and supporting the delivery of a service, including staff interactions and user experience.
+why: |-
+  To clarify relationships between intertwined systems and processes. By communicating the full complexity of a service, service blueprints help teams find opportunities for improvement.
+timeRequired: 4-12 hours
+governmentConsiderations: No PRA implications. No information is collected directly from members of the public.
+
+---
+
+## How to do it
+
+1. Gather information on the service through desk research and  [interviews]({% link _methods/stakeholder-and-user-interviews.md %}) with users, frontline staff, and support staff
+
+1. Create a diagram with four rows:
+- __User steps__: The primary action someone takes when interacting with the service
+- __Frontstage actions__: The online and offline interactions that users have with the service, including people, places where interactions occur, and physical or virtual objects which users interact with, like forms.
+- __Backstage actions__: Activities in the systems and processes that support the frontstage experience, but are not visible to users
+- __Support processes__: Activities executed by the rest of the organization or external partners — such as ongoing data management or software licensing — that don’t fall into the other rows
+
+1. Map the flow of each user interaction through the service. Note critical points and interactions in delivering the service, as well as any opportunities to handle interactions more efficiently or that would result in a better user experience.
+
+<section class="method--section method--section--18f-example" markdown="1" >
+
+## Example from 18F
+
+18F created [this service blueprint of getting a burger]({% link pages/service-blueprint-example.md %}) as an example to illustrate what this could look like
+
+</section>
+
+<section class="method--section method--section--government-considerations" markdown="1" >
+
+## Considerations for use in government
+
+No PRA implications. No information is collected directly from members of the public.
+
+</section>
diff --git a/_methods/stakeholder-influence-mapping b/_methods/stakeholder-influence-mapping
new file mode 100644
index 00000000..39512da7
--- /dev/null
+++ b/_methods/stakeholder-influence-mapping
@@ -0,0 +1,36 @@
+---
+layout: card
+title: Stakeholder influence mapping
+permalink: /discover/stakeholder-influence-mapping/
+redirect_from:
+  - /stakeholder-influence-mapping/
+description: A visual representation of stakeholders — the people who are involved — and their potential influence and impact on a project or service system, in comparison to one another. 
+category: Discover
+what: A visual representation of stakeholders — the people who are involved — and their potential influence and impact on a project or service system, in comparison to one another. 
+why: To uncover and describe power dynamics — the often-unspoken balances of influence and control — that could impact project outcomes; prioritize which stakeholders to engage with and how, and inform a communication and engagement approach. 
+timeRequired: ~1 hour
+governmentConsiderations:
+
+---
+
+## How to do it
+
+1. Gather the team and, ideally, at least one crucial  stakeholder familiar with their organization and how it works from both a technical and an interpersonal point of view. 
+1. If meeting in person, you’ll need sticky notes and a whiteboard; if meeting remotely, use a virtual whiteboard or tools that support online document collaboration, ideally simultaneously. 
+1. Divide the whiteboard into four areas, as a grid. Label the x axis influence and the y axis interest. 
+1. List out stakeholders together. Write down names of people, groups, communities, or organizations that your work may impact, and organize them into the four quadrants based on your understanding of their relative influence and interest. 
+1. Look at each quadrant to sort who to engage with and how:
+    - interested and influential - collaborate with them
+    - either influential or interested - keep them informed
+    - neither influential nor interested - allow them to drive their own involvement
+1. If your map reveals power dynamics that route around policy, consider whether the information poses personal or professional risk to any stakeholders. Avoid possible harm by sharing this map with only the people who need to understand it, and consider the consequences of those you do share with — or share an edited version.
+1. Review and update the map as you understand the situation better.
+
+<section class="method--section method--section--18f-example" markdown="1" >
+
+
+## Considerations for use in government  
+
+No PRA implications. No information is collected from members of the public.
+
+</section>
diff --git a/_methods/usability-testing.md b/_methods/usability-testing.md
old mode 100755
new mode 100644
index 196713d6..5bc3370b
--- a/_methods/usability-testing.md
+++ b/_methods/usability-testing.md
@@ -18,6 +18,7 @@ timeRequired: 30 minutes to 1 hour per test
 1. Recruit users and inform their consent. Provide a way for potential participants to sign up for the test. Pass along to participants an <a href="{{site.baseurl}}/participant-agreement/" class="usa-link">agreement</a> explaining what participation will entail. Clarify any logistical expectations, such as screen sharing, and how you'll share links or files of whatever it is you're testing.
 1. Run the tests. Moderators should verbally confirm with the participant that it’s okay to record the test, ask participants to think outloud, and guide the participant through the session. Observers should contribute to a <a href="{{site.baseurl}}/rolling-issues-log/" class="usa-link">rolling issues log</a> and relay any in-session questions to the moderator, refraining from interrupting the session from the participant's point of view. Engage your team in a <a href="{{site.baseurl}}/interview-debrief/" class="usa-link">post-interview debrief</a> after each test.
 1. Discuss the results. Schedule a collaborative synthesis meeting to discuss issues you observed, and any questions these tests raise concerning user needs. Conclude the meeting by determining how the team will use what it learned in service of future design decisions.
+main
 
 <section class="method--section method--section--18f-example" markdown="1" >
 
@@ -33,11 +34,12 @@ timeRequired: 30 minutes to 1 hour per test
 
 - [Introduction to remote moderated usability testing, part 1: What and why — 18F Blog](https://18f.gsa.gov/2018/11/14/introduction-to-remote-moderated-usability-testing-part-1/)
 - [Introduction to remote moderated usability testing, part 2: How — 18F Blog](https://18f.gsa.gov/2018/11/20/introduction-to-remote-moderated-usability-testing-part-2-how/)
-- [Example design research participant agreement]({{site.baseurl}}/participant-agreement/) / [Ejemplo de acuerdo de participante de investigación de diseño]({{site.baseurl}}/participant-agreement-spanish/) 
-- <a href="{{site.baseurl}}/interview-checklist/" class="usa-link">Example interview checklist</a>
-- <a href="{{site.baseurl}}/usability-test-script/" class="usa-link">Example usability test script</a>
+- [Example design research participant agreement](https://ux-guide.18f.gov/participant-agreement/) / [Ejemplo de acuerdo de participante de investigación de diseño](https://ux-guide.18f.gov/participant-agreement-spanish/) 
+- [Example interview checklist](https://ux-guide.18f.gov/interview-checklist/)
+- [Example usability test guide](https://ux-guide.18f.gov/usability-test-script/)
 - <a href="{{site.baseurl}}/rolling-issues-log/" class="usa-link">Example rolling issues log</a>
-- [Example interview debrief worksheet]({{site.baseurl}}/interview-debrief/)
+- [Example interview debrief worksheet](https://ux-guide.18f.gov/interview-debrief/)
+- [Usability test quality heuristics](https://ux-guide.18f.gov/usability-test-quality-heuristics/)
 
 </section>
 
diff --git a/_plugins/jekyll_get.rb b/_plugins/jekyll_get.rb
old mode 100755
new mode 100644
index c2990f14..60853259
--- a/_plugins/jekyll_get.rb
+++ b/_plugins/jekyll_get.rb
@@ -1,5 +1,4 @@
 require 'json'
-require 'hash-joiner'
 require 'open-uri'
 require 'base64'
 
@@ -21,9 +20,7 @@ def generate(site)
         begin
           target = site.data[name_of_target]
           source = JSON.load(open(d['json']))
-          if target
-            HashJoiner.deep_merge target, source
-          else
+          unless target
             site.data[name_of_target] = source
           end
           encoding = site.data[name_of_target]['encoding']
@@ -46,4 +43,4 @@ def generate(site)
       end
     end
   end
-end
+end
\ No newline at end of file
diff --git a/_sass/_uswds-theme-settings.scss b/_sass/_uswds-theme-settings.scss
new file mode 100644
index 00000000..5997c7c5
--- /dev/null
+++ b/_sass/_uswds-theme-settings.scss
@@ -0,0 +1 @@
+$theme-show-notifications: false;
\ No newline at end of file
diff --git a/_sass/category.scss b/_sass/category.scss
index fb7a1095..a251c638 100755
--- a/_sass/category.scss
+++ b/_sass/category.scss
@@ -5,6 +5,7 @@
     font-size: font-size('heading',12);
     line-height: line-height('sans',3);
     margin: 0;
+    font-weight:bold;
   }
 
   .category--subtitle {
@@ -124,7 +125,7 @@
       font-size: 1.5rem;
       margin-top: 2rem;
     }
-    h2 {
+    h3 {
       font-size: 1.3rem;
       margin-top: 2rem;
     }
diff --git a/_sass/footer.scss b/_sass/footer.scss
index d9854a7b..05fc533f 100755
--- a/_sass/footer.scss
+++ b/_sass/footer.scss
@@ -8,3 +8,27 @@
     padding-left: units(3);
   }
 }
+
+// Styling for heading links
+.usa-icon {
+  height: 1em;
+  width:1em;
+}
+
+.heading-permalink {
+  opacity: 0.2;
+}
+
+.heading-permalink:hover,
+.heading-permalink:focus {
+  opacity: 1;
+}
+
+// Visually hiding elements
+.visually-hidden {
+    position: absolute !important;
+    height: 1px; width: 1px; 
+    overflow: hidden;
+    clip: rect(1px 1px 1px 1px); /* IE6, IE7 */
+    clip: rect(1px, 1px, 1px, 1px);
+}
\ No newline at end of file
diff --git a/_sass/service-blueprint.scss b/_sass/service-blueprint.scss
new file mode 100644
index 00000000..980d8011
--- /dev/null
+++ b/_sass/service-blueprint.scss
@@ -0,0 +1,76 @@
+/* @group .service-blueprint-example */
+
+.service-blueprint caption {
+    caption-side: bottom;
+    font-size: smaller;
+    font-weight: normal;
+    max-width: 960px;
+    padding: 14px;
+}
+
+table.service-blueprint th, table.service-blueprint td {
+    border: none;
+    padding-top: 62px;
+    vertical-align: top;
+}
+
+.service-blueprint tbody td {
+    font-size: 0.7em;
+}
+
+.service-blueprint tbody th {
+    font-size: 0.9em;
+}
+
+.service-blueprint ul {
+    margin-left: 0;
+    padding-inline-start: 10px;
+    word-wrap: break-word;
+}
+
+.service-blueprint img {
+    display: block;
+    margin-bottom: 4px;
+}
+
+tr.blue th, tr.blue td {
+    background: #e7f1f9;
+}
+
+tr.pink th, tr.pink td {
+    background: #fdf5f6;
+}
+  
+  table.service-blueprint th.role {
+    border-top: solid #58B84F;
+    border-width: 8px;
+}
+
+.service-blueprint tbody th.steps {
+    border-top: solid 8px #aeddaa;
+}
+
+.service-blueprint tbody {
+    border-bottom: 2px solid #58B84F;
+}
+.service-blueprint tbody th:first-child {
+    padding-right: 40px;
+    padding-top: 20px;
+    min-width: 380px;
+}
+
+//optional styling
+.example-card {
+    background: white;
+    border-radius: 6px;
+    box-shadow: 1px 1px 0 rgba(0,0,0,0.08);
+    padding: 30px 0px 30px 30px;
+}
+
+body.layout--page-full-width.layout--service-blueprint-example {
+    background-color: #58B84F;
+}
+
+table.usa-table.service-blueprint {
+    margin-right: 20px;
+}
\ No newline at end of file
diff --git a/assets/application.js b/assets/application.js
index b3ec4ff9..18879278 100644
--- a/assets/application.js
+++ b/assets/application.js
@@ -25,14 +25,16 @@ const addHeadingLinks = () => {
   };
 
   const headings = document.querySelectorAll(
-    "main h1, main h2, main h3, main h4, main h5, main h6"
+    "main h2, main h3, main h4, main h5, main h6"
   );
   for (const heading of headings) {
     if (!heading.id) {
       heading.id = slugify(heading.innerText);
     }
 
-    heading.innerHTML = `${heading.innerText} <a href="#${heading.id}" aria-hidden="true" tabindex="-1" class="usa-link heading-link--symbol">#</a>`;
+    heading.innerHTML = `${heading.innerText} <span aria-hidden="true" class="heading-permalink"><a href="#${heading.id}" aria-label="Permanent link to ${heading.innerText}" class="usa-link heading-link--symbol"><svg class="usa-icon" aria-hidden="true" focusable="false" role="img">
+    <use xlink:href="#svg-link"></use>
+    </svg></a></span>`;
   }
 };
 
diff --git a/assets/downloads/ConsentForm.docx b/assets/downloads/ConsentForm.docx
deleted file mode 100644
index fa4e7dff..00000000
Binary files a/assets/downloads/ConsentForm.docx and /dev/null differ
diff --git a/assets/uswds/scss/theme/_uswds-theme-custom-styles.scss b/assets/uswds/scss/theme/_uswds-theme-custom-styles.scss
index 8578bab9..4ba00001 100644
--- a/assets/uswds/scss/theme/_uswds-theme-custom-styles.scss
+++ b/assets/uswds/scss/theme/_uswds-theme-custom-styles.scss
@@ -29,7 +29,8 @@ i.e.
   margin: 0 0 units(4) 0;
 }
 
-.layout--page main {
+.layout--page main,
+.layout--page-full-width main {
     max-width: 1024px;
     margin: 0 auto;
     box-sizing: border-box;
@@ -41,16 +42,14 @@ i.e.
   max-width: none;
 }
 
-
 @media screen and (min-width: 853.33px) {
 
   .layout--page main { padding-right: 25%; }
-  .layout--page.layout--methods main { padding-right: 0; }
+  .layout--page.layout--methods main, 
+  .layout--page-full-width main { padding-right: 0; }
 
 }
 
-
-
 // general
 iframe:focus,
 [href]:focus,
@@ -225,3 +224,57 @@ button,
     }
   }
 }
+
+// USWDS simple table styling
+//   This guide is being minimally maintained pending migration
+//   and rather than upgrade versions of USWDS, we have elected
+//   simply to copy in the rules we need to style an example table
+
+.usa-table-container--scrollable {
+  margin: 1.25rem 0;
+  overflow-y: hidden;
+}
+
+.usa-table-container--scrollable .usa-table {
+  margin: 0;
+}
+
+.usa-table {
+  border-collapse: collapse;
+  border-spacing: 0;
+  color: #1b1b1b;
+  font-family: Source Sans Pro Web,Helvetica Neue,Helvetica,Roboto,Arial,sans-serif;
+  font-size: 1.06rem;
+  line-height: 1.5;
+  margin: 1.25rem 0;
+}
+
+.usa-table, .usa-table tbody th {
+  text-align: left;
+}
+
+.usa-prose>.usa-table--striped tbody tr:nth-child(odd) td, .usa-prose>.usa-table--striped tbody tr:nth-child(odd) th, .usa-table--striped tbody tr:nth-child(odd) td, .usa-table--striped tbody tr:nth-child(odd) th {
+  background-color: #f0f0f0;
+  color: #1b1b1b;
+}
+
+.usa-table thead td, .usa-table thead th {
+  background-color: #e6e6e6;
+  color: #1b1b1b;
+}
+
+.usa-table thead th {
+  background-clip: padding-box;
+  font-weight: 700;
+  line-height: 1.3;
+}
+.usa-prose>table td, .usa-prose>table th, .usa-table td, .usa-table th {
+  background-color: #fff;
+  border: 1px solid #1b1b1b;
+  font-weight: 400;
+  padding: 0.5rem 1rem;
+}
+
+.usa-table-container--scrollable td {
+  white-space: nowrap;
+}
diff --git a/css/styles.scss b/css/styles.scss
index 49397a34..188c1bbc 100755
--- a/css/styles.scss
+++ b/css/styles.scss
@@ -9,6 +9,7 @@
 @import 'interview-checklist';
 @import 'interview-debrief';
 @import 'interview-script';
+@import 'service-blueprint';
 @import 'category';
 @import 'method';
 @import 'sticky';
diff --git a/go b/go
deleted file mode 100755
index 2e5c5ab2..00000000
--- a/go
+++ /dev/null
@@ -1,54 +0,0 @@
-#! /usr/bin/env ruby
-
-require 'English'
-
-Dir.chdir File.dirname(__FILE__)
-
-def try_command_and_restart(command)
-  exit $CHILD_STATUS.exitstatus unless system command
-  exec({ 'RUBYOPT' => nil }, RbConfig.ruby, *[$PROGRAM_NAME].concat(ARGV))
-end
-
-begin
-  require 'bundler/setup' if File.exist? 'Gemfile'
-rescue LoadError
-  try_command_and_restart 'gem install bundler'
-rescue SystemExit
-  try_command_and_restart 'bundle install'
-end
-
-begin
-  require 'go_script'
-rescue LoadError
-  try_command_and_restart 'gem install go_script' unless File.exist? 'Gemfile'
-  abort "Please add \"gem 'go_script'\" to your Gemfile"
-end
-
-require 'guides_style_18f'
-
-extend GoScript
-check_ruby_version '2.1.5'
-
-command_group :dev, 'Development commands'
-
-def_command :update_nav, 'Update the \'navigation:\' data in _config.yml' do
-  GuidesStyle18F.update_navigation_configuration Dir.pwd
-end
-
-def_command :update_theme, 'Update the guides_style_18f gem' do
-  GuidesStyle18F.update_theme
-end
-
-def_command :update_gems, 'Update Ruby gems' do |gems|
-  update_gems gems
-end
-
-def_command :serve, 'Serve the site at localhost:4000' do |args|
-  serve_jekyll args
-end
-
-def_command :build, 'Build the site' do |args|
-  build_jekyll args
-end
-
-execute_command ARGV
diff --git a/images/18f-icons/list-to-do-checked--c.svg b/images/18f-icons/list-to-do-checked--c.svg
new file mode 100644
index 00000000..487f771a
--- /dev/null
+++ b/images/18f-icons/list-to-do-checked--c.svg
@@ -0,0 +1,17 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<svg width="43px" height="34px" viewBox="0 0 43 34" version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink">
+    <!-- Generator: Sketch 61.1 (89650) - https://sketch.com -->
+    <title>svg/black/list-to-do-checked--c</title>
+    <desc>Created with Sketch.</desc>
+    <g id="**-Sticker-Sheets" stroke="none" stroke-width="1" fill="none" fill-rule="evenodd" stroke-linecap="round" stroke-linejoin="round">
+        <g id="sticker-sheet--all--page-4" transform="translate(-415.000000, -365.000000)" stroke="#000000" stroke-width="2">
+            <g id="icon-preview-row-copy-149" transform="translate(0.000000, 340.000000)">
+                <g id="Icon-Row">
+                    <g id="list-to-do-checked--c" transform="translate(413.000000, 18.214286)">
+                        <path d="M19,12.1428571 L44,12.1428571 M19,24.2857143 L44,24.2857143 M19,36.4285714 L44,36.4285714 M4,21.25 L10,21.25 L10,27.3214286 L4,27.3214286 L4,21.25 Z M4,33.3928571 L10,33.3928571 L10,39.4642857 L4,39.4642857 L4,33.3928571 Z M11,8.0952381 L5.5,14.1666667 L3,11.4069264"></path>
+                    </g>
+                </g>
+            </g>
+        </g>
+    </g>
+</svg>
\ No newline at end of file
diff --git a/images/18f-icons/settings.svg b/images/18f-icons/settings.svg
new file mode 100644
index 00000000..ccd9d6d3
--- /dev/null
+++ b/images/18f-icons/settings.svg
@@ -0,0 +1,17 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<svg width="40px" height="41px" viewBox="0 0 40 41" version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink">
+    <!-- Generator: Sketch 61.1 (89650) - https://sketch.com -->
+    <title>svg/black/settings</title>
+    <desc>Created with Sketch.</desc>
+    <g id="**-Sticker-Sheets" stroke="none" stroke-width="1" fill="none" fill-rule="evenodd" stroke-linecap="round" stroke-linejoin="round">
+        <g id="sticker-sheet--all--page-5" transform="translate(-417.000000, -2739.000000)" stroke="#000000" stroke-width="2">
+            <g id="icon-preview-row-copy-220" transform="translate(0.000000, 2717.000000)">
+                <g id="Icon-Row">
+                    <g id="settings" transform="translate(413.000000, 18.214286)">
+                        <path d="M24,29 C26.7614237,29 29,26.7614237 29,24 C29,21.2385763 26.7614237,19 24,19 C21.2385763,19 19,21.2385763 19,24 C19,26.7614237 21.2385763,29 24,29 Z M36.7818182,29.1818182 C36.3114016,30.247701 36.5371226,31.4925865 37.3518182,32.3254545 L37.4554545,32.4290909 C38.1041389,33.077054 38.4686266,33.9563135 38.4686266,34.8731818 C38.4686266,35.7900501 38.1041389,36.6693097 37.4554545,37.3172727 C36.8074915,37.9659571 35.9282319,38.3304448 35.0113636,38.3304448 C34.0944953,38.3304448 33.2152358,37.9659571 32.5672727,37.3172727 L32.4636364,37.2136364 C31.6307684,36.3989408 30.3858828,36.1732198 29.32,36.6436364 C28.2759144,37.0911179 27.5972577,38.1158895 27.5927273,39.2518182 L27.5927273,39.5454545 C27.5927273,41.4533473 26.0460746,43 24.1381818,43 C22.230289,43 20.6836364,41.4533473 20.6836364,39.5454545 L20.6836364,39.39 C20.6562705,38.2200678 19.9165058,37.1857671 18.8181818,36.7818182 C17.752299,36.3114016 16.5074135,36.5371226 15.6745455,37.3518182 L15.5709091,37.4554545 C14.922946,38.1041389 14.0436865,38.4686266 13.1268182,38.4686266 C12.2099499,38.4686266 11.3306903,38.1041389 10.6827273,37.4554545 C10.0340429,36.8074915 9.66955519,35.9282319 9.66955519,35.0113636 C9.66955519,34.0944953 10.0340429,33.2152358 10.6827273,32.5672727 L10.7863636,32.4636364 C11.6010592,31.6307684 11.8267802,30.3858828 11.3563636,29.32 C10.9088821,28.2759144 9.8841105,27.5972577 8.74818182,27.5927273 L8.45454545,27.5927273 C6.54665268,27.5927273 5,26.0460746 5,24.1381818 C5,22.230289 6.54665268,20.6836364 8.45454545,20.6836364 L8.61,20.6836364 C9.77993222,20.6562705 10.8142329,19.9165058 11.2181818,18.8181818 C11.6885984,17.752299 11.4628774,16.5074135 10.6481818,15.6745455 L10.5445455,15.5709091 C9.89586112,14.922946 9.53137337,14.0436865 9.53137337,13.1268182 C9.53137337,12.2099499 9.89586112,11.3306903 10.5445455,10.6827273 C11.1925085,10.0340429 12.0717681,9.66955519 12.9886364,9.66955519 C13.9055047,9.66955519 14.7847642,10.0340429 15.4327273,10.6827273 L15.5363636,10.7863636 C16.3692316,11.6010592 17.6141172,11.8267802 18.68,11.3563636 L18.8181818,11.3563636 C19.8622674,10.9088821 20.5409241,9.8841105 20.5454545,8.74818182 L20.5454545,8.45454545 C20.5454545,6.54665268 22.0921072,5 24,5 C25.9078928,5 27.4545455,6.54665268 27.4545455,8.45454545 L27.4545455,8.61 C27.4590759,9.74592868 28.1377326,10.7707002 29.1818182,11.2181818 C30.247701,11.6885984 31.4925865,11.4628774 32.3254545,10.6481818 L32.4290909,10.5445455 C33.077054,9.89586112 33.9563135,9.53137337 34.8731818,9.53137337 C35.7900501,9.53137337 36.6693097,9.89586112 37.3172727,10.5445455 C37.9659571,11.1925085 38.3304448,12.0717681 38.3304448,12.9886364 C38.3304448,13.9055047 37.9659571,14.7847642 37.3172727,15.4327273 L37.2136364,15.5363636 C36.3989408,16.3692316 36.1732198,17.6141172 36.6436364,18.68 L36.6436364,18.8181818 C37.0911179,19.8622674 38.1158895,20.5409241 39.2518182,20.5454545 L39.5454545,20.5454545 C41.4533473,20.5454545 43,22.0921072 43,24 C43,25.9078928 41.4533473,27.4545455 39.5454545,27.4545455 L39.39,27.4545455 C38.2540713,27.4590759 37.2292998,28.1377326 36.7818182,29.1818182 Z"></path>
+                    </g>
+                </g>
+            </g>
+        </g>
+    </g>
+</svg>
\ No newline at end of file
diff --git a/images/18f-icons/user-check.svg b/images/18f-icons/user-check.svg
new file mode 100644
index 00000000..9e2b9897
--- /dev/null
+++ b/images/18f-icons/user-check.svg
@@ -0,0 +1,17 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<svg width="38px" height="33px" viewBox="0 0 38 33" version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink">
+    <!-- Generator: Sketch 61.1 (89650) - https://sketch.com -->
+    <title>svg/black/user-check</title>
+    <desc>Created with Sketch.</desc>
+    <g id="**-Sticker-Sheets" stroke="none" stroke-width="1" fill="none" fill-rule="evenodd" stroke-linecap="round" stroke-linejoin="round">
+        <g id="sticker-sheet--all--page-6" transform="translate(-418.000000, -2660.000000)" stroke="#000000" stroke-width="2">
+            <g id="icon-preview-row-copy-269" transform="translate(0.000000, 2634.000000)">
+                <g id="Icon-Row">
+                    <g id="user-check" transform="translate(413.000000, 18.214286)">
+                        <path d="M31,39 L31,35.6666667 C31,31.9847683 28.0152317,29 24.3333333,29 L12.6666667,29 C8.98476833,29 6,31.9847683 6,35.6666667 L6,39 M18.6818182,23 C22.5478114,23 25.6818182,19.8659932 25.6818182,16 C25.6818182,12.1340068 22.5478114,9 18.6818182,9 C14.8158249,9 11.6818182,12.1340068 11.6818182,16 C11.6818182,19.8659932 14.8158249,23 18.6818182,23 Z M32,22.5 L35.3333333,26 L42,19"></path>
+                    </g>
+                </g>
+            </g>
+        </g>
+    </g>
+</svg>
\ No newline at end of file
diff --git a/images/18f-icons/user-network--c.svg b/images/18f-icons/user-network--c.svg
new file mode 100644
index 00000000..47e37780
--- /dev/null
+++ b/images/18f-icons/user-network--c.svg
@@ -0,0 +1,17 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<svg width="56px" height="48px" viewBox="0 0 56 48" version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink">
+    <!-- Generator: Sketch 61.1 (89650) - https://sketch.com -->
+    <title>svg/black/user-network--c</title>
+    <desc>Created with Sketch.</desc>
+    <g id="**-Sticker-Sheets" stroke="none" stroke-width="1" fill="none" fill-rule="evenodd" stroke-linecap="round" stroke-linejoin="round">
+        <g id="sticker-sheet--all--page-6" transform="translate(-417.000000, -3078.000000)" stroke="#000000" stroke-width="2">
+            <g id="icon-preview-row-copy-22" transform="translate(0.000000, 3059.000000)">
+                <g id="Icon-Row--Large-icon">
+                    <g id="user-network--c" transform="translate(413.000000, 10.000000)">
+                        <path d="M21.7951354,12.7957821 C24.7826905,11.0198601 28.2722447,10 32,10 C35.7277553,10 39.2173095,11.0198601 42.2048646,12.7957821 M51.3698299,35.0003211 C50.1176945,39.8648719 47.0813749,44.0131322 43,46.7059175 M20.9997776,46.7058074 C16.9185423,44.0130191 13.8822885,39.8648056 12.6301701,35.0003211 M40,56 L40,54 C40,51.790861 38.209139,50 36,50 L28,50 C25.790861,50 24,51.790861 24,54 L24,56 M32,46 C34.209139,46 36,44.209139 36,42 C36,39.790861 34.209139,38 32,38 C29.790861,38 28,39.790861 28,42 C28,44.209139 29.790861,46 32,46 Z M59,32 L59,30 C59,27.790861 57.209139,26 55,26 L47,26 C44.790861,26 43,27.790861 43,30 L43,32 M51,22 C53.209139,22 55,20.209139 55,18 C55,15.790861 53.209139,14 51,14 C48.790861,14 47,15.790861 47,18 C47,20.209139 48.790861,22 51,22 Z M5,32 L5,30 C5,27.790861 6.790861,26 9,26 L17,26 C19.209139,26 21,27.790861 21,30 L21,32 M13,22 C10.790861,22 9,20.209139 9,18 C9,15.790861 10.790861,14 13,14 C15.209139,14 17,15.790861 17,18 C17,20.209139 15.209139,22 13,22 Z"></path>
+                    </g>
+                </g>
+            </g>
+        </g>
+    </g>
+</svg>
\ No newline at end of file
diff --git a/index.html b/index.html
index 2e1c190f..bfb5deab 100755
--- a/index.html
+++ b/index.html
@@ -5,13 +5,16 @@
 ---
 <div class="usa-section intro-header">
   <div class="grid-container">
+    <h1 class="visually-hidden">{% if page.title %}
+      {{ page.title }}
+    {% endif %}    </h1>
     <p class="usa-intro no-print">A collection of tools to bring human-centered design into your project.</p>
   </div>
 </div>
 <div class="usa-section">
   {% for category in site.data.categories %}
     <section class="usa-prose grid-container category usa-section category--{{ category.category_name | downcase }}" id="{{ category.category_name | downcase }}">
-      <h1 class="category--title category--{{ category.category_name | downcase }}--title">{{ category.category_name }}</h1>
+      <h2 class="category--title category--{{ category.category_name | downcase }}--title">{{ category.category_name }}</h2>
       <div class="grid-row">
         <div class="grid-col-8">
           <div class="category--header usa-content">
@@ -21,7 +24,7 @@ <h1 class="category--title category--{{ category.category_name | downcase }}--ti
           </div>
         </div>
         <div class="grid-col-4 methods-listing">
-          <h2>Methods include</h2>
+          <h3>Methods include</h3>
           <ul class="usa-list">
             {% for method in category.methods %}
             <li>
diff --git a/pages/about.md b/pages/about.md
index 05697f3c..d9739b1d 100755
--- a/pages/about.md
+++ b/pages/about.md
@@ -12,12 +12,12 @@ The 18F Methods are a collection of tools that describe how our teams put human-
 Human-centered design, also referred to as "user-centered design," is a methodology that incorporates feedback from the people for whom you are designing throughout the design process. The goal of human-centered design is to end up with a solution that is tailored to meet people's needs, with little wasted effort and reduced risk. To achieve this goal, design teams at 18F talk with and observe real users to understand their needs, context, and challenges, come up with design concepts that might address these challenges, and then test them with real users. Find more resources on human-centered design in government in 18F's [User Experience Design Guide](https://ux-guide.18f.gov/) or at [digital.gov](https://digital.gov/topics/design/), including this overview of [the basics of human-centered design in government](https://www.youtube.com/watch?v=DGDCd2ELpok) from the Lab@OPM.
 
 ## Using the 18F Methods
-The 18F Methods are broken up into the four broad design phases your team is likely to go through during a project. While some cards refer to other methods, you may use them independently. You do not need to use all the cards in a section or complete certain tasks before moving on to others. Take whatever cards are most useful to your team and incorporate more tools as you’re ready.
+The 18F Methods are broken up into the four broad design phases your team is likely to go through during a project. The four phases are [Discover]({{site.baseurl}}/discover), [Decide]({{site.baseurl}}/decide), [Make]({{site.baseurl}}/make), [Validate]({{site.baseurl}}/validate). We provide cards that walk you through the steps of each phase and cards that deal with the [fundamentals]({{site.baseurl}}/fundamentals). While some cards refer to other methods, you may use them independently. You do not need to use all the cards in a section or complete certain tasks before moving on to others. Take whatever cards are most useful to your team and incorporate more tools as you’re ready.
 
 We’ve included additional guidance for using these methods in government research, specifically around the [Paperwork Reduction Act (PRA)](https://www.opm.gov/about-us/open-government/digital-government-strategy/fitara/paperwork-reduction-act-guide.pdf). We’re only able to include brief guidance on the PRA, and federal workers should check with their agency counsel for additional guidance. You should also read the cards in the fundamentals section for more background on conducting design research as a government employee.
 
 ## Go behind the scenes
-As with all of 18F’s products, the 18F Methods are completely open source. You are free to copy, share, or reuse them [as you wish](https://github.com/18F/methods/blob/staging/LICENSE.md). We also welcome input from the public or our government colleagues, whether it’s correcting a typo or suggesting a new method to include. You can see our [guidelines for contributing on GitHub](https://github.com/18F/methods/blob/staging/CONTRIBUTING.md). Please don't hesitate to reach out to the team at [18f-methods@gsa.gov](mailto:18f-methods@gsa.gov) with questions, comments, or suggestions. You can also send us your thoughts using the **Get in touch** button at the bottom of each page.
+As with all of 18F’s products, the 18F Methods are completely open source. You are free to copy, share, or reuse them [as you wish](https://github.com/18F/methods/blob/staging/LICENSE.md). We also welcome input from the public or our government colleagues, whether it’s correcting a typo or suggesting a new method to include. You can see our [guidelines for contributing on GitHub](https://github.com/18F/methods/blob/staging/CONTRIBUTING.md). To share your feedback about the Methods site, click the **Provide feedback** button that you can find at the bottom of each page or open an issue or pull request in [our GitHub repository](https://github.com/18F/methods).
 
 ## Release notes
 
diff --git a/pages/interview-checklist.md b/pages/archive/interview-checklist.md
similarity index 100%
rename from pages/interview-checklist.md
rename to pages/archive/interview-checklist.md
diff --git a/pages/interview-debrief.md b/pages/archive/interview-debrief.md
similarity index 100%
rename from pages/interview-debrief.md
rename to pages/archive/interview-debrief.md
diff --git a/pages/interview-script.md b/pages/archive/interview-script.md
similarity index 100%
rename from pages/interview-script.md
rename to pages/archive/interview-script.md
diff --git a/pages/participant-agreement-spanish.md b/pages/archive/participant-agreement-spanish.md
similarity index 100%
rename from pages/participant-agreement-spanish.md
rename to pages/archive/participant-agreement-spanish.md
diff --git a/pages/participant-agreement.md b/pages/archive/participant-agreement.md
similarity index 100%
rename from pages/participant-agreement.md
rename to pages/archive/participant-agreement.md
diff --git a/pages/usability-test-script.md b/pages/archive/usability-test-script.md
similarity index 100%
rename from pages/usability-test-script.md
rename to pages/archive/usability-test-script.md
diff --git a/pages/service-blueprint-example.md b/pages/service-blueprint-example.md
new file mode 100644
index 00000000..97e1b151
--- /dev/null
+++ b/pages/service-blueprint-example.md
@@ -0,0 +1,148 @@
+---
+title: Service blueprint example
+description: A service blueprint of getting a burger
+layout: page-full-width
+permalink: /service-blueprint-example/
+---
+
+<style type="text/css" media="print">
+@page {
+  margin: 1in;
+}
+</style>
+<section class="example-card">
+# Service blueprint example
+<p>This simple [service blueprint]({% link _methods/service-blueprint.md %}) is an example of how you might lay out the layers of your service. There are many ways to create a service blueprint and adapt the structure to best represent and capture your context.</p>
+<div class="usa-table-container--scrollable" tabindex="0">
+  <table class="usa-table service-blueprint">
+    <caption>This is a table showing an example service blueprint. The top row is the journey of a customer ordering and eating a burger at a restaurant. Each column is a different step in the customer's journey. The remaining rows describe different parts of the service and the support provided at each step in the customer’s journey.</caption>
+      <tr>
+        <th scope="row" class="role"> 
+        <img src="../images/18f-icons/user-check.svg" alt="" width="48" height="48">
+        <strong>User steps</strong><br>
+        The primary action someone takes when interacting with the service.</th>
+        <th scope="col" class="steps"><strong>Decide and look up how to get to the restaurant</strong></th>
+        <th scope="col" class="steps"><strong>Arrive at the restaurant and order</strong></th>
+        <th scope="col" class="steps"><strong>Find a table and eat the burger</strong></th>
+        <th scope="col" class="steps"><strong>Clean up and leave the restaurant</strong></th>
+      </tr>
+      <tr>
+        <th scope="row">
+        <img src="../images/18f-icons/user-network--c.svg" alt="" width="48" height="48">
+        <strong>Frontstage</strong><br>
+        The online and offline interactions that users have with the service which includes the people, places, objects which users interact with.</th>
+        <td>
+          <ul>
+            <li>Website</li>
+            <li>Newspaper</li>
+            <li>Radio Ad</li>
+            <li>Address search</li>
+          </ul>
+        </td>
+      <td>
+        <ul>
+          <li>Parking Lot</li>
+          <li>Building</li>
+          <li>Lobby</li>
+          <li>Signage</li>
+          <li>Electronic menu</li>
+          <li>Paper menu</li>
+        </ul>
+      </td>
+      <td>
+        <ul>
+          <li>Counter</li>
+          <li>Cash register</li>
+          <li>Card reader</li>
+          <li>Electronic menu</li>
+          <li>Paper menu</li>
+        </ul>
+      </td>
+      <td>
+        <ul>
+          <li>Paper goods</li>
+          <li>Condiment counter</li>
+          <li>Condiment containers</li>
+          <li>Napkins</li>
+          <li>Cutlery</li>
+        </ul>
+      </td>
+      </tr>
+      <tr>
+        <th scope="row">
+        <img src="../images/18f-icons/settings.svg" alt="" width="48" height="48">
+        <strong>Backstage</strong><br>
+      Activities in the systems and  
+      processes that support the  
+      frontstage experience, but are not  
+      visible to users</th>
+        <td>
+          <ul>
+            <li>
+              Website maintenance
+              <li>Customer service support and staffing</li>
+              <li>Branding and advertising activities</li>
+            </li>
+          </ul>
+        </td>
+        <td>
+          <ul>
+            <li>Staff support and scheduling</li>
+            <li>Payment system</li>
+            <li>Menu upkeep</li>
+          </ul>
+        </td>
+        <td>
+          <ul>
+            <li>Staff support and scheduling</li>
+            <li>Dining area maintenance</li>
+          </ul>
+        </td>
+        <td>
+        <ul>
+            <li>Staff support and scheduling</li>
+            <li>Waste collection</li>
+        </ul>
+        </td>
+      </tr>
+      <tr>
+        <th scope="row"><img src="../images/18f-icons/list-to-do-checked--c.svg" alt="" width="48" height="48">
+        <strong>Support processes</strong><br>  
+        Activities executed by the rest of the organization or external partners — such as ongoing data management or software licensing — that don’t fall into the other rows</th>
+        <td>
+          <ul>
+            <li>Advertising partnerships</li>
+            <li>Website server support</li>
+            <li>Branding and website efforts</li>
+          </ul>
+        </td>
+        <td>
+          <ul>
+            <li>Building license</li>
+            <li>Food supply</li>
+            <li>Gas, electricity, and water</li>
+            <li>Food safety regulations</li>
+            <li>Workers' union partnership</li>
+            <li>Employee policies</li>
+          </ul>
+        </td>
+        <td>
+          <ul>
+            <li>Building license</li>
+            <li>Food supply</li>
+            <li>Gas, electricity, and water</li>
+            <li>Food safety regulations</li>
+            <li>Workers' union partnership</li>
+            <li>Employee policies</li>
+          </ul>
+        </td>
+        <td>
+          <ul>
+            <li>Waste management contracts</li>
+            <li>Customer service staff support and scheduling</li>
+          </ul>
+        </td>
+      </tr>
+  </table>
+</div>
+</section>