diff --git a/_data/agencies.yml b/_data/agencies.yml
index 893e248ae..55d6b3ba4 100644
--- a/_data/agencies.yml
+++ b/_data/agencies.yml
@@ -1,144 +1,144 @@
-
name: U.S. Air Force
acronym: USAF
- logo: usaf.png
+ logo: assets/img/logos/agencies/usaf.png
featured: true
-
name: U.S. Army
- logo: us-army.png
+ logo: assets/img/logos/agencies/us-army.png
-
name: U.S. Marine Corps
acronym: USMC
- logo: usmc.png
+ logo: assets/img/logos/agencies/usmc.png
-
name: U.S. Navy
- logo: us-navy.png
+ logo: assets/img/logos/agencies/us-navy.png
-
name: Centers for Medicare and Medicaid Services
- logo: centers-for-medicare-and-medicaid.png
+ logo: assets/img/logos/agencies/centers-for-medicare-and-medicaid.png
-
name: Consumer Financial Protection Bureau
acronym: CFPB
- logo: cfpb.png
+ logo: assets/img/logos/agencies/cfpb.png
-
name: Department of Agriculture
acronym: USDA
- logo: USDA.svg
+ logo: assets/img/logos/agencies/USDA.svg
-
name: Department of Education
- logo: USDE.png
+ logo: assets/img/logos/agencies/USDE.png
-
name: Department of Health and Human Services
acronym: HHS
- logo: USDHHS.png
+ logo: assets/img/logos/agencies/USDHHS.png
featured: true
-
name: Department of the Interior
acronym: DOI
- logo: USDOI.svg
+ logo: assets/img/logos/agencies/USDOI.svg
featured: true
-
name: Department of Justice
acronym: DOJ
- logo: USDOJ.png
+ logo: assets/img/logos/agencies/USDOJ.png
featured: true
-
name: Department of State
- logo: USDS.png
+ logo: assets/img/logos/agencies/USDS.png
-
name: Department of the Treasury
- logo: USDT.png
+ logo: assets/img/logos/agencies/USDT.png
-
name: Federal Bureau of Investigation
acronym: FBI
- logo: fbi.png
+ logo: assets/img/logos/agencies/fbi.png
-
name: Federal Election Commission
acronym: FEC
- logo: fec.svg
+ logo: assets/img/logos/agencies/fec.svg
-
name: Federal Emergency Management Agency
acronym: FEMA
- logo: fema.png
+ logo: assets/img/logos/agencies/fema.png
-
name: Federal Retirement Thrift Investment Board
- logo: frtib.png
+ logo: assets/img/logos/agencies/frtib.png
-
name: General Services Administration
acronym: GSA
- logo: gsa-logo.svg
+ logo: assets/img/logos/agencies/gsa-logo.svg
-
name: National Geospatial-Intelligence Agency
acronym: NGA
- logo: nga.png
+ logo: assets/img/logos/agencies/nga.png
-
name: National Institute of Standards and Technology
acronym: NIST
- logo: nist.png
+ logo: assets/img/logos/agencies/nist.png
-
name: National Oceanic and Atmospheric Administration
acronym: NOAA
- logo: noaa.png
+ logo: assets/img/logos/agencies/noaa.png
-
name: National Science Foundation
acronym: NSF
- logo: nsf.png
+ logo: assets/img/logos/agencies/nsf.png
-
name: The Library of Congress
- logo: loc.png
+ logo: assets/img/logos/agencies/loc.png
-
name: U.S. Tax Court
- logo: tax-court.png
+ logo: assets/img/logos/agencies/tax-court.png
-
name: Environmental Protection Agency
acronym: EPA
- logo: EPA.png
+ logo: assets/img/logos/agencies/EPA.png
-
name: National Aeronautics and Space Administration
acronym: NASA
- logo: NASA.svg
+ logo: assets/img/logos/agencies/NASA.svg
-
name: National Archives and Records Administration
acronym: NARA
- logo: NARA.png
+ logo: assets/img/logos/agencies/NARA.png
-
name: Nuclear Regulatory Commission
- logo: NRC.svg
+ logo: assets/img/logos/agencies/NRC.svg
-
name: Office of Management and Budget
acronym: OMB
- logo: OMB.svg
+ logo: assets/img/logos/agencies/OMB.svg
featured: true
-
name: Office of Personnel Management
acronym: OPM
- logo: OPM.svg
+ logo: assets/img/logos/agencies/OPM.svg
-
name: Alaska Department of Health and Social Services
- logo: alaska-dhss.png
+ logo: assets/img/logos/agencies/alaska-dhss.png
-
name: California Child Welfare Digital Services
acronym: CWDS
- logo: cwds.png
+ logo: assets/img/logos/agencies/cwds.png
-
name: State of Vermont Agency of Human Services
- logo: vermont.png
+ logo: assets/img/logos/agencies/vermont.png
-
name: Securities and Exchange Commission
acronym: SEC
- logo: SEC.svg
+ logo: assets/img/logos/agencies/SEC.svg
-
name: Small Business Administration
acronym: SBA
- logo: SBA.svg
+ logo: assets/img/logos/agencies/SBA.svg
-
name: Social Security Administration
- logo: SSA.png
+ logo: assets/img/logos/agencies/SSA.png
-
name: State of Wisconsin
- logo: wisconsin.svg
+ logo: assets/img/logos/agencies/wisconsin.svg
featured: true
-
name: U.S. Postal Service
acronym: USPS
- logo: USPS.svg
+ logo: assets/img/logos/agencies/USPS.svg
diff --git a/_data/guides.yml b/_data/guides.yml
index 5c2c4e2b1..28975d4b5 100644
--- a/_data/guides.yml
+++ b/_data/guides.yml
@@ -7,8 +7,8 @@
description: "Make websites more accessible so everyone can use them."
promoted: false
image:
- light: "/assets/img/guides/accessibility-lightest.svg"
- dark: "/assets/img/guides/accessibility-darker.svg"
+ light: "assets/img/guides/accessibility-lightest.svg"
+ dark: "assets/img/guides/accessibility-darker.svg"
hero: ""
- name: "Agile"
@@ -16,8 +16,8 @@
description: "Move toward an agile approach to stay within budget and provide value to the public."
promoted: false
image:
- light: "/assets/img/guides/agile-lightest.svg"
- dark: "/assets/img/guides/agile-darker.svg"
+ light: "assets/img/guides/agile-lightest.svg"
+ dark: "assets/img/guides/agile-darker.svg"
hero: ""
- name: "Content"
@@ -25,8 +25,8 @@
description: "Create content in plain language to help the public save time and build trust."
promoted: false
image:
- light: "/assets/img/guides/content-lightest.svg"
- dark: "/assets/img/guides/content-darker.svg"
+ light: "assets/img/guides/content-lightest.svg"
+ dark: "assets/img/guides/content-darker.svg"
hero: ""
- name: "Derisking"
@@ -35,8 +35,8 @@
promoted: true
image:
light: ""
- dark: "/assets/img/guides/derisking-darker.svg"
- hero: "/assets/img/guides/derisking-hero.svg"
+ dark: "assets/img/guides/derisking-darker.svg"
+ hero: "assets/img/guides/derisking-hero.svg"
- name: "Design Methods"
link: "https://guides.18f.gov/methods/"
@@ -44,8 +44,8 @@
promoted: true
image:
light: ""
- dark: "/assets/img/guides/design-methods-darker.svg"
- hero: "/assets/img/guides/design-methods-hero.svg"
+ dark: "assets/img/guides/design-methods-darker.svg"
+ hero: "assets/img/guides/design-methods-hero.svg"
- name: "Engineering"
link: "https://guides.18f.gov/engineering"
@@ -53,7 +53,7 @@
promoted: false
image:
light: ""
- dark: "/assets/img/guides/engineering-darker.svg"
+ dark: "assets/img/guides/engineering-darker.svg"
hero: ""
- name: "Product"
@@ -61,8 +61,8 @@
description: "Support a team to deliver the right product to the right audience."
promoted: false
image:
- light: "/assets/img/guides/product-lightest.svg"
- dark: "/assets/img/guides/product-darker.svg"
+ light: "assets/img/guides/product-lightest.svg"
+ dark: "assets/img/guides/product-darker.svg"
hero: ""
- name: "User Experience"
@@ -70,6 +70,6 @@
description: "Make your products and services work for the people that use them."
promoted: false
image:
- light: "/assets/img/guides/ux-lightest.svg"
- dark: "/assets/img/guides/ux-darker.svg"
+ light: "assets/img/guides/ux-lightest.svg"
+ dark: "assets/img/guides/ux-darker.svg"
hero: ""
diff --git a/_data/social_media.yml b/_data/social_media.yml
index 038e38cb3..0d00573f7 100644
--- a/_data/social_media.yml
+++ b/_data/social_media.yml
@@ -2,23 +2,23 @@
platform: GitHub
link: https://github.com/18F
image:
- light: /assets/img/social-icons/svg/github-lightest.svg
- dark: /assets/img/social-icons/svg/github-darkest.svg
+ light: assets/img/social-icons/svg/github-lightest.svg
+ dark: assets/img/social-icons/svg/github-darkest.svg
-
platform: Twitter
link: https://twitter.com/18F
image:
- light: /assets/img/social-icons/svg/twitter-lightest.svg
- dark: /assets/img/social-icons/svg/twitter-darkest.svg
+ light: assets/img/social-icons/svg/twitter-lightest.svg
+ dark: assets/img/social-icons/svg/twitter-darkest.svg
-
platform: LinkedIn
link: https://www.linkedin.com/company/gsa18f
image:
- light: /assets/img/social-icons/svg/linkedin-lightest.svg
- dark: /assets/img/social-icons/svg/linkedin-darkest.svg
+ light: assets/img/social-icons/svg/linkedin-lightest.svg
+ dark: assets/img/social-icons/svg/linkedin-darkest.svg
-
platform: RSS feed
link: /feed/
image:
- light: /assets/img/social-icons/svg/rss-lightest.svg
- dark: /assets/img/social-icons/svg/rss25.svg
+ light: assets/img/social-icons/svg/rss-lightest.svg
+ dark: assets/img/social-icons/svg/rss25.svg
diff --git a/_includes/card-project.html b/_includes/card-project.html
index c43882001..4bbfcfd5f 100644
--- a/_includes/card-project.html
+++ b/_includes/card-project.html
@@ -1,38 +1,31 @@
{% comment %}
This partial outputs a card that displays a project title, the associated agency logo, and an excerpt. The expected argument for this partial is the markdown file name for the project, which is in the "_services_projects" directory.
{% endcomment %}
-
{% assign project = collections.services | where: 'fileSlug', project_id | first %}
-
-
- {% comment %}
- code smell: nil checks / timid code
- This template is uncertain about the presence of project.data.agency, agency.logo, project.url, and project.data.title. If any of those are missing, this template doesn't work or look good.
-
- A better way to handle would be to enforce some data guarantees in a pre-build stage, or have the
- template error out.
- {% endcomment %}
- {% if project.data.agency %}
-
-
+
+ {% comment %}
+ code smell: nil checks / timid code
+ This template is uncertain about the presence of project.data.agency, agency.logo, project.url, and project.data.title. If any of those are missing, this template doesn't work or look good.
+ A better way to handle would be to enforce some data guarantees in a pre-build stage, or have the
+ template error out.
+{% endcomment %}
+{% if project.data.agency %}
+
We helped the U.S. Citizenship and Immigration Services (USCIS) launch myUSCIS, a platform that allows users to easily access information about the immigration process and find immigration options for which they may qualify. Re-imagining the immigration process meant moving from a form-centric website to a human-centric one. We worked closely with USCIS across multiple disciplines to create a suite of resources and tools to demystify the naturalization process, move application forms online, and design an improved account system for applicants.
BetaFEC
-
+
{% image "assets/img/projects/beta-fec.jpg" "A screenshot of the betaFEC homepage" %}
The Federal Election Commission (FEC) has long been a pioneer of open data, but 18F was able to help the FEC build its first public API and a new website on top of that API. This site helps make campaign finance information more accessible to the public, as part of a larger redesign of the FEC’s online presence. Read more about the site and why we’ve released it as a beta.
College Scorecard
-
+
{% image "assets/img/projects/college-scorecard.jpg" "A screenshot of the college scorecard" %}
The College Scorecard site is an example of what 18F can do to help your agency provide an interactive, well-designed way for the public to access your data. We worked with the U.S. Digital Service and the Department of Education to build College Scorecard to give students and their families access to previously unreleased data about colleges and universities so they can make better decisions. The site is built on top of a public API, which also allows private individuals and companies to use the data. Read more about the College Scorecard project.
U.S. Web Design System
-
+
{% image "assets/img/projects/draft-us-web-design-standards.png" "A screenshot of standards.usa.gov" %}
{% image "assets/img/projects/analytics-usa-gov.png" "A screenshot of the analytics.usa.gov homepage." %}
You can now view a dashboard of analytics data from the websites of agencies participating in GSA's Digital Analytics Program. The basic dashboard has three views: one showing how many people are on government websites right now; the other two show the most popular pages on government sites in the last seven and 30 days. In 2016, we added agency-specific pages to the dashboard, allowing users to see the same data for several departments as well as across the entire government. This open source project has been adapted for use in other city and state governments.
cloud.gov
-
+
{% image "assets/img/projects/cloud-gov.png" "A screenshot of the cloud.gov homepage" %}
cloud.gov includes a Platform-as-a-Service (PaaS) specifically built for government, based on the open source Cloud Foundry. It provides a secure, scalable platform for teams to build and host their application or website. It can help development teams work faster and cheaper by handling much of their deployment complexity. The cloud.gov platform is currently in a small pilot program, but we will be expanding access over time.
Wage and Hour Division Field Operations Handbook
-
+
{% image "assets/img/projects/dol-handbook.jpg" "The 18F team working with Department of Labor staff in the GSA headquarters." %}
In two days, our consulting team was able to work with a team at the Department of Labor’s Wage and Hour Division to take the four-volume, printed Field Operations Handbook and create an internal prototype of an online, searchable version. We were also able to demonstrate the power of using agile design and development methods.
RFP Ghostwriting with the State of California
-
+
{% image "assets/blog/ca-child-welfare/ca-team.jpg" "The California, Code for America, and 18F team after the workshop." %}
We partnered with the Department of Health and Human Services, the State of California, and Code for America to draft a request for proposal (RFP) to fix the state's child welfare case management system. This system is used by more than 20,000 social workers to track and manage the more than 500,000 cases of child abuse and neglect that are reported in California each year. 18F's two-day RFP ghostwriting workshop got stakeholders on board with modular contracting and modern development methodologies, and helped the state trim their initial 1,500 page RFP into two 70-page documents.
- {% assign image_path = "/assets/img/logos/agencies/" | append: project_agency.logo %}
{% include "card-with-image.html",
- image_path: image_path,
+ image_path: project_agency.logo,
image_alt_text: project_agency.name,
image_size: "md",
link_url: project_details.data.permalink,
diff --git a/content/posts/2014-09-04-a-new-look-at-the-freedom-of-information-act.md b/content/posts/2014-09-04-a-new-look-at-the-freedom-of-information-act.md
index b8e5707eb..1b9a7c350 100644
--- a/content/posts/2014-09-04-a-new-look-at-the-freedom-of-information-act.md
+++ b/content/posts/2014-09-04-a-new-look-at-the-freedom-of-information-act.md
@@ -5,7 +5,7 @@ tumblr_url: http://18fblog.tumblr.com/post/96625804492/a-new-look-at-the-freedom
title: "A new look at the Freedom of Information Act"
-image: /assets/blog/foia/in-hand.jpg
+image: assets/blog/foia/in-hand.jpg
description: "As demand for information continues to grow, it is important to continue iterating the ways we refine the FOIA request process. Our effort is one of a number of commitments towards creating a more open, transparent government. We will explore how to supplement the work that has already been done by creating tools to improve the online FOIA requests process by designing for the user."
excerpt: "As demand for information continues to grow, it is important to continue iterating the ways we refine the FOIA request process. Our effort is one of a number of commitments towards creating a more open, transparent government. We will explore how to supplement the work that has already been done by creating tools to improve the online FOIA requests process by designing for the user."
@@ -34,7 +34,7 @@ Since 1966, the [Freedom of Information Act](http://www.foia.gov/about.html), FO
As demand for information continues to grow, it is important to continue iterating the ways we refine the FOIA request process. Our effort is one of a number of [commitments (PDF)](https://obamawhitehouse.archives.gov/sites/default/files/docs/us_national_action_plan_6p.pdf) towards creating a more open, transparent government. We will explore how to supplement the work that has already been done by creating tools to improve the online FOIA requests process by designing for the user.
diff --git a/content/posts/2014-09-18-getting-to-work-for-the-american-people.md b/content/posts/2014-09-18-getting-to-work-for-the-american-people.md
index bd0f3f4d5..cca0f207e 100644
--- a/content/posts/2014-09-18-getting-to-work-for-the-american-people.md
+++ b/content/posts/2014-09-18-getting-to-work-for-the-american-people.md
@@ -94,7 +94,7 @@ Attracting great digital talent
-------------------------------
diff --git a/content/posts/2014-09-25-design-studio-onrr.md b/content/posts/2014-09-25-design-studio-onrr.md
index 6ee27a3df..5d4b1c318 100644
--- a/content/posts/2014-09-25-design-studio-onrr.md
+++ b/content/posts/2014-09-25-design-studio-onrr.md
@@ -60,17 +60,17 @@ Next, following a round of introductions, we dove right into the collaborative d
**Creating user personas.** Based on the participants’ previous research on users, the group developed [user personas](http://www.usability.gov/how-to-and-tools/methods/personas.html) to serve as examples of the types of people who would interact with the website. We did this by brainstorming possible user goals, behavior patterns, skills, attitudes and environments, and then condensing these into representative groups through [affinity mapping](https://en.wikipedia.org/wiki/Affinity_diagram). The resulting personas give users actual characteristics — names, faces and narratives. This helps our design studio participants (and our 18F team designers!) shift focus away from meeting specific requirements and deliverables, and onto meeting the needs of the users.
-![photo: team creating personas]({{site.baseurl}}/assets/blog/eiti/eiti1.jpg)
+{% image "assets/blog/eiti/eiti1.jpg" "photo: team creating personas" %}
_Building user personas_
**Sketching.** Next came rapid rounds of sketching. Participants chose a specific user persona to design for, and each individual was asked to produce 5 sketches in 8 minutes depicting how to meet that user’s needs. After the buzzer told everyone to put their pens down, all participants presented and critiqued each other’s sketches. To do this, we focused on: “Does the design satisfy the goals of the user persona?” and “What assumptions does the design make that we want or need to test?”
-![photo: critiquing sketches]({{site.baseurl}}/assets/blog/eiti/eiti2.jpg)
+{% image "assets/blog/eiti/eiti2.jpg" "photo: critiquing sketches" %}
_Critiquing the first round of sketches_
We didn’t focus on whether the design was pretty or technically feasible; we simply wanted to generate ideas we knew would delight our user personas. This process — sketching, presenting, and critiquing — was repeated until the group converged on a clear set of winning designs.
-![photo: wall of sketches]({{site.baseurl}}/assets/blog/eiti/eiti3.jpg)
+{% image "assets/blog/eiti/eiti3.jpg" "photo: wall of sketches" %}
_Second round of sketches producing some clear winners!_
## What’s next?
diff --git a/content/posts/2014-11-13-why-we-use-https-in-every-gov-website-we-make.md b/content/posts/2014-11-13-why-we-use-https-in-every-gov-website-we-make.md
index 891eb2f32..2721e653e 100644
--- a/content/posts/2014-11-13-why-we-use-https-in-every-gov-website-we-make.md
+++ b/content/posts/2014-11-13-why-we-use-https-in-every-gov-website-we-make.md
@@ -20,7 +20,7 @@ On today's Internet, in today's web browsers, **HTTPS** (`https://`) offers the
That's why 18F's policy is to **use HTTPS for every .gov website we make**. 18F is an in-house government technology team that builds things for the rest of the U.S. federal government, and we're committed to deploying HTTPS across all of our released websites.
-![HTTPS URL on desktop]({{site.baseurl}}/assets/blog/https-everywhere/18f-https-desktop.png)
+{% image "assets/blog/https-everywhere/18f-https-desktop.png" "HTTPS URL on desktop" %}
Deciding to use HTTPS everywhere was not difficult. Strong encryption benefits our visitors and our government partners by providing:
diff --git a/content/posts/2014-11-17-taking-control-of-our-website-with-jekyll-and-webhooks.md b/content/posts/2014-11-17-taking-control-of-our-website-with-jekyll-and-webhooks.md
index 69ec55f65..6045f4067 100644
--- a/content/posts/2014-11-17-taking-control-of-our-website-with-jekyll-and-webhooks.md
+++ b/content/posts/2014-11-17-taking-control-of-our-website-with-jekyll-and-webhooks.md
@@ -15,7 +15,7 @@ tags:
- jekyll
---
-[![Our website running with Jekyll]({{site.baseurl}}/assets/blog/new-jekyll-site/header.png)](https://github.com/18F/18f.gsa.gov/pull/235)
+[{% image "assets/blog/new-jekyll-site/header.png" "Our website running with Jekyll" %}](https://github.com/18F/18f.gsa.gov/pull/235)
A few of us here recently took a bit of time to drastically rework 18F's main [website and blog](https://18f.gsa.gov) — what you're reading right now — and take it fully into our own hands.
@@ -128,7 +128,7 @@ We made this work using **[GitHub's webhooks](https://github.com/blog/1778-webho
We created two webhooks for [our website's main repository](https://github.com/18f/18f.gsa.gov), pointed at our staging and live URLs:
-![18F site webhooks]({{site.baseurl}}/assets/blog/new-jekyll-site/webhooks.png)
+{% image "assets/blog/new-jekyll-site/webhooks.png" "18F site webhooks" %}
Each is configured to notify the webhook when changes are made to the files in the repository, either directly or through a pull request.
diff --git a/content/posts/2014-11-26-how-to-use-more-open-source.md b/content/posts/2014-11-26-how-to-use-more-open-source.md
index bcb8ec778..a398c2748 100644
--- a/content/posts/2014-11-26-how-to-use-more-open-source.md
+++ b/content/posts/2014-11-26-how-to-use-more-open-source.md
@@ -42,7 +42,7 @@ We can mark important events in the evolution of the relational database for end
1. 2007: PostgreSQL either comes with a Linux distribution or can be installed in 20 minutes.
1. 2014: PostgreSQL can be installed in five minutes, is more convenient to use, and is a common backbone of 18F's projects and many commercial firms.
-
+{% image_with_class "assets/blog/2014/11/25/image00.png" "image-open-source-blog" "ThirtyYearHistoryOfPostgresAndLucene (1).png" %}
The above graph shows our subjective evaluation of the usefulness of PostgreSQL relative to its total cost of ownership. This "geometrically" increasing usefulness is familiar from hardware performance curves plotted against time, but in this case owes very little to that phenomenon. Rather, it represents the typical commoditization of software. The community of users and developers drive important software tools from unique inventions to broadly available tools. Along the way, the tool usually becomes a commercial product, and then becomes available as an open source alternative.
@@ -66,11 +66,11 @@ The same diagram also plots the even more rapid evolution of a an open source fu
On the __Value Chain axis__, we have inserted the [standard three-tier architecture](https://en.wikipedia.org/wiki/Multitier_architecture), consisting of a Persistence Layer, Business Logic Layer, and Presentation Layer.
-
+{% image_with_class "assets/blog/2014/11/25/image03.png" "image-open-source-blog" "PostgresTemplateOpenSourceThreeLayerWithDecorations (1).png" %}
_The evolution of PostgreSQL_
-
+{% image_with_class "assets/blog/2014/11/25/image04.png" "image-open-source-blog" "LuceneTemplateOpenSourceThreeLayerWithDecorations (1).png" %}
_The evolution of Lucene_
@@ -86,7 +86,7 @@ __Now take each component and analyze it in terms of the evolution axis.__ That
__Now draw a draft Wardley-Duncan map of our your system.__ A large whiteboard with sticky notes is a convenient way to do this, but you can also print out our basic disposable diagram by following this [link]({{ site.baseurl }}/assets/blog/2014/11/25/image02.png) to this diagram:
-
+{% image_with_class "assets/blog/2014/11/25/image02.png" "image-open-source-blog" "PrintableOpenSourceWardleyDuncanMap (2).png" %}
Now that you have analyzed your system, ask yourself if any "moves" are possible. A move would be a change to your system that changed the position of one of your components. For example, can you identify a part of your system which was written by a contractor whose function has now been mostly subsumed by the increasing power and commoditization of software? Are you using a product that has an open source equivalent? __In general, any move to the right on this diagram represents a chance to make your system more secure, robust, easier to support, and to save the taxpayer money.__
@@ -120,7 +120,7 @@ We have asserted that open source software represents the endpoint of a commodit
The open source community and the availability of open source code appears to be growing explosively. At the end of 2013, GitHub [announced that they had 10 million repositories](https://github.com/blog/1724-10-million-repositories), and published this chart:
-
+{% image_with_class "assets/blog/2014/11/25/image01.png" "image-open-source-blog" "68747470733a2f2f662e636c6f75642e6769746875622e636f6d2f6173736574732f343438332f313830333636372f62306564363634652d366332342d313165332d393535392d6535373032323135633437612e706e67 (1).png" %}
However, in the words of Theodore Sturgeon defending science fiction, "90% of everything is crud." Most of the repositories (or "repos") at GitHub, are simple copies of more important repos. Moreover, most of the projects at GitHub do not have any great importance or an active enough community to be particularly noteworthy for our purposes. Nonetheless, the tiny fraction of these 10 million systems that remain are an enormous number of valuable projects which can be used as building blocks to construct larger systems. In a sense, this explosion of the number of combinable projects represents the fulfilment of the [Unix Philosophy](https://en.wikipedia.org/wiki/Unix_philosophy), which Doug McIlroy has expressed as:
diff --git a/content/posts/2014-12-18-a-complete-list-of-gov-domains.md b/content/posts/2014-12-18-a-complete-list-of-gov-domains.md
index 674beeca9..9dc5f4552 100644
--- a/content/posts/2014-12-18-a-complete-list-of-gov-domains.md
+++ b/content/posts/2014-12-18-a-complete-list-of-gov-domains.md
@@ -19,7 +19,7 @@ tags:
---
diff --git a/content/posts/2015-01-08-an-open-source-tool-for-easier-database-testing.md b/content/posts/2015-01-08-an-open-source-tool-for-easier-database-testing.md
index f7984cd4d..73b21ce47 100644
--- a/content/posts/2015-01-08-an-open-source-tool-for-easier-database-testing.md
+++ b/content/posts/2015-01-08-an-open-source-tool-for-easier-database-testing.md
@@ -34,7 +34,7 @@ of foreign key relationships between tables can make extracting a limited
yet valid subset of its tuples feel like trying to cut a little sweater
out of a big sweater without snipping any yarns.
-![Don't break any yarns.]({{site.baseurl}}/assets/blog/db-testing-tool/cut_sweater.jpg)
+{% image "assets/blog/db-testing-tool/cut_sweater.jpg" "Don't break any yarns." %}
So we've written a new utility,
[rdbms-subsetter](https://github.com/18F/rdbms-subsetter),
@@ -46,7 +46,7 @@ Populating a test database can be as simple as
rdbms-subsetter postgresql://:@/proddb postgresql://:@/testdb 0.001
```
-![rdbms-subsetter in action]({{site.baseurl}}/assets/blog/db-testing-tool/subsetter.png)
+{% image "assets/blog/db-testing-tool/subsetter.png" "rdbms-subsetter in action" %}
It should work against
[any database that SQLAlchemy supports](http://docs.sqlalchemy.org/en/rel_0_9/core/engines.html#supported-databases).
diff --git a/content/posts/2015-01-16-open-source-for-good-government.md b/content/posts/2015-01-16-open-source-for-good-government.md
index db8e12d10..a46ffc78d 100644
--- a/content/posts/2015-01-16-open-source-for-good-government.md
+++ b/content/posts/2015-01-16-open-source-for-good-government.md
@@ -2,7 +2,7 @@
title: Open source for good government
date: '2015-01-16'
layout: post
-image: /assets/blog/join-us/18f_govuk.png
+image: assets/blog/join-us/18f_govuk.png
hero: false
tags:
- open source
@@ -16,7 +16,7 @@ description: 'Organizations like 18F and the U.K.’s Government Digital Service
excerpt: 'Organizations like 18F and the U.K.’s Government Digital Service (GDS) fully embrace open source, and their combined commitment to openness and transparency is transforming the delivery of government digital services in both countries.'
---
-
+{% image "assets/blog/join-us/18f_govuk.png" "18F and GDS logos" %}
A common misconception of open source is that it is just a licence for using software. For individuals and organizations involved with open source projects, it is a philosophy of openness and collaboration embedded in the project from idea to launch. Whether it’s designing an interface, or deploying an application, open source is fundamental to everything we do. Organizations like 18F and the U.K.’s Government Digital Service (GDS) fully embrace open source, and this commitment to openness and transparency is transforming the delivery of government digital services in both countries.
diff --git a/content/posts/2015-02-10-a-story-of-an-agile-workshop.md b/content/posts/2015-02-10-a-story-of-an-agile-workshop.md
index 38623e1e5..a605c621d 100644
--- a/content/posts/2015-02-10-a-story-of-an-agile-workshop.md
+++ b/content/posts/2015-02-10-a-story-of-an-agile-workshop.md
@@ -83,7 +83,7 @@ been hastily brought in. Their bank of workstations was divided by a big
projector — the “stage” upon which the demos would be shown. Other
observers sat in the back of the room.
-![The room: developers on left, the demo area, and product owners on right.]({{site.baseurl}}/assets/blog/agile-workshop/workshop3.JPG)
+{% image "assets/blog/agile-workshop/workshop3.JPG" "The room: developers on left, the demo area, and product owners on right." %}
## The first sprint brought a quick win
diff --git a/content/posts/2015-02-17-three-18f-products-that-will-help-your-workplace.md b/content/posts/2015-02-17-three-18f-products-that-will-help-your-workplace.md
index ba52be8ee..80d4dfd5c 100644
--- a/content/posts/2015-02-17-three-18f-products-that-will-help-your-workplace.md
+++ b/content/posts/2015-02-17-three-18f-products-that-will-help-your-workplace.md
@@ -44,7 +44,7 @@ like — in fact, I recommend it.
The Hub is just what it sounds like — a centralized place where team members share project documentation and more general information about how 18F works.
-![A screenshot of The Hub]({{site.baseurl}}/assets/blog/three-products/hub.png)
+{% image "assets/blog/three-products/hub.png" "A screenshot of The Hub" %}
The Hub is really easy to navigate, and it’s equally easy to update
— anyone can add new information in seconds. Yesterday, for example, I
@@ -68,7 +68,7 @@ Opportunities](https://www.digitalgov.gov/join-digitalgov/open-opportunities-in-
which connects people from across and within government agencies to
collaborate on projects. So far, over 100 projects have been completed.
-![A screenshot of Midas]({{site.baseurl}}/assets/blog/three-products/midas.png)
+{% image "assets/blog/three-products/midas.png" "A screenshot of Midas" %}
Midas can benefit all organizations, but it’s especially useful for
those with distributed teams and whose employees have diverse skill
@@ -89,7 +89,7 @@ designated person collects these Snippets in a CSV file and sends out a
weekly email digest. Snippets subscribers can learn, at a glance, what
all of their colleagues are up to.
- ![A snippet from Mike Bland, describing his workflow]({{site.baseurl}}/assets/blog/snippets/20141215-mbland.jpg)
+{% image "assets/blog/snippets/20141215-mbland.jpg" "A snippet from Mike Bland, describing his workflow" %}
If you don’t have the technical know-how to collect this data in a CSV,
you can have people fill out Snippets via email or on a blog — the point
diff --git a/content/posts/2015-02-24-how-to-use-github-and-the-terminal-a-guide.md b/content/posts/2015-02-24-how-to-use-github-and-the-terminal-a-guide.md
index 53be72479..ab0412b6a 100644
--- a/content/posts/2015-02-24-how-to-use-github-and-the-terminal-a-guide.md
+++ b/content/posts/2015-02-24-how-to-use-github-and-the-terminal-a-guide.md
@@ -53,11 +53,11 @@ If you'd rather not use the script, you can also [follow the detailed instructio
The terminal icon looks like this:
-![Terminal App]({{site.baseurl}}/assets/blog/github-tutorial/terminal.png)
+{% image "assets/blog/github-tutorial/terminal.png" "Terminal App" %}
And you should have a window like this when you open it:
-![Screen shot of blank terminal window]({{site.baseurl}}/assets/blog/github-tutorial/terminal-window.png)
+{% image "assets/blog/github-tutorial/terminal-window.png" "Screen shot of blank terminal window" %}
* Go to Terminal and paste the following `curl --remote-name https://raw.githubusercontent.com/18F/laptop/master/mac` and press enter.
@@ -71,7 +71,7 @@ You're going to see the word "directory" a lot in this tutorial. Directory is an
1. Type `ls`: this will show you everything in the directory where you are currently located. If you type `ls -1` it will list them all in a single column for you. `ls` stands for "**l**i**s**t" and the `-1` tells your computer to list the directory in one column. If you are in your home directory, you will probably see a list in Terminal similar to this screenshot:
-![Screenshot: home directory]({{site.baseurl}}/assets/blog/github-tutorial/w_screenshot1.png)
+{% image "assets/blog/github-tutorial/w_screenshot1.png" "Screenshot: home directory" %}
2. Now type `cd Documents`: this will take you into your Documents directory, if that was one of the options shown when you used the 'ls' command above. `cd` stands for "**c**hange **d**irectory."
3. Type `ls -1` again to see all the files inside your Documents directory.
@@ -87,7 +87,7 @@ I like to put all my GitHub projects in the same directory. So **the first thing
> **Pro tip:** You can always get back to your code directory by typing `cd ~/code`
-![Screenshot: typing in mkdir code]({{site.baseurl}}/assets/blog/github-tutorial/mkdir-code.gif)
+{% image "assets/blog/github-tutorial/mkdir-code.gif" "Screenshot: typing in mkdir code" %}
## Clone a repo on your computer
@@ -105,7 +105,7 @@ In this step we are going to _clone_ the 18f.gsa.gov project to your computer.
* Type in `cd ~/code` and press enter to get to the `code` directory we created earlier.
-![Screenshot: typing in cd code]({{site.baseurl}}/assets/blog/github-tutorial/cd-code.gif)
+{% image "assets/blog/github-tutorial/cd-code.gif" "Screenshot: typing in cd code" %}
* Go to [18f.gsa.gov's GitHub page](https://github.com/18F/18f.gsa.gov) and look on the right side of the page, under the links for "Issues" and "Graphs." You'll see it says "You can clone with HTTPS, SSH, or Subversion." Click on the SSH link and copy the URL (web address) that's in that text box to your clipboard.
@@ -113,7 +113,7 @@ In this step we are going to _clone_ the 18f.gsa.gov project to your computer.
* Type in `git clone ` and then paste the URL that you copied to your clipboard. This is now copying the 18f.gsa.gov repo to your local computer.
-![screenshot: cloning repo]({{site.baseurl}}/assets/blog/github-tutorial/git-clone.gif)
+{% image "assets/blog/github-tutorial/git-clone.gif" "screenshot: cloning repo" %}
> If you run into an error here and **have** run the Laptop script, you need to open and register your GitHub desktop application. The script installs the application, but the application will not auto-generate an SSH key until you log-in with your 18F GitHub account credentials. Just open GitHub desktop and it will guide you as a first time user. You'll validate your local computer with 2FA and then check a few more boxes. After completing that, re-try the `git clone [url]` command.
@@ -127,7 +127,7 @@ On this page you will see a list of files and folders in this project. All of th
You are seeing on the website is another view of files and folders as shown here:
-![Screenshot: 18f.gsa.gov's repo in mac folder]({{site.baseurl}}/assets/blog/github-tutorial/w_screenshot2.png)
+{% image "assets/blog/github-tutorial/w_screenshot2.png" "Screenshot: 18f.gsa.gov's repo in mac folder" %}
If you click on the `branch:staging` button, you can see a list of all of the "branches" that exist on this project. Every time you come directly to [18f.gsa.gov](https://github.com/18F/18f.gsa.gov), it will show you the staging branch because we've made that branch the default.
@@ -135,7 +135,7 @@ Branches are little sandboxes for other people working on the project to prepare
In the next step we're going to create a branch, and later on, when you make a pull request, GitHub will automatically assume you're trying to contribute to the staging branch.
-![Screenshot: showing what the 18f GitHub site looks like]({{site.baseurl}}/assets/blog/github-tutorial/screenshot4.gif)
+{% image "assets/blog/github-tutorial/screenshot4.gif" "Screenshot: showing what the 18f GitHub site looks like" %}
> On the right side, you can also see a list of the existing pull requests and issues. All of the pull requests go to the staging branch. When we merge the pull request to the staging branch, GitHub automatically brings those changes into the project, but does not make them live on https://18f.gsa.gov yet.
@@ -151,7 +151,7 @@ This last command will show you a little bit of information about what you're wo
* _"Your branch is up-to-date with 'origin/staging'"_ means your branch is up to date with the staging branch of the remote location called "origin." A Git repo can have any number of remote locations it can interact with, called "remotes". By default, when you clone a GitHub repo, a remote called "origin" is created that points to the repo on the GitHub website. To view your repo's remote names and their location, type `git remote -v`. The name "origin" is arbitrary. You could rename it to "github" if you wanted to, but we won't do that now.
* _"Nothing to commit / working directory clean"_ means you're completely up to date and haven't made any changes.
-![Screenshot: how to use git status]({{site.baseurl}}/assets/blog/github-tutorial/screenshot5.gif)
+{% image "assets/blog/github-tutorial/screenshot5.gif" "Screenshot: how to use git status" %}
## Build the 18F site
@@ -181,7 +181,7 @@ Okay. Now you're ready to start editing.
**Voila! You can now see all of the files that make up the site.** It should look like this.
-![Screen Shot: All of the files that make up the 18F site]({{site.baseurl}}/assets/blog/github-tutorial/image10.png)
+{% image "assets/blog/github-tutorial/image10.png" "Screen Shot: All of the files that make up the 18F site" %}
> We now want to create a branch, or a sandbox where you can make changes to the website. On this team we always work on branches. This allows you to collaborate with teammates without interfering with other people's existing work.
@@ -191,7 +191,7 @@ Okay. Now you're ready to start editing.
* Type `git status` to make sure you're now on the branch. You should see something that looks like this:
-![Screenshot: git checkout and status]({{site.baseurl}}/assets/blog/github-tutorial/screenshot11.gif)
+{% image "assets/blog/github-tutorial/screenshot11.gif" "Screenshot: git checkout and status" %}
### Edit and commit a blog post
@@ -199,11 +199,11 @@ We're now going to walk you through creating a new blog post for 18f.gsa.gov.
* Type `ls -1F` to see a list of files and folders that make up 18f.gsa.gov's repo.
-![screen shot: ls -F command]({{site.baseurl}}/assets/blog/github-tutorial/image13.png)
+{% image "assets/blog/github-tutorial/image13.png" "screen shot: ls -F command" %}
* Go back to Sublime Text and write your post. Then save your post in the `_posts` directory with the name `2015-02-23-new_post.md` where '2015-02-23' is today's date.
-![Screen shot: Saving post in _posts directory]({{site.baseurl}}/assets/blog/github-tutorial/image14.png)
+{% image "assets/blog/github-tutorial/image14.png" "Screen shot: Saving post in _posts directory" %}
### Adding front matter
@@ -228,7 +228,7 @@ image: /assets/blog/how-to-github/image.jpg
A [complete explanation for the front-matter](https://github.com/18F/18f.gsa.gov/tree/staging/_posts#metadata-explained) can be found on the 18F Blogging Guide. And now you can start writing the text of your blog post on line 16. Say hello! It should look like this:
-![Screen Shot: Adding Front Matter and saving the post]({{site.baseurl}}/assets/blog/github-tutorial/image15.png)
+{% image "assets/blog/github-tutorial/image15.png" "Screen Shot: Adding Front Matter and saving the post" %}
* When you are done writing, save the post by pressing Command + S.
@@ -251,7 +251,7 @@ A [complete explanation for the front-matter](https://github.com/18F/18f.gsa.gov
> You'll see that the file is now listed under changes to be committed.
-![Screen Shot: Git Add Post / Status]({{site.baseurl}}/assets/blog/github-tutorial/screenshot16.gif)
+{% image "assets/blog/github-tutorial/screenshot16.gif" "Screen Shot: Git Add Post / Status" %}
> Well done! At this point, you've told Git that this file should be committed, but you haven't committed anything. So you could work on other things that need to be committed, or you could commit this file right now. We're going to commit right now.
@@ -275,7 +275,7 @@ create mode 100644 _posts/2015-02-23-new-post.md
* Type `git push origin ` (where `` is the name you gave your branch) and then hit enter.
-![Screen shot: git commit]({{site.baseurl}}/assets/blog/github-tutorial/screenshot17.gif)
+{% image "assets/blog/github-tutorial/screenshot17.gif" "Screen shot: git commit" %}
> This uploads your branch and changes to the 18f.gsa.gov project on GitHub.
@@ -283,7 +283,7 @@ create mode 100644 _posts/2015-02-23-new-post.md
> It will look like this:
-![Screen shot: Pull Request]({{site.baseurl}}/assets/blog/github-tutorial/image19.png)
+{% image "assets/blog/github-tutorial/image19.png" "Screen shot: Pull Request" %}
* Click `Compare and Pull Request`. It's a big green button.
@@ -291,17 +291,17 @@ create mode 100644 _posts/2015-02-23-new-post.md
* Then click `Create Pull Request`.
-![Screen Shot: Creating Pull Request]({{site.baseurl}}/assets/blog/github-tutorial/image20.png)
+{% image "assets/blog/github-tutorial/image20.png" "Screen Shot: Creating Pull Request" %}
> This asks 18F to accept your contribution.
-![Screen Shot: 18F receiving contribution from user]({{site.baseurl}}/assets/blog/github-tutorial/image21.png)
+{% image "assets/blog/github-tutorial/image21.png" "Screen Shot: 18F receiving contribution from user" %}
> You always want to make sure what's on your local machine is as up to date as it can be. So whenever you return to the terminal, make the following a habit:
* Type `git checkout staging` followed by `git pull` again, to make sure your version of the staging branch is current.
-![screenshot: checkout and pull]({{site.baseurl}}/assets/blog/github-tutorial/screenshot22.gif)
+{% image "assets/blog/github-tutorial/screenshot22.gif" "screenshot: checkout and pull" %}
After you type `git pull` one of two things might happen:
diff --git a/content/posts/2015-02-25-We-Are-Hiring.md b/content/posts/2015-02-25-We-Are-Hiring.md
index 1613c3f09..7a29e6ace 100644
--- a/content/posts/2015-02-25-We-Are-Hiring.md
+++ b/content/posts/2015-02-25-We-Are-Hiring.md
@@ -30,7 +30,7 @@ We’re transforming government from the inside out, creating cultural change by
Whether you’re near an 18F office in Washington DC, San Francisco, Chicago, or New York, or you’re closer to some of our teammates in Seattle, Portland, San Diego, Austin, Tucson, Dayton, Raleigh, or Philadelphia, we want to hear from you!
-![A map of 18F team members]({{site.baseurl}}/assets/blog/were-hiring/map.png)
+{% image "assets/blog/were-hiring/map.png" "A map of 18F team members" %}
Our rapidly growing team is home to a variety of roles, including these:
diff --git a/content/posts/2015-02-26-Five-Ways-To-Turn-A-Bad-Idea-Into-A-Great-One.md b/content/posts/2015-02-26-Five-Ways-To-Turn-A-Bad-Idea-Into-A-Great-One.md
index d9e5258ab..e9f07c893 100644
--- a/content/posts/2015-02-26-Five-Ways-To-Turn-A-Bad-Idea-Into-A-Great-One.md
+++ b/content/posts/2015-02-26-Five-Ways-To-Turn-A-Bad-Idea-Into-A-Great-One.md
@@ -31,7 +31,7 @@ As Steve himself describes in a post he wrote for [Core77](http://www.core77.com
“Creative activities often follow a double-hump model. At first you'll hit all the obvious ideas. These aren't a waste of time; sometimes the obvious ideas have been neglected and you can treat those as low-hanging fruit: obvious, easy to implement, incremental improvement. But you'll find that you run out of steam with those ideas. Like the false ending in a '80s rock song, don't think this fadeout means it's time to start applauding. There's still more. Push on, and this is when you get to the transgressive, weird, crazy and sometimes innovative ideas. That's the place you want to get to, where you are truly butting up against the edges of what's allowable.”
-![The double-hump model]({{site.baseurl}}/assets/blog/portigal-event-image/2humps.jpg)
+{% image "assets/blog/portigal-event-image/2humps.jpg" "The double-hump model" %}
## A safe space is necessary for top-notch brainstorming
diff --git a/content/posts/2015-02-27-making-procurement-easier-some-questions-for-developer-kaitlin-devine.md b/content/posts/2015-02-27-making-procurement-easier-some-questions-for-developer-kaitlin-devine.md
index cc347aaf2..ec4ad0f6d 100644
--- a/content/posts/2015-02-27-making-procurement-easier-some-questions-for-developer-kaitlin-devine.md
+++ b/content/posts/2015-02-27-making-procurement-easier-some-questions-for-developer-kaitlin-devine.md
@@ -46,7 +46,7 @@ government?**
Probably my elevator pitch would be that it’s an Angie’s List for
government contractors.
-![Screen: Discovery Homepage]({{site.baseurl}}/assets/blog/discovery-launch/discovery-intro.gif)
+{% image "assets/blog/discovery-launch/discovery-intro.gif" "Screen: Discovery Homepage" %}
**So it’s a way for government contractors to find out information?**
diff --git a/content/posts/2015-03-02-cos-post.md b/content/posts/2015-03-02-cos-post.md
index b08bc1a82..7e689bab3 100644
--- a/content/posts/2015-03-02-cos-post.md
+++ b/content/posts/2015-03-02-cos-post.md
@@ -15,7 +15,7 @@ description: "When the Employment and Training Administration’s CareerOneStop
hero: false
---
-!["The CareerOneStop homepage"]({{site.baseurl}}/assets/img/cos.png)
+{% image "assets/img/cos.png" ""The CareerOneStop homepage"" %}
When the [Employment and Training Administration’s](http://www.doleta.gov/) [CareerOneStop](http://www.careeronestop.org) team set out to redesign the career, training, and job resources sections of the site, they didn’t immediately begin rewriting code. Instead, they embraced a user-centered approach that focused on the user experience (UX). In a general sense, focusing on UX means taking a step back to learn about users’ core needs and preferences before making changes to a product or service.
diff --git a/content/posts/2015-03-04-annoucing-oasis-discovery-making-market-research-easier.md b/content/posts/2015-03-04-annoucing-oasis-discovery-making-market-research-easier.md
index 5d54b8e0e..2b0d7cb98 100644
--- a/content/posts/2015-03-04-annoucing-oasis-discovery-making-market-research-easier.md
+++ b/content/posts/2015-03-04-annoucing-oasis-discovery-making-market-research-easier.md
@@ -22,7 +22,7 @@ Discovery will allow federal acquisition personnel to conduct initial market res
This first release is geared for use with GSA’s newly released [OASIS vehicle](http://www.federaltimes.com/story/government/acquisition/gsa-gwac/2014/12/17/oasis-signals-a-new-era-for-gsa/20549171/). Eventually, 18F hopes to make additional vehicles and resources available through Discovery, as well.
-![Screen: Discovery Homepage]({{site.baseurl}}/assets/blog/discovery-launch/discovery-intro.gif)
+{% image "assets/blog/discovery-launch/discovery-intro.gif" "Screen: Discovery Homepage" %}
### Who is it for?
@@ -37,7 +37,7 @@ Discovery was built with *user-centered* processes, meaning we conducted a signi
The screenshot below shows how the Discovery team tracked user input/research. Significant findings were captured on a Discovery Research Trello board, and then were fed back into the main project Trello board as new project tasks, which could then be explored through team and client design exercises (e.g., design studios, sketching).
-![Trello Board for Discovery Research Process]({{site.baseurl}}/assets/blog/discovery-launch/trelloboard.png)
+{% image "assets/blog/discovery-launch/trelloboard.png" "Trello Board for Discovery Research Process" %}
### How we used open source with open data
diff --git a/content/posts/2015-03-06-ux-lessons-learned-from-a-procurement-project.md b/content/posts/2015-03-06-ux-lessons-learned-from-a-procurement-project.md
index 58ebc125e..aff2eeb6d 100644
--- a/content/posts/2015-03-06-ux-lessons-learned-from-a-procurement-project.md
+++ b/content/posts/2015-03-06-ux-lessons-learned-from-a-procurement-project.md
@@ -135,7 +135,7 @@ there wasn’t one place to get that information.
That’s where Discovery fits in.
-![Screen: Discovery Homepage]({{site.baseurl}}/assets/blog/discovery-launch/discovery-intro.gif)
+{% image "assets/blog/discovery-launch/discovery-intro.gif" "Screen: Discovery Homepage" %}
**How did you determine that Discovery was the tool that you needed to
build?**
diff --git a/content/posts/2015-03-11-onet-today-and-beyond.md b/content/posts/2015-03-11-onet-today-and-beyond.md
index c20f395d4..9772d6c43 100644
--- a/content/posts/2015-03-11-onet-today-and-beyond.md
+++ b/content/posts/2015-03-11-onet-today-and-beyond.md
@@ -54,7 +54,7 @@ that have existed (and will continue to exist) in the medium term.
Examples of some such occupations include firefighter, teacher, and
lawyer, to name a few.
-![The O*Net Content model takes many sources to identify detailed occupations.]({{site.baseurl}}/assets/blog/onet/image01.jpg)
+{% image "assets/blog/onet/image01.jpg" "The O*Net Content model takes many sources to identify detailed occupations." %}
*Fig. 1: O\*NET content model*
@@ -224,7 +224,7 @@ A public-private partnership that produces a Skills Market Platform
(SMP) (Fig. 2), which is an open, dynamic, growing, standards-based,
public-facing platform for skills data.
-![Reference architecture for a skills market platform]({{site.baseurl}}/assets/blog/onet/image00.png)
+{% image "assets/blog/onet/image00.png" "Reference architecture for a skills market platform" %}
*Fig. 2: reference architecture for a Skills Market Platform (SMP)*
@@ -290,4 +290,4 @@ Data Standard. Donate some programming and design cycles to implementing
the Skills Network Protocol and or the Skills Innovation Layer. Help
change the world as we know it.
-[![Send an email to get involved.]({{site.baseurl}}/assets/blog/onet/image02.gif)](mailto:openinnovationhrs@dol.gov)
+[{% image "assets/blog/onet/image02.gif" "Send an email to get involved." %}](mailto:openinnovationhrs@dol.gov)
diff --git a/content/posts/2015-03-17-does-18f-pass-the-bechdel-test-for-tech.md b/content/posts/2015-03-17-does-18f-pass-the-bechdel-test-for-tech.md
index 97a913cdd..d6dac6c4e 100644
--- a/content/posts/2015-03-17-does-18f-pass-the-bechdel-test-for-tech.md
+++ b/content/posts/2015-03-17-does-18f-pass-the-bechdel-test-for-tech.md
@@ -25,7 +25,7 @@ original Bechdel test, which was created by writer and graphic novelist
Alison Bechdel. The Bechdel test was originally designed to evaluate
works of fiction. A work passed if at least one woman had a conversation with another woman about something other than a man.
-![The 18F team]({{site.baseurl}}/assets/blog/bechdel/team.jpg)
+{% image "assets/blog/bechdel/team.jpg" "The 18F team" %}
We decided to see how many 18F projects pass this modified test. To
pass, a project had to have at least one function written by a woman dev
diff --git a/content/posts/2015-03-19-18f-by-the-numbers.md b/content/posts/2015-03-19-18f-by-the-numbers.md
index 49253f86e..6ace6e4c4 100644
--- a/content/posts/2015-03-19-18f-by-the-numbers.md
+++ b/content/posts/2015-03-19-18f-by-the-numbers.md
@@ -18,7 +18,7 @@ hero: false
Today, we’re celebrating our first anniversary. We wanted to take a look at some of the numbers that have helped define 18F during our first year.
-![Infographic showing 18F's first-year progress by the numbers]({{site.baseurl}}/assets/blog/agile-day/18fbythenumbers.png)
+{% image "assets/blog/agile-day/18fbythenumbers.png" "Infographic showing 18F's first-year progress by the numbers" %}
## By the projects
diff --git a/content/posts/2015-03-31-focus-on-accessibility.md b/content/posts/2015-03-31-focus-on-accessibility.md
index 7b254155a..12d755615 100644
--- a/content/posts/2015-03-31-focus-on-accessibility.md
+++ b/content/posts/2015-03-31-focus-on-accessibility.md
@@ -16,7 +16,7 @@ Last week, we published [this post](https://18f.gsa.gov/2015/03/24/making-twitte
To increase the accessibility of the images we Tweet, [@18F](https://twitter.com/18f) has started replying to photo-centric Tweets with *a description of what’s in the photo*. Noting this, our followers offered additional suggestions about how we can increase the accessibility of our Tweets. We’d like to thank all of our followers who offered us suggestions, and encourage you to share suggestions, if you have them.
-![Tweet describing a tweet featuring an image]({{site.baseurl}}/assets/blog/accessibility/pictureintweet.png)
+{% image "assets/blog/accessibility/pictureintweet.png" "Tweet describing a tweet featuring an image" %}
Accessibility is central to our work here at 18F. In a very broad sense, all of our work is driven by a desire to improve the accessibility of federal resources and knowledge. Consider, for example, some of the work 18F is undertaking. Collaborating with USCIS (United States Citizenship and Immigration Services) and others, our team is helping to redesign the USCIS user experience and the content for websites related to immigration and citizenship. In particular, this team is making sure that the recommended path through the sites, along with the sites’ content, is understandable to diverse audiences, thereby making the information more accessible to everyone.
diff --git a/content/posts/2015-04-03-how-to-welcome-new-coders-to-a-civic-hackathon.md b/content/posts/2015-04-03-how-to-welcome-new-coders-to-a-civic-hackathon.md
index 4b34d7205..c7b4c9bc0 100644
--- a/content/posts/2015-04-03-how-to-welcome-new-coders-to-a-civic-hackathon.md
+++ b/content/posts/2015-04-03-how-to-welcome-new-coders-to-a-civic-hackathon.md
@@ -106,7 +106,7 @@ skills or interests people have. Listing interests on a nametag also
helps facilitate conversations between people who may be meeting for the
first time.
-![Image: nametag from recent hackathon showing color-coded stickers for devs, designers, and content strategists]({{site.baseurl}}/assets/blog/new-to-hackathon/nametag.jpg)
+{% image "assets/blog/new-to-hackathon/nametag.jpg" "Image: nametag from recent hackathon showing color-coded stickers for devs, designers, and content strategists" %}
## Clearly label issues on GitHub with ways people can help
diff --git a/content/posts/2015-04-07-icymi-a11yhack-accessibility-awareness-hackathon.md b/content/posts/2015-04-07-icymi-a11yhack-accessibility-awareness-hackathon.md
index ccf6c38e4..94ded51c5 100644
--- a/content/posts/2015-04-07-icymi-a11yhack-accessibility-awareness-hackathon.md
+++ b/content/posts/2015-04-07-icymi-a11yhack-accessibility-awareness-hackathon.md
@@ -54,9 +54,9 @@ Federation of the Blind](https://nfb.org/) could come and help us
out. Their insight was inspiring and we got a lot of great feedback from
them,” said Nick Bristow, one of the event organizers.
-![A tweet from Accessibility Partner: "Having my CAPTCHA mind blown #a11yhack"]({{site.baseurl}}/assets/blog/a11yhack/a11ytweet1.png)
+{% image "assets/blog/a11yhack/a11ytweet1.png" "A tweet from Accessibility Partner: “Having my CAPTCHA mind blown #a11yhack”" %}
-![A tweet from Rebecca Williams: "Accessibility advices like, 'don't use read more links, be more descriptive' are also good writing/life advice. #a11yhack"]({{site.baseurl}}/assets/blog/a11yhack/allytweet2.png)
+{% image "assets/blog/a11yhack/allytweet2.png" "A tweet from Rebecca Williams: “Accessibility advices like, 'don't use read more links, be more descriptive' are also good writing/life advice. #a11yhack”" %}
“The hackathon itself was also successful. [Megan
Smith](https://obamawhitehouse.archives.gov/administration/eop/ostp/about/leadershipstaff/smith)
@@ -79,7 +79,7 @@ overlook if you don't need it. But I hope that the hackathon helped
raise awareness and get the message across that accessibility is
something we all can improve.”
-[![The hackpad, we've archived this as a markdown file on the hackathon's website. Click this link to read the contents.]({{site.baseurl}}/assets/blog/a11yhack/hackpad.png)](https://18f.github.io/hackathons/a11yhack/hackpad-snapshot/)
+[{% image "assets/blog/a11yhack/hackpad.png" "The hackpad, we've archived this as a markdown file on the hackathon's website. Click this link to read the contents." %}](https://18f.github.io/hackathons/a11yhack/hackpad-snapshot/)
Jackie Kazil, another organizer, said several aspects of the gathering
stood out to her, including alternatives to Web practices such as video
@@ -102,7 +102,7 @@ it’s not acceptable, has to be revisited, is not efficient,” she said,
adding that “bringing the accessibility consideration earlier into the
process is going to help improve the experience.”
-![The crowd at a11yhack]({{site.baseurl}}/assets/blog/a11yhack/a11yhack.jpg)
+{% image "assets/blog/a11yhack/a11yhack.jpg" "The crowd at a11yhack" %}
Photo: Jameson Dempesy
Overall, everyone in attendance seemed to have a great time networking
diff --git a/content/posts/2015-04-09-flexibility-when-releasing-a-new-product-peace-corps-new-donation-platform.md b/content/posts/2015-04-09-flexibility-when-releasing-a-new-product-peace-corps-new-donation-platform.md
index ee6904f13..b5580ba0b 100644
--- a/content/posts/2015-04-09-flexibility-when-releasing-a-new-product-peace-corps-new-donation-platform.md
+++ b/content/posts/2015-04-09-flexibility-when-releasing-a-new-product-peace-corps-new-donation-platform.md
@@ -48,7 +48,7 @@ user found a compelling story, they could select a donation amount
in-line, turning what used to be a four-step process into a single
click.
-![screenshot: workflow of donation pathways on Peace Corps site]({{site.baseurl}}/assets/blog/peacecorps/image03.png)
+{% image "assets/blog/peacecorps/image03.png" "screenshot: workflow of donation pathways on Peace Corps site" %}
Our ideal interface would have been a seamless user experience, but once
scoped would have required a heavy lift from our front end and
@@ -97,7 +97,7 @@ kicked out every five minutes while other pages are generated hourly.
With several machines primed and auto-scaling capability, we expected to
handle dozens of requests per second.
-![screenshot of donation platform for Peace Corps birding for conservation project]({{site.baseurl}}/assets/blog/peacecorps/image00.png)
+{% image "assets/blog/peacecorps/image00.png" "screenshot of donation platform for Peace Corps birding for conservation project" %}
After reviewing the numbers from Peace Corps' media blitz in early
March, we know that part of our calculus was correct — S3 and CloudFront
@@ -128,7 +128,7 @@ legacy system also provided a search engine, allowing users to find
funds based on keywords. One of these features would make it to launch
but the other would not.
-![Screenshot: product backlog for Peace Corps sprints]({{site.baseurl}}/assets/blog/peacecorps/image02.png)
+{% image "assets/blog/peacecorps/image02.png" "Screenshot: product backlog for Peace Corps sprints" %}
We pushed hard to cut as many fields as possible from the donor form,
diff --git a/content/posts/2015-04-28-intersection-of-art-and-technology.md b/content/posts/2015-04-28-intersection-of-art-and-technology.md
index 7ee1fcdc3..94e0352bc 100644
--- a/content/posts/2015-04-28-intersection-of-art-and-technology.md
+++ b/content/posts/2015-04-28-intersection-of-art-and-technology.md
@@ -27,7 +27,7 @@ At this point, you may be thinking, “Why is someone writing about Bjӧrk on th
Our work at 18F is informed by both our users and the experiences they have with the websites and applications we work on. As designers and developers, we help merge the user experiences by using art and technology to [create useful, engaging, and delightful user-centered design](https://18f.gsa.gov/2014/09/25/design-studio-onrr/). Artists help people see and experience the world around them in new or different ways. Similarly, our roles are to help government, and the American public, see, experience, and build technology in a different way.
-![Screenshot of analytics.gsa.gov]({{site.baseurl}}/assets/blog/art-tech/dap-dashboard.png)
+{% image "assets/blog/art-tech/dap-dashboard.png" "Screenshot of analytics.gsa.gov" %}
One way to help people process technology differently is by designing visualizations that allow people to quickly comprehend large amounts of data. Recently, [18F helped launch analytics.gsa.gov](https://18f.gsa.gov/2015/03/19/how-we-built-analytics-usa-gov/) to display the web traffic from various federal government websites. The analytics site serves as a way for the public and government officials to easily see which federal government sites people visit the most. This viewpoint displays highly valuable and relevant information that aids in making impactful and long-term content decisions that affect the public. It also helps federal employees make targeted decisions on how to approach and then decide how to make user interactions more friendly on mobile.
diff --git a/content/posts/2015-04-29-18f-how-we-write.md b/content/posts/2015-04-29-18f-how-we-write.md
index 3dda2f12d..8b8cf1edf 100644
--- a/content/posts/2015-04-29-18f-how-we-write.md
+++ b/content/posts/2015-04-29-18f-how-we-write.md
@@ -19,7 +19,7 @@ We collaborate on much of what we do at 18F, from the way we work on code to the
This collaboration begins during the generative stage of the drafting process. Anyone on the 18F team can suggest an idea for a blog post. We collect these ideas as issues in a private GitHub repository and open each issue up to feedback from the entire team. For example, Sarah Allen, a developer at 18F, suggested writing the post you are reading right now:
-![Screen shot of a GitHub thread from Sarah Allen: IDEA: we should write a blog post about how we create transparency and alignment within our organization with our blogging process, where anyone on the whole team can chime in on blog posts I was telling some friends about our process and how we use github (or used to?) tagging drafts with idea, draft, ready and approved -- I don't see these labels now. I wanted to share our README from this repo, but its private. I would love to have a written reference to our process -- I think other orgs could learn from it, and would help prospective candidates understand how we work.]({{site.baseurl}}/assets/blog/how-we-write/sarah.png)
+{% image "assets/blog/how-we-write/sarah.png" "Screen shot of a GitHub thread from Sarah Allen: IDEA: we should write a blog post about how we create transparency and alignment within our organization with our blogging process, where anyone on the whole team can chime in on blog posts I was telling some friends about our process and how we use github (or used to?) tagging drafts with idea, draft, ready and approved -- I don't see these labels now. I wanted to share our README from this repo, but its private. I would love to have a written reference to our process -- I think other orgs could learn from it, and would help prospective candidates understand how we work." %}
This isn’t the only way we come up with our post ideas. Sometimes, we’ll overhear a great conversation — or witness one in our chat program — and realize that it would make an equally great post. In these cases, one of us will reach out to the conversation participants and ask if they’d like to write a post based on their discussion. If they’re not free or willing to write it, a member of the editorial team will offer to create a GitHub issue and work up the first draft.
@@ -32,7 +32,7 @@ We also ask our teammates if they have thoughts on a post date and who, in addit
Sometimes we hold posts to coincide with a product launch. In both of these cases, we ask the project leads for their thoughts and make sure that they’re added to the GitHub issue, as well. This ensures that all the relevant information is collected in one place, and makes it easy for anyone who needs to weigh in before publication to do so.
-![Screen shot of another GitHub thread: Kate: Sarah, Also love this idea — when would you like to publish?]({{site.baseurl}}/assets/blog/how-we-write/kate2.png)
+{% image "assets/blog/how-we-write/kate2.png" "Screen shot of another GitHub thread: Kate: Sarah, Also love this idea — when would you like to publish?" %}
In addition to the editorial team, anyone from 18F is encouraged to enter the GitHub thread and offer feedback or suggest copy for the actual blog post itself. Even if someone may not have time to write an entire post, they can contribute and receive a byline for their efforts. This allows our teammates who are busy coding or designing projects to write about their process and work, without requiring them to sit down and write hundreds of words. (We also have a weekly blog “huddle” with the editorial team, where anyone from 18F can talk about works-in-progress, ask for help, or find collaborators.)
diff --git a/content/posts/2015-05-12-announcing-the-calc-tool.md b/content/posts/2015-05-12-announcing-the-calc-tool.md
index 71d33ee86..b2dcab4d4 100644
--- a/content/posts/2015-05-12-announcing-the-calc-tool.md
+++ b/content/posts/2015-05-12-announcing-the-calc-tool.md
@@ -25,7 +25,7 @@ conduct market research and price analysis for professional labor
categories across a database of contract awarded prices for 48,000 labor
categories from more than 5,000 recent GSA contracts.
-![Gif of a sample CALC search]({{site.baseurl}}/assets/blog/calc-announcement/calc_demo.gif)
+{% image "assets/blog/calc-announcement/calc_demo.gif" "Gif of a sample CALC search" %}
Before CALC, contracting officers had to sift through paper contracts or
comb through GSA Advantage files to stitch together a picture of fair
diff --git a/content/posts/2015-05-14-18Fpages.md b/content/posts/2015-05-14-18Fpages.md
index cf8fcf763..1fac3a2b4 100644
--- a/content/posts/2015-05-14-18Fpages.md
+++ b/content/posts/2015-05-14-18Fpages.md
@@ -48,7 +48,7 @@ for our 18f.gsa.gov technical stack, proved surprisingly
straightforward, and now we’re happy to announce
[https://pages.18f.gov/](https://pages.18f.gov/), aka “18F Pages.”
-![Screenshot of 18F Pages site]({{site.baseurl}}/assets/blog/18F-Pages/18Fpages.jpg)
+{% image "assets/blog/18F-Pages/18Fpages.jpg" "Screenshot of 18F Pages site" %}
While the site is still in its earliest stages, we will be adding more
content to it over time, as our team generates documentation that we
diff --git a/content/posts/2015-05-18-myusa.md b/content/posts/2015-05-18-myusa.md
index 48dd812a6..9b4696d08 100644
--- a/content/posts/2015-05-18-myusa.md
+++ b/content/posts/2015-05-18-myusa.md
@@ -15,7 +15,7 @@ image: /assets/blog/myusa/myusa.jpg
hero: false
---
-[![MyUsa Screenshot]({{site.baseurl}}/assets/blog/myusa/myusa.jpg)](https://my.usa.gov/)
+[{% image "assets/blog/myusa/myusa.jpg" "MyUsa Screenshot" %}](https://my.usa.gov/)
Quick! How many times did you visit a government website during the past
diff --git a/content/posts/2015-05-19-five-questions-with-dan-brown.md b/content/posts/2015-05-19-five-questions-with-dan-brown.md
index f021f7001..0ec013717 100644
--- a/content/posts/2015-05-19-five-questions-with-dan-brown.md
+++ b/content/posts/2015-05-19-five-questions-with-dan-brown.md
@@ -19,7 +19,9 @@ image: /assets/blog/speaker-series/d-brown.jpg
hero: false
---
-
+
Dan Brown, co-founder of D.C.-based design firm [EightShapes](http://eightshapes.com/) and author of “[Communicating Design](http://www.amazon.com/Communicating-Design-Developing-Documentation-Planning/dp/0321712463)” and “[Designing Together](http://www.amazon.com/Designing-Together-collaboration-management-professionals/dp/0321918630/ref=sr_1_1?s=books&ie=UTF8&qid=1431552817&sr=1-1&keywords=Designing+Together+Dan+Brown),” is fascinated by conflict — but not in the way you might think. Brown has spent years studying how and why conflict arises in the workplace, its centrality to good design, the differences between healthy and unhealthy conflict, and more.
diff --git a/content/posts/2015-05-21-TockingTime.md b/content/posts/2015-05-21-TockingTime.md
index 382aefeed..697f5808c 100644
--- a/content/posts/2015-05-21-TockingTime.md
+++ b/content/posts/2015-05-21-TockingTime.md
@@ -38,7 +38,7 @@ our own accounting and for the taxpayers who support our work.
For a long time, our internal time tracking looked something like this:
-![Old time tracking screenshot]({{site.baseurl}}/assets/blog/tockingtime/tock02.jpg)
+{% image "assets/blog/tockingtime/tock02.jpg" "Old time tracking screenshot" %}
Every week, our operations team dutifully created a giant Google Sheets
spreadsheet and shared it with the entire team. As we grew, the number
@@ -88,7 +88,7 @@ internal platform as a service and flex our Python muscles.
The first prototype took about day to build and deploy. We built it
entirely in the open (see our [GitHub repository](https://github.com/18f/tock)) and immediately put it online for the team to test.
-![Prototype screenshot]({{site.baseurl}}/assets/blog/tockingtime/tock03.jpg)
+{% image "assets/blog/tockingtime/tock03.jpg" "Prototype screenshot" %}
*The first iteration of Tock*
At the core, this is a very simple Django site. We have four main
@@ -139,7 +139,7 @@ grew rapidly as people tried to strike the right balance between
capturing work accurately and forcing users to browse a long list of
random things:
-![List screenshot]({{site.baseurl}}/assets/blog/tockingtime/tock00.jpg)
+{% image "assets/blog/tockingtime/tock00.jpg" "List screenshot" %}
*So many items!*
We fixed this, in part, by providing an auto-select based on
@@ -147,7 +147,7 @@ We fixed this, in part, by providing an auto-select based on
designed specifically for this purpose. Now, Tock users can search by
either the project or partner agency name when selecting a line item:
-![Line screenshot]({{site.baseurl}}/assets/blog/tockingtime/tock01.jpg)
+{% image "assets/blog/tockingtime/tock01.jpg" "Line screenshot" %}
### The future of time
diff --git a/content/posts/2015-05-27-dan-brown-conflict-in-design.md b/content/posts/2015-05-27-dan-brown-conflict-in-design.md
index 0e1b39616..d795bb69c 100644
--- a/content/posts/2015-05-27-dan-brown-conflict-in-design.md
+++ b/content/posts/2015-05-27-dan-brown-conflict-in-design.md
@@ -47,7 +47,7 @@ During his talk, Brown asked audience members to draw “situation” cards from
The pattern cards offer techniques for unsticking situations. For example, “make a plan,” or “offer a sneak peek.”
-![Pattern and situation cards]({{site.baseurl}}/assets/blog/speaker-series/pattern-situation.jpg)
+{% image "assets/blog/speaker-series/pattern-situation.jpg" "Pattern and situation cards" %}
The third piece of the puzzle, “trait” cards, are useful for self-reflection and understanding characteristics. “Dogmatism,” for example, can predict conflicts and the techniques that best resolve them.
diff --git a/content/posts/2015-05-28-18F-guides.md b/content/posts/2015-05-28-18F-guides.md
index 35125be30..9bab4e166 100644
--- a/content/posts/2015-05-28-18F-guides.md
+++ b/content/posts/2015-05-28-18F-guides.md
@@ -27,7 +27,7 @@ basics. [18F Guides](https://pages.18f.gov/guides/) aims to fill that
role for our young and growing team, and we hope it may be of use to
others as well.
-![18F Guides homepage]({{site.baseurl}}/assets/blog/18F-guides/18F-guides.png)
+{% image "assets/blog/18F-guides/18F-guides.png" "18F Guides homepage" %}
## Coalescing best practices
diff --git a/content/posts/2015-06-02-taking-the-pulse-of-the-federal-governments-web-presence.md b/content/posts/2015-06-02-taking-the-pulse-of-the-federal-governments-web-presence.md
index 183725435..f1ab1d2d7 100644
--- a/content/posts/2015-06-02-taking-the-pulse-of-the-federal-governments-web-presence.md
+++ b/content/posts/2015-06-02-taking-the-pulse-of-the-federal-governments-web-presence.md
@@ -22,7 +22,7 @@ The U.S. federal government is launching a new project to monitor how it's doing
A sort of health monitor for the U.S. government's websites, it's called **[Pulse](https://pulse.cio.gov)**, and you can find it at **[pulse.cio.gov](https://pulse.cio.gov)**.
-[![pulse homepage]({{site.baseurl}}/assets/blog/pulse/pulse.png)](https://pulse.cio.gov)
+[{% image "assets/blog/pulse/pulse.png" "pulse homepage" %}](https://pulse.cio.gov)
[Pulse](https://pulse.cio.gov) is a lightweight dashboard that uses the [official .gov domain list](https://github.com/GSA/data/blob/gh-pages/dotgov-domains/2015-03-15-federal.csv) to measure two things:
@@ -35,7 +35,7 @@ The project will hopefully expand over time to measure more best practices and m
## Background
-[![pulse screenshot of analytics]({{site.baseurl}}/assets/blog/pulse/analytics-agencies.png)](https://pulse.cio.gov/analytics/agencies/)
+[{% image "assets/blog/pulse/analytics-agencies.png" "pulse screenshot of analytics" %}](https://pulse.cio.gov/analytics/agencies/)
Pulse is a collaboration between 18F and the [Office of Government-wide Policy](http://www.gsa.gov/portal/content/104550) (OGP).
@@ -45,7 +45,7 @@ Like 18F, OGP is an office of the U.S. General Services Administration. Among ma
## How pulse.cio.gov works
-[![pulse screenshot of https]({{site.baseurl}}/assets/blog/pulse/https-agencies.png)](https://pulse.cio.gov/https/agencies/)
+[{% image "assets/blog/pulse/https-agencies.png" "pulse screenshot of https" %}](https://pulse.cio.gov/https/agencies/)
Pulse was created in around six weeks. We built the project [in the open from Day 1](https://github.com/18f/pulse), obtained our domain name and relevant cybersecurity approvals in our first couple weeks, and released new versions of the dashboard to [pulse.cio.gov](https://pulse.cio.gov) early and often throughout the process.
@@ -66,7 +66,7 @@ The process is not fully automated, and so Pulse isn't updated every day. There'
## Measuring participation in the Digital Analytics Program
-[![pulse screenshot of analytics homepage]({{site.baseurl}}/assets/blog/pulse/analytics.png)](https://pulse.cio.gov/analytics/domains/)
+[{% image "assets/blog/pulse/analytics.png" "pulse screenshot of analytics homepage" %}](https://pulse.cio.gov/analytics/domains/)
The [Digital Analytics Program](https://www.digitalgov.gov/services/dap/) is a free, shared web analytics service for U.S. federal agencies.
@@ -74,13 +74,13 @@ To participate, agencies place some JavaScript on their websites that report to
Access to the account is shared within the federal government, and much of its data is shared publicly on [analytics.usa.gov](https://analytics.usa.gov/). The Digital Analytics Program also regularly publishes a list of around 4,000 participating websites that have reported visitor data in the preceding 2 weeks.
-[![pulse screenshot of analytics domains]({{site.baseurl}}/assets/blog/pulse/analytics-domains.png)](https://pulse.cio.gov/analytics/domains/)
+[{% image "assets/blog/pulse/analytics-domains.png" "pulse screenshot of analytics domains" %}](https://pulse.cio.gov/analytics/domains/)
Pulse measures participation in the simplest way possible: by comparing the .gov domain list to the list of participating websites published by the Digital Analytics Program. It's not rocket science, but in the future we'd like to automate this process using the [`analytics-reporter`](https://github.com/18F/analytics-reporter) tool [we created for analytics.usa.gov](https://18f.gsa.gov/2015/03/19/how-we-built-analytics-usa-gov/).
## Measuring HTTPS in .gov
-[![pulse screenshot of https homepage]({{site.baseurl}}/assets/blog/pulse/https.png)](https://pulse.cio.gov/https/domains/)
+[{% image "assets/blog/pulse/https.png" "pulse screenshot of https homepage" %}](https://pulse.cio.gov/https/domains/)
Enforcing strong HTTPS is an [important baseline](https://18f.gsa.gov/2014/11/13/why-we-use-https-in-every-gov-website-we-make/) for government websites, and is in the [process](https://blog.mozilla.org/security/2015/04/30/deprecating-non-secure-http/) of [becoming](https://www.chromium.org/Home/chromium-security/marking-http-as-non-secure) the baseline for the web at large.
@@ -88,7 +88,7 @@ HTTPS is simple enough to detect, but characterizing HTTPS support for a domain,
We lean heavily on the open source [`site-inspector`](https://github.com/benbalter/site-inspector), a command line tool written in Ruby. `site-inspector` measures various useful things about websites, and was originally written by Ben Balter to [analyze .gov domains](http://ben.balter.com/2015/05/11/third-analysis-of-federal-executive-dotgovs/).
-[![pulse screenshot of https domains]({{site.baseurl}}/assets/blog/pulse/https-domains.png)](https://pulse.cio.gov/https/domains/)
+[{% image "assets/blog/pulse/https-domains.png" "pulse screenshot of https domains" %}](https://pulse.cio.gov/https/domains/)
To get the precision we wanted, we needed to take into account several subtle things about domains:
diff --git a/content/posts/2015-06-08-data-act-data-act-explainer.md b/content/posts/2015-06-08-data-act-data-act-explainer.md
index f0b4ad407..e9cd20f16 100644
--- a/content/posts/2015-06-08-data-act-data-act-explainer.md
+++ b/content/posts/2015-06-08-data-act-data-act-explainer.md
@@ -50,7 +50,7 @@ appropriation to an actual payment. These systems don’t have a common
way to tie money back to specific programs and projects, and that’s what
the DATA Act proposes to fix.
-[![Diagram of government appropriation reporting]({{site.baseurl}}/assets/blog/data-act-implementation/data-act-reporting.jpg)](http://www.datacoalition.org/what-is-data-transparency/data-act/)
+[{% image "assets/blog/data-act-implementation/data-act-reporting.jpg" "Diagram of government appropriation reporting" %}](http://www.datacoalition.org/what-is-data-transparency/data-act/)
*Image courtesy of the [Data Transparency
Coalition](http://www.datacoalition.org/what-is-data-transparency/data-act/)*
@@ -70,7 +70,7 @@ several different initiatives, the Department may allocate those dollars
to more specific buckets like Pell grants, work-study, and scholarships
for veterans’ dependents.
-![Diagram of account labeling]({{site.baseurl}}/assets/blog/data-act-implementation/data-act-labels.jpg)
+{% image "assets/blog/data-act-implementation/data-act-labels.jpg" "Diagram of account labeling" %}
When Treasury pays money to a recipient of student financial aid, it
debits the money from the high-level $30 billion account. The specifics
diff --git a/content/posts/2015-06-11-18f-at-national-civic-hacking-day.md b/content/posts/2015-06-11-18f-at-national-civic-hacking-day.md
index 8b8d8fe8d..f3c49ea0d 100644
--- a/content/posts/2015-06-11-18f-at-national-civic-hacking-day.md
+++ b/content/posts/2015-06-11-18f-at-national-civic-hacking-day.md
@@ -26,7 +26,7 @@ enough of this. Fortunately, there were [more than 100 events](http://hackforcha
Here’s just some of what we worked on together:
-![Pictures from the D.C. event]({{site.baseurl}}/assets/blog/national-day-of-civic-hacking-2015/hacking-day-dc.jpg)
+{% image "assets/blog/national-day-of-civic-hacking-2015/hacking-day-dc.jpg" "Pictures from the D.C. event" %}
*Scenes from the event in Washington, D.C.*
**Washington, D.C.**: The Small Business Administration and Census
@@ -56,7 +56,7 @@ who lives in San Diego, led a
for a Street Sweeper app. We got from markers and drawing to working
code in less than an hour!
-![The group of civic hackers in Tucson]({{site.baseurl}}/assets/blog/national-day-of-civic-hacking-2015/hacking-day-tucson.jpg)
+{% image "assets/blog/national-day-of-civic-hacking-2015/hacking-day-tucson.jpg" "The group of civic hackers in Tucson" %}
*Civic hackers at the event hosted by Code for Tucson*
**Tucson, Ariz**: [Code for Tucson](http://codefortucson.org/),
diff --git a/content/posts/2015-06-16-fast-company-story.md b/content/posts/2015-06-16-fast-company-story.md
index 7958e28b6..59daed6cc 100644
--- a/content/posts/2015-06-16-fast-company-story.md
+++ b/content/posts/2015-06-16-fast-company-story.md
@@ -18,7 +18,7 @@ image: /assets/blog/fast-company/jumpshot.jpg
hero: false
---
-![The U.S. Digital Service family]({{site.baseurl}}/assets/blog/fast-company/jumpshot.jpg)
+{% image "assets/blog/fast-company/jumpshot.jpg" "The U.S. Digital Service family" %}
*Photo by Daniel Shea for Fast Company*
We often get asked to explain how 18F fits in with the larger U.S.
diff --git a/content/posts/2015-06-17-what-estonia-can-teach-us-about-government-records.md b/content/posts/2015-06-17-what-estonia-can-teach-us-about-government-records.md
index 968884b10..b4c2f5077 100644
--- a/content/posts/2015-06-17-what-estonia-can-teach-us-about-government-records.md
+++ b/content/posts/2015-06-17-what-estonia-can-teach-us-about-government-records.md
@@ -39,7 +39,7 @@ of Estonia’s most prominent technologists visited D.C. for a week-long
tour, which included meetings with the State Department, the World Bank,
and U.S. digital services teams.
-
+{% image_with_class "assets/blog/estonia/Estonia2.jpg" "width-500px" "The Estonian delegation with members of 18F, OSTP, and CTO Megan Smith" %}
*U.S. Chief Technology Officer Megan Smith, members of U.S. digital
services teams, and the representatives from Estonia.*
diff --git a/content/posts/2015-06-24-thomas-vander-wal-event.md b/content/posts/2015-06-24-thomas-vander-wal-event.md
index b22f20307..273ee497a 100644
--- a/content/posts/2015-06-24-thomas-vander-wal-event.md
+++ b/content/posts/2015-06-24-thomas-vander-wal-event.md
@@ -34,7 +34,7 @@ Vander Wal said during his lecture. But many companies don’t save
instant message conversations. And email buries data in an archive
that’s inaccessible to most.
-![An illustration of closed-node communication]({{site.baseurl}}/assets/blog/vander-wal/email.jpg)
+{% image "assets/blog/vander-wal/email.jpg" "An illustration of closed-node communication" %}
*An illustration of closed-node communication, from Vander Wal’s
presentation*
@@ -59,7 +59,7 @@ keeping](https://18f.gsa.gov/2015/05/28/18F-guides/), and — whenever
possible — we illuminate our processes, hopefully [to the benefit of
the larger tech community](https://pages.18f.gov/guides/).
-![A slide listing the values of open node communication]({{site.baseurl}}/assets/blog/vander-wal/opennodes.jpg)
+{% image "assets/blog/vander-wal/opennodes.jpg" "A slide listing the values of open node communication" %}
*Open-node communication allows members of the same community to share
institutional knowledge deftly and painlessly.*
diff --git a/content/posts/2015-07-06-18f-content-guide.md b/content/posts/2015-07-06-18f-content-guide.md
index e0b989046..63aeeba51 100644
--- a/content/posts/2015-07-06-18f-content-guide.md
+++ b/content/posts/2015-07-06-18f-content-guide.md
@@ -17,7 +17,7 @@ image: /assets/blog/content-style-guide/style-guide-screen.jpg
hero: false
---
-[![Screenshot of the 18F Content Guide]({{site.baseurl}}/assets/blog/content-style-guide/style-guide-screen.jpg)](https://pages.18f.gov/content-guide/)
+[{% image "assets/blog/content-style-guide/style-guide-screen.jpg" "Screenshot of the 18F Content Guide" %}](https://pages.18f.gov/content-guide/)
18F recently introduced its [series of guides](https://18f.gsa.gov/2015/05/28/18F-guides/), a collection of best practices for our internal project teams. As Mike Bland writes in his post describing the guides, “Though these guides currently carry the 18F brand, the intention is to spread the use and cultivation of the material throughout the broader [U.S. Digital Service](https://wh.gov/usds/) effort.”
diff --git a/content/posts/2015-07-08-openfec-api.md b/content/posts/2015-07-08-openfec-api.md
index 124b19891..8118f41fa 100644
--- a/content/posts/2015-07-08-openfec-api.md
+++ b/content/posts/2015-07-08-openfec-api.md
@@ -14,7 +14,7 @@ excerpt: "Today marks the launch of the FEC’s first API. With that API, search
hero: false
---
-![OpenFEC: Explore campaign finance data]({{site.baseurl}}/assets/blog/openfec-api/openfec-banner.jpg)
+{% image "assets/blog/openfec-api/openfec-banner.jpg" "OpenFEC: Explore campaign finance data" %}
The Federal Election Commission (FEC) empowers citizens with the information they need to make informed decisions about their democracy.
@@ -23,7 +23,7 @@ Since opening its doors in the ‘70s, the FEC has evolved to better serve the p
With that API, searching for candidates and committees will be easier and more interactive. Information is organized around concepts like candidates, which are more welcoming than navigating buckets of information based on forms.
diff --git a/content/posts/2015-07-17-the-new-10.md b/content/posts/2015-07-17-the-new-10.md
index 8cf1ef8a3..a1212e632 100644
--- a/content/posts/2015-07-17-the-new-10.md
+++ b/content/posts/2015-07-17-the-new-10.md
@@ -36,7 +36,7 @@ operates under a cost-recoverable model.
Then the fun really began.
-![Treasury's The New 10 site]({{site.baseurl}}/assets/blog/the-new-10/the-new-10.jpg)
+{% image "assets/blog/the-new-10/the-new-10.jpg" "Treasury's The New 10 site" %}
We set up a number of creative reviews with 18F Consulting and
Treasury’s design team. My colleague Jesse Taggert and I partnered
diff --git a/content/posts/2015-07-29-style-guide-for-open-source-documentation.md b/content/posts/2015-07-29-style-guide-for-open-source-documentation.md
index 622ee97c4..383d9684e 100644
--- a/content/posts/2015-07-29-style-guide-for-open-source-documentation.md
+++ b/content/posts/2015-07-29-style-guide-for-open-source-documentation.md
@@ -17,7 +17,7 @@ hero: false
We routinely publish our best practices in the [18F Guides](https://pages.18f.gov/guides/), and today we’re happy to launch a new one: the [18F Open Source Style Guide](https://pages.18f.gov/open-source-guide/).
-![Screenshot of Open Source Guide]({{site.baseurl}}/assets/blog/open-source-guide/screenshot-of-guide.png)
+{% image "assets/blog/open-source-guide/screenshot-of-guide.png" "Screenshot of Open Source Guide" %}
The Open Source Style Guide is a comprehensive handbook for writing clear, accessible, and user-friendly documentation so that your open source code repositories are accessible both internally and externally.
diff --git a/content/posts/2015-08-06-communicart-tool-will-streamline-purchase-card-process.md b/content/posts/2015-08-06-communicart-tool-will-streamline-purchase-card-process.md
index 0b233b62e..666b8f6d8 100644
--- a/content/posts/2015-08-06-communicart-tool-will-streamline-purchase-card-process.md
+++ b/content/posts/2015-08-06-communicart-tool-will-streamline-purchase-card-process.md
@@ -42,7 +42,7 @@ process. With our partners at the General Service Administration's
Public Buildings Service in Washington, D.C., we’ve started building a
tool to help make this process fast and efficient.
-[![Screenshot of the Communicart approval portal]({{site.baseurl}}/assets/blog/communicart/communicart-screenshot.png)](https://cap.18f.gov/)
+[{% image "assets/blog/communicart/communicart-screenshot.png" "Screenshot of the Communicart approval portal" %}](https://cap.18f.gov/)
We call it [Communicart](https://18f.gsa.gov/our-work/c2/).
It’s a tool that took some cues from the process for tracking “carts”
diff --git a/content/posts/2015-08-10-18f-design-methods.md b/content/posts/2015-08-10-18f-design-methods.md
index add7781b3..91e78403d 100644
--- a/content/posts/2015-08-10-18f-design-methods.md
+++ b/content/posts/2015-08-10-18f-design-methods.md
@@ -103,7 +103,7 @@ this in a future blog post — stay tuned.)
**Check out the [method cards online](https://methods.18f.gov/) for more information.** Our “alpha” digital version provides more details about each method, short stories about how we’ve used a given method in our work, and links to additional resources.
-[![A screenshot of the Design Method Cards website]({{site.baseurl}}/assets/blog/design-method-cards/method-cards.png)](https://methods.18f.gov/)
+[{% image "assets/blog/design-method-cards/method-cards.png" "A screenshot of the Design Method Cards website" %}](https://methods.18f.gov/)
## Principles that are and are not here
diff --git a/content/posts/2015-08-26-aaron-gustafson-beyond-responsive-design.md b/content/posts/2015-08-26-aaron-gustafson-beyond-responsive-design.md
index f38aefdf8..1031e9ad4 100644
--- a/content/posts/2015-08-26-aaron-gustafson-beyond-responsive-design.md
+++ b/content/posts/2015-08-26-aaron-gustafson-beyond-responsive-design.md
@@ -14,7 +14,7 @@ excerpt: "Web standards and accessibility expert Aaron Gustafson recently came t
description: "Web standards and accessibility expert Aaron Gustafson recently came to 18F to speak about progressive enhancement and to challenge designers to improve user experience across browsers and devices."
image: /assets/blog/aaron-gustafson/mms-gustafson.jpg
---
-![Aaron Gustafson gives a presentation at 18F]({{site.baseurl}}/assets/blog/aaron-gustafson/gustafson.jpg)
+{% image "assets/blog/aaron-gustafson/gustafson.jpg" "Aaron Gustafson gives a presentation at 18F" %}
Web standards and accessibility expert Aaron Gustafson was working with
a major drug store chain when he discovered they only tested their
website on iPhones and iPads.
@@ -76,7 +76,7 @@ The text is the peanut, a fine snack on its own. But with chocolate
(CSS), it’s tastier. And it’s best with colorful candy coating
(Javascript). Ultimately, you can enjoy it at whatever step you get it.
-![A peanut, a chocolate covered peanut, and a peanut M&M]({{site.baseurl}}/assets/blog/aaron-gustafson/mms-gustafson.jpg)
+{% image "assets/blog/aaron-gustafson/mms-gustafson.jpg" "A peanut, a chocolate covered peanut, and a peanut M&M" %}
*Slide from [Gustafson’s
presentation](http://www.slideshare.net/AaronGustafson/beyond-responsive-18f-2015)*.
diff --git a/content/posts/2015-08-31-how-playing-with-legos-taught-executives-agile.md b/content/posts/2015-08-31-how-playing-with-legos-taught-executives-agile.md
index bb3653d8f..5bf562c4c 100644
--- a/content/posts/2015-08-31-how-playing-with-legos-taught-executives-agile.md
+++ b/content/posts/2015-08-31-how-playing-with-legos-taught-executives-agile.md
@@ -28,7 +28,7 @@ But they started wondering, is this really the best way? Or should we be
trying something new? It turns out not even the creator of waterfall,
Dr. Winston Royce, thought waterfall was a good idea!
-![A highlighted quote that says "I believe in this concept, but the implementation described above is risky and invites failure."]({{site.baseurl}}/assets/blog/lego-workshop/waterfall-quote.jpg)
+{% image "assets/blog/lego-workshop/waterfall-quote.jpg" "A highlighted quote that says "I believe in this concept, but the implementation described above is risky and invites failure."" %}
*From page 2 of Dr. Royce’s 1970 paper, [Managing the
Development of Large Software Systems](http://www.serena.com/docs/agile/papers/Managing-The-Development-of-Large-Software-Systems.pdf).*
@@ -56,7 +56,7 @@ what agile is. One must experience it for oneself. It was time for the
red pill.
-
+{% image "assets/blog/lego-workshop/red-pill.gif" "The red and blue pill from The Matrix" %}
We split the group into two teams and told them that, in the next 90
@@ -75,7 +75,7 @@ As the product owner, I gave the teams their user stories:
And then I dumped a bucket of Lego bricks in front of each team. “Go!”
-![SBA executives prepare to build with Legos.]({{site.baseurl}}/assets/blog/lego-workshop/sba-execs-legos-2.jpg)
+{% image "assets/blog/lego-workshop/sba-execs-legos-2.jpg" "SBA executives prepare to build with Legos." %}
After a few “I haven’t played with Legos in 40 years…”, they were off!
diff --git a/content/posts/2015-09-03-every-kid-in-a-park.md b/content/posts/2015-09-03-every-kid-in-a-park.md
index e7249a5a5..511692187 100644
--- a/content/posts/2015-09-03-every-kid-in-a-park.md
+++ b/content/posts/2015-09-03-every-kid-in-a-park.md
@@ -18,7 +18,7 @@ image: /assets/blog/every-kid-in-a-park/every-kid-in-a-park.jpg
hero: false
---
-[![Two students hold up their Every Kid in a Park passes]({{site.baseurl}}/assets/blog/every-kid-in-a-park/every-kid-in-a-park.jpg)](https://www.flickr.com/photos/usinterior/20900647896/in/album-72157657833038461/)
+[{% image "assets/blog/every-kid-in-a-park/every-kid-in-a-park.jpg" "Two students hold up their Every Kid in a Park passes" %}](https://www.flickr.com/photos/usinterior/20900647896/in/album-72157657833038461/)
*Students from Samuel W. Tucker Elementary School receive an Every Kid
in a Park pass. Photo credit: Department of Interior.*
@@ -87,7 +87,7 @@ photos, to the text on every page. Even the information for parents and
teachers was designed to be understandable for our primary users
— fourth graders.
-![Children and adults sit around a large piece of paper while co-designing the Every Kid in a Park website.]({{site.baseurl}}/assets/blog/every-kid-in-a-park/ekip-user-testing.jpg)
+{% image "assets/blog/every-kid-in-a-park/ekip-user-testing.jpg" "Children and adults sit around a large piece of paper while co-designing the Every Kid in a Park website." %}
*Sally Jewell, Secretary of the U.S. Department of the Interior, sits with kids as they help co-design the Every Kid in a Park website using methods developed by the University of Maryland Human Computer Interaction KidsTeam Lab. Photo Credit: Evan Golub, 2015.*
## Building a site for kids has unique challenges
diff --git a/content/posts/2015-09-04-what-is-technical-debt.md b/content/posts/2015-09-04-what-is-technical-debt.md
index 7d7c43e8d..f14d5507c 100644
--- a/content/posts/2015-09-04-what-is-technical-debt.md
+++ b/content/posts/2015-09-04-what-is-technical-debt.md
@@ -26,7 +26,7 @@ And the extra time it takes to work with our unwieldy code or design,
until it’s fixed, represents the interest portion.
-
+{% image "assets/blog/technical-debt/graphic-1.jpg" "width-400px" "A bar graph showing how poor design can increase the cost of making changes or adding new features" %}
Like financial debt, not all technical debt is bad debt. For example,
@@ -54,7 +54,7 @@ technical debt. Martin Fowler, a leading software expert, classifies
technical debt into four types, as shown in the quadrant below.
-
+{% image "assets/blog/technical-debt/graphic-2.jpg" "A grid of the four types of technical debt. Reckless and deliberate, reckless and inadvertent, prudent and deliberate, prudent and inadvertent." %} width="600px">
Here's how each type may occur:
@@ -81,7 +81,7 @@ within a software product over time:
- The predictability of results decreases, making management highly distrustful. (Producing accurate estimates for software with a high amount of debt is nearly impossible.)
-
+{% image "assets/blog/technical-debt/graphic-3.jpg" "A graph showing how the cost of change increases over time when you have technical debt, and that hurts your ability to meet user needs." %}
*Source: [Jim
diff --git a/content/posts/2015-09-09-how-a-two-day-spring-moved-an-agency-twenty-years-forward.md b/content/posts/2015-09-09-how-a-two-day-spring-moved-an-agency-twenty-years-forward.md
index 541b96dbd..34a5e3667 100644
--- a/content/posts/2015-09-09-how-a-two-day-spring-moved-an-agency-twenty-years-forward.md
+++ b/content/posts/2015-09-09-how-a-two-day-spring-moved-an-agency-twenty-years-forward.md
@@ -37,14 +37,14 @@ While conducting investigations, Labor employees often turn to the Field Operati
---
-![Two investigators and an 18F user researcher who is shadowing them]({{site.baseurl}}/assets/blog/labor-handbook/field-team.jpg)
+{% image "assets/blog/labor-handbook/field-team.jpg" "Two investigators and an 18F user researcher who is shadowing them" %}
*Two investigators (left and right) and an 18F user researcher (center) who is shadowing them to understand how investigators use paper and digital methods to accomplish their job.*
## The current landscape: Publishing in the 21st century
The handbook consists of four five-inch-thick binders containing printed and photocopied pages. These binders are replicated and distributed across numerous regional and local offices. The handbook also exists as online PDFs, where each chapter or subsection is published as its own PDF. With these two options, investigators don’t have an easy way to quickly access and search for much-needed information that helps them complete investigations, particularly when they’re working out in the field.
-![Three large binders of handbook materials]({{site.baseurl}}/assets/blog/labor-handbook/handbook.jpg)
+{% image "assets/blog/labor-handbook/handbook.jpg" "Three large binders of handbook materials" %}
## The challenge: How to move this project forward?
@@ -86,7 +86,7 @@ In this two day sprint, about eight of us gathered to:
We facilitated a two-hour kick-off meeting (sometimes called an Inception). It got the group aligned around the problem and to agree on a plan moving forward.
-![The 18F and Labor team writes notes up on a large white board]({{site.baseurl}}/assets/blog/labor-handbook/group-1.jpg)
+{% image "assets/blog/labor-handbook/group-1.jpg" "The 18F and Labor team writes notes up on a large white board" %}
*Kick off (Inception)*
During this Inception we:
@@ -123,7 +123,7 @@ Examples of our user stories:
- As an investigator, I want the FOH to be easy to read because past methods have been hard to read. *(provide good version 1 typography and design of this online resource)*
-![Developers, investigators, and product owners work together on day 2. The project's progress boards are taped to the windows.]({{site.baseurl}}/assets/blog/labor-handbook/group-2.jpg)
+{% image "assets/blog/labor-handbook/group-2.jpg" "Developers, investigators, and product owners work together on day 2. The project's progress boards are taped to the windows." %}
*Day 2 of the team working out of the 18F common space. Developers on the left. Investigators (users) and product owners talking about needs on the right. Taped to the windows are the progress boards (Backlog, Current, Done).*
Tom, the product owner had already used optical character recognition (OCR) software to convert 100s of PDFs into MS Word documents. Microsoft styles and headings were applied to the content to begin to structure the data. (Aside: this is a perfect example of using the tools you know best to move a project forward!) With that in hand, our developer validated the technical feasibility of converting those Word documents to HTML pages that could be searched using Elasticsearch.
@@ -158,7 +158,7 @@ One of the great things about a cross-functional team in the same room for a spr
Actual investigators made this sprint a success. Working with them over the two days, we determined the best interface copy that would be clear and actionable to their peers. Seconds after code was pushed to the staging site, we observed how they used search and understood the search results pages. Feedback was immediately incorporated.
-![Screenshots of the prototype for an online version of the handbook.]({{site.baseurl}}/assets/blog/labor-handbook/foh-screenshot.jpg)
+{% image "assets/blog/labor-handbook/foh-screenshot.jpg" "Screenshots of the prototype for an online version of the handbook." %}
*Two days later we had a working prototype showing browsable chapters and a search results page.*
## What’s next?
diff --git a/content/posts/2015-09-14-college-scorecard-launch.md b/content/posts/2015-09-14-college-scorecard-launch.md
index 66f1b5d91..199f34391 100644
--- a/content/posts/2015-09-14-college-scorecard-launch.md
+++ b/content/posts/2015-09-14-college-scorecard-launch.md
@@ -34,7 +34,7 @@ College search resources like [ScholarMatch](http://scholarmatcher.scholarmatch.
## How we did it
-![A team of people look at a demo of College Scorecard]({{site.baseurl}}/assets/blog/college-scorecard/college-scorecard-1.jpg)
+{% image "assets/blog/college-scorecard/college-scorecard-1.jpg" "A team of people look at a demo of College Scorecard" %}
*One of our many demos.*
This was a truly collaborative team effort: thank you to the [Department of Education](http://www.ed.gov/), White House Domestic Policy Council, White House Council of Economic Advisors, Department of Treasury, Office of Management and Budget, [18F](https://18f.gsa.gov/) (at GSA) and the team at the [U.S. Digital Service](https://obamawhitehouse.archives.gov/digital/united-states-digital-service).
@@ -46,7 +46,7 @@ We knew what we needed to do: make people’s lives better by providing them the
**Instead of guessing, we decided to go out and ask them.**
-![An amazing guidance counselor at Anacostia High with two of his students.]({{site.baseurl}}/assets/blog/college-scorecard/college-scorecard-2.jpg)
+{% image "assets/blog/college-scorecard/college-scorecard-2.jpg" "An amazing guidance counselor at Anacostia High with two of his students." %}
*An amazing guidance counselor at Anacostia High with two of his students.*
Following our practice of [focusing on user needs](https://playbook.cio.gov/#play1), the College Scorecard team first spent time engaging directly with users at every single step in the project. Some of our favorite conversations were when we talked to high school students in Washington, D.C.’s Anacostia neighborhood and their excellent guidance counselor. He told us how he “hacks” the process to make sure every one of his students gets an acceptance letter from a college, and feels that rush of possibility.
@@ -57,7 +57,7 @@ We built on the hard work of the Department of Education; previously, they met w
### Be agile.
-![Secretary of Education Arne Duncan sees the difference between the paper prototype and the mobile-friendly version of the College Scorecard.]({{site.baseurl}}/assets/blog/college-scorecard/college-scorecard-3.jpg)
+{% image "assets/blog/college-scorecard/college-scorecard-3.jpg" "Secretary of Education Arne Duncan sees the difference between the paper prototype and the mobile-friendly version of the College Scorecard." %}
*Secretary of Education Arne Duncan sees the difference between the paper prototype and the mobile-friendly version of the College Scorecard.*
Based on this research and input from the field, we made the cheapest, fastest prototype of the College Scorecard possible. We knew it needed to be mobile-first, simple, and easy to customize. That prototype ended up being a homemade, cardboard iPhone — slips of paper with wireframes of what the tool could look like. It probably cost less than a cup of coffee to produce.
diff --git a/content/posts/2015-09-15-federalist-platform-launch.md b/content/posts/2015-09-15-federalist-platform-launch.md
index 6a6447a21..48221abe4 100644
--- a/content/posts/2015-09-15-federalist-platform-launch.md
+++ b/content/posts/2015-09-15-federalist-platform-launch.md
@@ -15,7 +15,7 @@ image: /assets/blog/federalist/sbst-screenshot-2.jpg
hero: false
---
-![The new White House Social and Behavioral Sciences Team homepage]({{site.baseurl}}/assets/blog/federalist/sbst-screenshot-2.jpg)
+{% image "assets/blog/federalist/sbst-screenshot-2.jpg" "The new White House Social and Behavioral Sciences Team homepage" %}
_Summer 2017 Update: Federalist [left beta in June 2017](https://18f.gsa.gov/2017/06/01/federalist-is-out-of-beta-and-open-for-business/) and is currently seeking new customers. Email us at federalist-inquiries@gsa.gov or fill out this [Google form](https://docs.google.com/forms/d/e/1FAIpQLSesNI1qlov7Ec_1u2FralYWg9hV4WsB-3FyAHPXc1pRT6In7w/viewform) if you're interested in using Federalist for your office._
diff --git a/content/posts/2015-09-21-new-citizenship-resources.md b/content/posts/2015-09-21-new-citizenship-resources.md
index 9f5549694..33c10c509 100644
--- a/content/posts/2015-09-21-new-citizenship-resources.md
+++ b/content/posts/2015-09-21-new-citizenship-resources.md
@@ -81,7 +81,7 @@ capture new customers’ attention. Our new, highly visual page links out
to the existing CRC resources, making it easy for customers to quickly
access more detailed information.
-![A screenshot of part of the new USCIS rights and responsibilities page]({{site.baseurl}}/assets/blog/citizenshipweek/rights-and-responsibilities.jpg)
+{% image "assets/blog/citizenshipweek/rights-and-responsibilities.jpg" "A screenshot of part of the new USCIS rights and responsibilities page" %}
*The new USCIS rights and responsibilities page.*
@@ -132,7 +132,7 @@ most informed decision possible. Customers can also use the locator to
find nearby citizenship preparation classes, which will help them
navigate the naturalization process.
-![A map of English and citizenship classes]({{site.baseurl}}/assets/blog/citizenshipweek/classes.jpg)
+{% image "assets/blog/citizenshipweek/classes.jpg" "A map of English and citizenship classes" %}
*The English and citizenship preparation class locator provides location and
contact information.*
diff --git a/content/posts/2015-09-22-usa-gov-launches-vote-usa-gov-to-help-citizens-register-and-connect-with-states.md b/content/posts/2015-09-22-usa-gov-launches-vote-usa-gov-to-help-citizens-register-and-connect-with-states.md
index 0e227d39f..211572844 100644
--- a/content/posts/2015-09-22-usa-gov-launches-vote-usa-gov-to-help-citizens-register-and-connect-with-states.md
+++ b/content/posts/2015-09-22-usa-gov-launches-vote-usa-gov-to-help-citizens-register-and-connect-with-states.md
@@ -15,7 +15,7 @@ _This post originally appeared on the [GSA Blog](http://gsablogs.gsa.gov/gsablog
One of the most important rights of American citizens is the right to vote. It is the foundation of our democracy, and in many ways, the basis of our government. This is why the team at USA.gov is excited to announce the launch of vote.USA.gov.
-[![Screen shot of the homepage at vote.usa.gov]({{site.baseurl}}/assets/blog/vote-usa-gov/vote.jpg)](https://vote.usa.gov)
+[{% image "assets/blog/vote-usa-gov/vote.jpg" "Screen shot of the homepage at vote.usa.gov" %}](https://vote.usa.gov)
USA.gov is an interagency initiative administered by the Federal Citizen Information Center, a division of the [U.S. General Services Administration's Office of Citizen Services and Innovative Technologies](http://www.gsa.gov/portal/category/25729). USA.gov helps connect visitors to important government services and related resources.
diff --git a/content/posts/2015-09-28-web-design-standards.md b/content/posts/2015-09-28-web-design-standards.md
index 65bd69106..8ace9d5e2 100644
--- a/content/posts/2015-09-28-web-design-standards.md
+++ b/content/posts/2015-09-28-web-design-standards.md
@@ -41,7 +41,7 @@ government services, they’re often met with confusing navigation
systems, a cacophony of visual brands, and inconsistent interaction
patterns.
-![A collection of buttons from government websites with many different colors and styles.]({{site.baseurl}}/assets/blog/web-design-standards/buttons.png)
+{% image "assets/blog/web-design-standards/buttons.png" "A collection of buttons from government websites with many different colors and styles." %}
*Each button, a special snowflake. A snapshot of a quick survey of buttons across government websites.*
Dedicated federal workers are striving to build helpful digital tools
@@ -139,7 +139,7 @@ patterns were further tested with end users.
We believe agencies should still usability test everything they build,
but following the standards will help everyone avoid common pitfalls.
-![A sample of code from the Web Design Standards.]({{site.baseurl}}/assets/blog/web-design-standards/code.png)
+{% image "assets/blog/web-design-standards/code.png" "A sample of code from the Web Design Standards." %}
*All of our standards include code samples.*
### Front-end
@@ -160,7 +160,7 @@ After speaking with dozens of front-end developers and designers in
government, we sought to strike a balance between modular CSS and code
that’s clean and easy-to-use.
-![A screenshot of the color section of the Design Standards.]({{site.baseurl}}/assets/blog/web-design-standards/colors.png)
+{% image "assets/blog/web-design-standards/colors.png" "A screenshot of the color section of the Design Standards." %}
*The Design Standards include an extensive color palette.*
### Visual design
diff --git a/content/posts/2015-10-05-managing-technical-debt.md b/content/posts/2015-10-05-managing-technical-debt.md
index e4868de92..b38cd272a 100644
--- a/content/posts/2015-10-05-managing-technical-debt.md
+++ b/content/posts/2015-10-05-managing-technical-debt.md
@@ -76,7 +76,7 @@ greater understanding of the value of paying it back or not paying it
back. You can do this using our friend, the heat map, like the one shown
below.
-![A heat map of the various penalties involved with technical debt in different areas of code.]({{site.baseurl}}/assets/blog/technical-debt/heat-map.jpg)
+{% image "assets/blog/technical-debt/heat-map.jpg" "A heat map of the various penalties involved with technical debt in different areas of code." %}
*Source: [Modified from a post by James
King](http://kingsinsight.com/2010/07/31/estimating-the-impact-of-technical-debt-on-stories-heat-maps/)*
diff --git a/content/posts/2015-10-07-digital-economy-practice.md b/content/posts/2015-10-07-digital-economy-practice.md
index 595ab83f7..ff79db2de 100644
--- a/content/posts/2015-10-07-digital-economy-practice.md
+++ b/content/posts/2015-10-07-digital-economy-practice.md
@@ -16,7 +16,7 @@ hero: false
Since launching [more than a year ago](https://18f.gsa.gov/2015/03/20/one-year-in-and-looking-forward/), 18F has made tremendous progress toward introducing new ways to [deliver services to the public](https://18f.gsa.gov/dashboard/). As we continue to explore how to better serve our colleagues across the government, we’ve come to realize that there may be opportunities to achieve high impact in targeted areas by aligning our *subject expertise* (for example, finance, healthcare) with our *digital expertise* (for example, human-centered design, agile development) to help agencies achieve their policy goals. Being adopters of the lean startup philosophy, this means one thing: Let’s run an experiment. To test our hypothesis, we’re launching an alpha version of our first policy vertical (or niche market) within [18F Consulting]({{ site.baseurl }}/consulting/): the Digital Economy Practice.
-
+{% image_with_class "assets/blog/digital-economy-practice/dep-graphic2.jpg" "width-500px" "The Digital Economy Practice competencies include industry and policy, people and organization, design and product, technology and data, and acquisition and procurement." %}
Across the government, agencies work hard to improve economic outcomes for our country and others. Whether it’s the U.S. Department of the Treasury’s [*my*RA](https://myra.treasury.gov/), which helps people start to save for retirement, or the Securities and Exchange Commission’s [Tick Size Pilot](http://www.sec.gov/news/pressrelease/2015-82.html), which studies different stock price quotation methods in order to improve access to capital for small publicly-traded companies, there are countless government initiatives aimed at expanding economic opportunity.
diff --git a/content/posts/2015-10-09-cloud-gov-launch.md b/content/posts/2015-10-09-cloud-gov-launch.md
index f6cad112a..df604755e 100644
--- a/content/posts/2015-10-09-cloud-gov-launch.md
+++ b/content/posts/2015-10-09-cloud-gov-launch.md
@@ -35,7 +35,7 @@ make it as easy as possible to build right near the water and get it
launched quickly and easily, even at battleship scale.
---
diff --git a/content/posts/2015-10-13-open-source-micropurchasing.md b/content/posts/2015-10-13-open-source-micropurchasing.md
index d78a4c269..bdc822cf3 100644
--- a/content/posts/2015-10-13-open-source-micropurchasing.md
+++ b/content/posts/2015-10-13-open-source-micropurchasing.md
@@ -24,7 +24,7 @@ Specifically, we’re going to use our "micro-purchase" authority. Like all fede
There are several reasons we’re trying this experiment. But perhaps the most important reason is this: we want another reason for our partner agencies to support open source code. We've long known at 18F that opening our source code from day one improves our ability to deliver. But we want to show that opening our source code improves our ability to contract for digital services. We also want to see whether this is a sustainable way to engage small businesses and non-traditional contractors in the government space.
-![An animation of how the CALC tool works]({{site.baseurl}}/assets/blog/calc-announcement/calc_demo.gif)
+{% image "assets/blog/calc-announcement/calc_demo.gif" "An animation of how the CALC tool works" %}
*A demonstration of our CALC tool, which we will use for this micro-purchase experiment.*
## How will it work?
diff --git a/content/posts/2015-10-15-best-practices-for-distributed-teams.md b/content/posts/2015-10-15-best-practices-for-distributed-teams.md
index 7db2d07e8..e36d7d2bd 100644
--- a/content/posts/2015-10-15-best-practices-for-distributed-teams.md
+++ b/content/posts/2015-10-15-best-practices-for-distributed-teams.md
@@ -67,7 +67,7 @@ touch at least part of the day and won’t slow down ‘hot items,’ yet
still allows people half the day to focus on actually moving the ball
forward.”
-![A grid of 18F team members using video chat to attend a meeting.]({{site.baseurl}}/assets/blog/distributed-teams/18f-team-acano.jpg)
+{% image "assets/blog/distributed-teams/18f-team-acano.jpg" "A grid of 18F team members using video chat to attend a meeting." %}
*Part of the 18F team at the weekly all-hands meeting.*
We share our screens frequently.
@@ -202,6 +202,6 @@ their projects.
If you have more questions on the tools we use and how we use them, just
ask us at [18f@gsa.gov](mailto:18f@gsa.gov).
-![A grid of 18F team members using signs to wish their colleague a happy birthday.]({{site.baseurl}}/assets/blog/distributed-teams/acano-birthday.jpg)
+{% image "assets/blog/distributed-teams/acano-birthday.jpg" "A grid of 18F team members using signs to wish their colleague a happy birthday." %}
*Our design team takes two minutes out of their weekly meeting to wish
teammate Jeremy Canfield (bottom left) a happy birthday.*
diff --git a/content/posts/2015-10-21-every-kid-in-a-park-follow-up.md b/content/posts/2015-10-21-every-kid-in-a-park-follow-up.md
index 1abbff071..d16dd1b45 100644
--- a/content/posts/2015-10-21-every-kid-in-a-park-follow-up.md
+++ b/content/posts/2015-10-21-every-kid-in-a-park-follow-up.md
@@ -93,7 +93,7 @@ Final touches
Although we hope our users never encounter it, we also added a 404 page.
We’re proud of the content and design:
-![The Every Kid in a Park 404 page.]({{site.baseurl}}/assets/blog/every-kid-in-a-park/404.png)
+{% image "assets/blog/every-kid-in-a-park/404.png" "The Every Kid in a Park 404 page." %}
In all, we’re thrilled with
[everykidinapark.gov](http://everykidinapark.gov). We’ve handed the
diff --git a/content/posts/2015-10-29-welcome-to-betafec.md b/content/posts/2015-10-29-welcome-to-betafec.md
index 4ba60ca86..c0875ba05 100644
--- a/content/posts/2015-10-29-welcome-to-betafec.md
+++ b/content/posts/2015-10-29-welcome-to-betafec.md
@@ -13,7 +13,7 @@ excerpt: "As the 2016 presidential election heats up, here at 18F we’ve been w
hero: false
---
-[![The betaFEC homepage.]({{site.baseurl}}/assets/blog/fec/beta-fec-home.gif)](https://beta.fec.gov)
+[{% image "assets/blog/fec/beta-fec-home.gif" "The betaFEC homepage." %}](https://beta.fec.gov)
As the 2016 presidential election heats up, here at 18F we’ve been working with the Federal Election Commission (FEC) to make campaign finance data more accessible to the public. Today, we launched [betaFEC](http://beta.fec.gov), the first piece in a complete redesign of the FEC’s online presence.
diff --git a/content/posts/2015-11-02-useiti-what-we-learned-where-were-headed.md b/content/posts/2015-11-02-useiti-what-we-learned-where-were-headed.md
index ba80104f6..7a5a1050c 100644
--- a/content/posts/2015-11-02-useiti-what-we-learned-where-were-headed.md
+++ b/content/posts/2015-11-02-useiti-what-we-learned-where-were-headed.md
@@ -12,7 +12,7 @@ excerpt: During Sunshine Week, we wrote about our progress on the Extractive Ind
image: /assets/blog/eiti/drill.jpg
hero: false
---
-![An oil rig on public land. Courtesy of the Department of Energy]({{site.baseurl}}/assets/blog/eiti/drill.jpg)
+{% image "assets/blog/eiti/drill.jpg" "An oil rig on public land. Courtesy of the Department of Energy" %}
_Oil drilling is one of many industries included in the Extractive Industries Transparency Initiative (EITI). The U.S. Department of the Interior and the USEITI multi-stakeholder group will publish the first report this December._
diff --git a/content/posts/2015-11-04-complexity-is-the-adversary.md b/content/posts/2015-11-04-complexity-is-the-adversary.md
index a145899a8..a929bc2c0 100644
--- a/content/posts/2015-11-04-complexity-is-the-adversary.md
+++ b/content/posts/2015-11-04-complexity-is-the-adversary.md
@@ -22,7 +22,7 @@ Look at [goto fail](https://www.imperialviolet.org/2014/02/22/applebug.html), [H
It's not just the complexity of the technology itself that's the problem. When our compliance documentation is complex, we’re making ourselves less secure. If it takes a hundred (or several hundred) pages to explain all the security controls you've implemented on a piece of software, that's not a good thing.
-![A sample of required security documentation for federal websites.]({{site.baseurl}}/assets/blog/complexity-and-security/security-documentation-1.jpg)
+{% image "assets/blog/complexity-and-security/security-documentation-1.jpg" "A sample of required security documentation for federal websites." %}
_A sample of required security documentation. It's not uncommon to see 300 pages or more._
diff --git a/content/posts/2015-11-06-micro-purchase-lessons.md b/content/posts/2015-11-06-micro-purchase-lessons.md
index 4a6399e3c..367de9961 100644
--- a/content/posts/2015-11-06-micro-purchase-lessons.md
+++ b/content/posts/2015-11-06-micro-purchase-lessons.md
@@ -33,7 +33,7 @@ But beyond the fact that we got working software in a little less than a week af
* The largest bid increment was $740, the smallest bid increment was $1, and the most common bid increment was $50.
* As of the afternoon of November 6, 2015, there were more than 10,000 unique visitors to the GitHub issue (though much of it was driven by being on the [front page of Hacker News](https://news.ycombinator.com/item?id=10471677)), and more than 300 unique visitors to the underlying data that is the subject of the micro-purchase experiment.
-![Traffic statistics for the CALC repository in GitHub]({{site.baseurl}}/assets/blog/micro-purchase/micro-purchase-analytics.jpg)
+{% image "assets/blog/micro-purchase/micro-purchase-analytics.jpg" "Traffic statistics for the CALC repository in GitHub" %}
*A snapshot of the analytics for the CALC repository on GitHub.*
Given these statistics, we think it’s fair to say that there is a market for open-source micro-purchasing, though we obviously will need to spend some time and effort refining our methods.
diff --git a/content/posts/2015-11-09-conversation-with-cfpb-natalie-kurz.md b/content/posts/2015-11-09-conversation-with-cfpb-natalie-kurz.md
index 90ed06ef8..0a4a0d4c7 100644
--- a/content/posts/2015-11-09-conversation-with-cfpb-natalie-kurz.md
+++ b/content/posts/2015-11-09-conversation-with-cfpb-natalie-kurz.md
@@ -14,7 +14,7 @@ image: /assets/blog/speaker-series/natalie-kurz.jpg
hero: false
---
-
+{% image_with_class "assets/blog/speaker-series/natalie-kurz.jpg" "image-conversation-with-Kurz" "CFPB's Natalie Kurz" %}
Last month, content strategist and UX designer Natalie Kurz [presented at 18F](https://18f.gsa.gov/2015/11/03/content-strategy-for-all-insights-from-cfpb-natalie-kurz/). Currently a Technology and Innovation Fellow at the [Consumer Financial Protection Bureau](http://www.consumerfinance.gov/), Kurz has spent more than 15 years helping clients create, maintain, and promote beautiful, brand-adherent content.
diff --git a/content/posts/2015-11-10-boston-is-using-gsa-calc-tool.md b/content/posts/2015-11-10-boston-is-using-gsa-calc-tool.md
index 60326a569..28ae77797 100644
--- a/content/posts/2015-11-10-boston-is-using-gsa-calc-tool.md
+++ b/content/posts/2015-11-10-boston-is-using-gsa-calc-tool.md
@@ -31,7 +31,7 @@ The tool, he says, offers city government contracting officers a way to get a br
“One of the challenges cities face in tech procurement is that you're making decisions based solely on information provided by vendors. CALC...can help ensure decisions are fully informed,” he says.
-![The CALC tool in action]({{site.baseurl}}/assets/blog/calc-announcement/calc_demo.gif)
+{% image "assets/blog/calc-announcement/calc_demo.gif" "The CALC tool in action" %}
CALC helps contracting officers determine the range of pricing — at the highest level — for a specific labor category. For example, a search for “Senior Engineer” will return comparable labor categories and their rates, which can be further narrowed by filtering for associated criteria such as years of experience, education level, etc.
diff --git a/content/posts/2015-11-17-choose-design-over-architecture.md b/content/posts/2015-11-17-choose-design-over-architecture.md
index 5b66d4608..f0a264fa1 100644
--- a/content/posts/2015-11-17-choose-design-over-architecture.md
+++ b/content/posts/2015-11-17-choose-design-over-architecture.md
@@ -29,7 +29,7 @@ In short, architectural plans push the team towards [waterfall development](http
## Starting from user stories and user experience
-![A user story generating architecture organically.]({{site.baseurl}}/assets/blog/design-over-architecture/user-story-architecture.jpg)
+{% image "assets/blog/design-over-architecture/user-story-architecture.jpg" "A user story generating architecture organically." %}
*A user story generating architecture organically.*
[User stories](https://en.wikipedia.org/wiki/User_story) are simple scenarios told from the point of view of a person using the software. There can be many types of users for an application. For example, an application might have people consuming the application via a public web page and others who are developers consuming it via an API. The application may also need administrators to establish content or permissions.
@@ -77,7 +77,7 @@ After the team addresses lots of stories, driven by their top priorities, the ar
## Keeping our code from becoming a structureless mess
-![Without good software design techniques, your code can become a mess as you fulfill more user stories.]({{site.baseurl}}/assets/blog/design-over-architecture/messy-code.jpg)
+{% image "assets/blog/design-over-architecture/messy-code.jpg" "Without good software design techniques, your code can become a mess as you fulfill more user stories." %}
*Without good software design techniques, your code can become a mess as you fulfill more user stories.*
Without a guiding architectural map, how does a team keep the code clean and useful?
@@ -97,7 +97,7 @@ Focusing on software design turns the process of getting to architecture on its
Seemingly since the dawn of programming, engineers have been concerned with making code more modular and flexible. In that time, we have developed great guiding principles.
-![Using refactoring to impose design on the chaos that happens with continual development]({{site.baseurl}}/assets/blog/design-over-architecture/refactoring.jpg)
+{% image "assets/blog/design-over-architecture/refactoring.jpg" "Using refactoring to impose design on the chaos that happens with continual development" %}
*Using refactoring to impose design on the chaos that happens with continual development.*
### SOLID
diff --git a/content/posts/2015-11-17-gsa-gov-refreshed-with-eye-toward-mobile-users.md b/content/posts/2015-11-17-gsa-gov-refreshed-with-eye-toward-mobile-users.md
index 32540d599..3a1e373a7 100644
--- a/content/posts/2015-11-17-gsa-gov-refreshed-with-eye-toward-mobile-users.md
+++ b/content/posts/2015-11-17-gsa-gov-refreshed-with-eye-toward-mobile-users.md
@@ -14,7 +14,7 @@ image: /assets/blog/gsa-homepage/gsa-homepage.jpg
hero: false
---
-![A screenshot of the new gsa.gov homepage]({{site.baseurl}}/assets/blog/gsa-homepage/gsa-homepage.jpg)
+{% image "assets/blog/gsa-homepage/gsa-homepage.jpg" "A screenshot of the new gsa.gov homepage" %}
*Originally posted on [GSA's blog](http://gsablogs.gsa.gov/gsablog/2015/11/17/gsa-gov-refreshed-with-eye-toward-mobile-users/).*
diff --git a/content/posts/2015-12-01-how-we-dramatically-improved-18fs-onboarding-process-in-3-months.md b/content/posts/2015-12-01-how-we-dramatically-improved-18fs-onboarding-process-in-3-months.md
index 39caf0dfb..4e7d11648 100644
--- a/content/posts/2015-12-01-how-we-dramatically-improved-18fs-onboarding-process-in-3-months.md
+++ b/content/posts/2015-12-01-how-we-dramatically-improved-18fs-onboarding-process-in-3-months.md
@@ -40,7 +40,7 @@ From the beginning, we conceived of onboarding as a series of
interlinking blocks. Here’s the way we drew our mental model of these
blocks back in September:
-![An early sketch for onboarding modules]({{site.baseurl}}/assets/blog/onboarding/learning-modules.jpg)
+{% image "assets/blog/onboarding/learning-modules.jpg" "An early sketch for onboarding modules" %}
Every 18F employee needs to know certain general stuff: what the [Hatch Act is](https://www.oge.gov/web/oge.nsf/Outside%20Employment%20and%20Activities/88E8E6E11682F97885257E96006364FF?opendocument), where to file
their health insurance, and how to add their biography to our website,
@@ -154,7 +154,7 @@ Mrs. Landingham releases one message per day to new hires over their
first 30 days. The messages are prewritten: when new hires are signed
up, they begin the 30 day cycle of messaging. They look like this:
-![A test conversation with Mrs. Dolores Landingham, the onboarding chat bot.]({{site.baseurl}}/assets/blog/onboarding/dolores.jpg)
+{% image "assets/blog/onboarding/dolores.jpg" "A test conversation with Mrs. Dolores Landingham, the onboarding chat bot." %}
We find that Mrs. Landingham is a fun, easy, and efficient way to
provide information to new hires. She helps them learn about Slack by
diff --git a/content/posts/2015-12-02-analytics-usa-gov-new-features-more-data.md b/content/posts/2015-12-02-analytics-usa-gov-new-features-more-data.md
index 46daf6a9a..f8505977a 100644
--- a/content/posts/2015-12-02-analytics-usa-gov-new-features-more-data.md
+++ b/content/posts/2015-12-02-analytics-usa-gov-new-features-more-data.md
@@ -22,7 +22,7 @@ hero: false
*This post was originally published on the [DigitalGov blog](https://www.digitalgov.gov/2015/12/01/analytics-usa-gov-new-features-and-more-data).*
-![The analytics.usa.gov homepage.]({{site.baseurl}}/assets/blog/dap/analytics-homepage.jpg)
+{% image "assets/blog/dap/analytics-homepage.jpg" "The analytics.usa.gov homepage." %}
As of writing this post, 25,225 of the 124,878 total visitors on federal government websites participating in the [Digital Analytics Program](http://www.digitalgov.gov/services/dap/) (DAP) are NOT located in the United States. And as a result of a new location feature on the expanded [analytics.usa.gov](https://analytics.usa.gov/), you are free to check for yourself how many current users are from outside the country, anytime you’d like.
@@ -35,7 +35,7 @@ Location data
We’ve created two new location charts on the dashboard, one showing the cities providing the most visitors and one showing U.S. vs. international traffic, including a breakdown of the countries with the most visitors outside the U.S. Both of the visualizations reflect data in real-time (updating every minute), so you can wake-up to see which countries are visiting U.S. government websites while we’re asleep! Additionally, while most of the time you’ll see U.S. cities on that particular chart, it is not limited to the United States. If there is a world event and for some reason a large proportion of people in Mumbai, India (for example), are visiting U.S. government websites, the chart will reflect that.
-![A snapshot of location data from analytics.usa.gov]({{site.baseurl}}/assets/blog/dap/analytics-locations.jpg)
+{% image "assets/blog/dap/analytics-locations.jpg" "A snapshot of location data from analytics.usa.gov" %}
One thing to keep in mind about location information is that since we anonymize IP addresses of visitors at the earliest possible point, the location data is not accurate enough to pinpoint exact locations of visitors. With IP addresses anonymized, we rely on the network domain and service provider to determine a relative location. As a result, people visiting from a suburb may appear as visiting from the closest city.
@@ -52,13 +52,13 @@ Two important things to understand about downloads:
PDF files seem to dominate the list, but other extensions in the category include .doc, .xls., .mp3, among others. The data reflects the number of times the file was accessed in the past seven days.
-![A screenshot of a top downloaded item, in this case an Application for Naturalization from USCIS.]({{site.baseurl}}/assets/blog/dap/analytics-downloads.jpg)
+{% image "assets/blog/dap/analytics-downloads.jpg" "A screenshot of a top downloaded item, in this case an Application for Naturalization from USCIS." %}
You can click on the page title, “Application for Naturalization | USCIS,” to go to the page the file is located, or you can click on the file name, “n-400.pdf”, to download (or open) the file right from analytics.usa.gov!
Expanded downloadable files
---------------------------
-
+
{% image "assets/blog/dap/analytics-downloads2.jpg" "width-300px" "A list of types of data you can download from analytics.usa.gov." %}
There’s a limit to how much data we can display on the page for you, so we have greatly expanded the downloadable data reports. We offer downloads of various types of data (some in CSV format and some in JSON) so that you can work with the data yourself!
diff --git a/content/posts/2015-12-03-power-of-mindset-normatives-matthew-milan.md b/content/posts/2015-12-03-power-of-mindset-normatives-matthew-milan.md
index 41e0281d3..fc3e70528 100644
--- a/content/posts/2015-12-03-power-of-mindset-normatives-matthew-milan.md
+++ b/content/posts/2015-12-03-power-of-mindset-normatives-matthew-milan.md
@@ -20,7 +20,9 @@ What changed?
In short, *how* Engelbart’s unique mindset was presented shifted his colleagues’ opinion of him. Stewart Brand, editor of the Whole Earth Catalog and co-founder of the Long Now Foundation, helped to shape Engelbart’s raw material into a presentation that was direct, convincing, and easy to comprehend.
-
+
This concept — the transformative power of shared mindset — was the focus of Matthew Milan’s recent talk for the 18F Design Presents speaker series. Milan, founder of and design leader at software design firm [Normative](http://www.normative.com/), has fifteen years’ experience in the domain of emerging technologies, and he excels at translating complex information into compelling user experiences.
diff --git a/content/posts/2015-12-07-what-exactly-do-we-even-do-all-day.md b/content/posts/2015-12-07-what-exactly-do-we-even-do-all-day.md
index 52eb68944..d4ec522d7 100644
--- a/content/posts/2015-12-07-what-exactly-do-we-even-do-all-day.md
+++ b/content/posts/2015-12-07-what-exactly-do-we-even-do-all-day.md
@@ -54,7 +54,7 @@ addition to open sourcing our code on GitHub, the combined EPA
e-Manifest and 18F team adopted Trello as our project management tool,
and [set it to public](https://trello.com/b/0geMlbgF/epa-emanifest).
-[![The public Trello board for the e-Manifest project]({{site.baseurl}}/assets/blog/e-manifest/e-manifest-trello.jpg)](https://trello.com/b/0geMlbgF/epa-emanifest)
+[{% image "assets/blog/e-manifest/e-manifest-trello.jpg" "The public Trello board for the e-Manifest project" %}](https://trello.com/b/0geMlbgF/epa-emanifest)
*The public Trello board for the e-Manifest project.*
We shared the link with internal stakeholders at EPA, OMB, and in
diff --git a/content/posts/2015-12-08-using-emoji-for-knowledge-sharing.md b/content/posts/2015-12-08-using-emoji-for-knowledge-sharing.md
index f52f8831b..a0c7dc9cf 100644
--- a/content/posts/2015-12-08-using-emoji-for-knowledge-sharing.md
+++ b/content/posts/2015-12-08-using-emoji-for-knowledge-sharing.md
@@ -36,7 +36,7 @@ So I tried an experiment: I asked my 18F coworkers to tag
messages *that every new 18F employee should know* with the
:evergreen_tree: emoji.
-![Melody Kramer explaining how to tag messages on Slack]({{site.baseurl}}/assets/blog/onboarding/evergreen-tree.png)
+{% image "assets/blog/onboarding/evergreen-tree.png" "Melody Kramer explaining how to tag messages on Slack" %}
This allowed me to search Slack using this command:
"has::evergreen_tree:" to surface all of the tips and tricks my
diff --git a/content/posts/2015-12-09-an-open-source-government-is-a-faster-more-efficient-government.md b/content/posts/2015-12-09-an-open-source-government-is-a-faster-more-efficient-government.md
index c5aef09ea..82c8638e6 100644
--- a/content/posts/2015-12-09-an-open-source-government-is-a-faster-more-efficient-government.md
+++ b/content/posts/2015-12-09-an-open-source-government-is-a-faster-more-efficient-government.md
@@ -58,7 +58,7 @@ months of time, allowing our small team to focus on issues with
ATF-specific regulations, branding, and deployment. This is the great,
fulfilled promise of open source; we reap the benefits every day.
-![A comparison of CFPB's eRegs and ATF's eRegs]({{site.baseurl}}/assets/blog/atf/eregs-comparison.jpg)
+{% image "assets/blog/atf/eregs-comparison.jpg" "A comparison of CFPB's eRegs and ATF's eRegs" %}
Collaborating with our peers
----------------------------
diff --git a/content/posts/2015-12-11-how-we-test-18f-gsa-gov.md b/content/posts/2015-12-11-how-we-test-18f-gsa-gov.md
index a2d97c788..03ae52b7b 100644
--- a/content/posts/2015-12-11-how-we-test-18f-gsa-gov.md
+++ b/content/posts/2015-12-11-how-we-test-18f-gsa-gov.md
@@ -20,7 +20,7 @@ hero: false
[About a year ago](https://18f.gsa.gov/2014/11/17/taking-control-of-our-website-with-jekyll-and-webhooks/) we converted this site to run fully on Jekyll and migrated our blog from Tumblr. When we did that we gained some freedom and the ability to edit our content on GitHub. We’ve received quite a few pull requests from readers to fix typos and optimize images. As our blog got more complicated, we started making mistakes that were hard to catch before publishing. So we came up with a way to catch many of those errors, before they end up in your browser.
-![A screenshot of an image error]({{site.baseurl}}/assets/blog/18f-site/site-with-tests.png)
+{% image "assets/blog/18f-site/site-with-tests.png" "A screenshot of an image error" %}
*Basic content problems are a pain. This is why we run automated tests on 18f.gsa.gov.*
One advantage of hosting our site’s code on GitHub is we can integrate with continuous integration (CI) services to check our work before we publish. Many open source projects use a CI to run various tests on their code. We use it to run tests on our content. We use Travis CI but there are many others out there. Until recently, the only test we ran was building the site to know if it was successful.
diff --git a/content/posts/2015-12-15-how-bot-named-dolores-landingham-transformed-18fs-onboarding.md b/content/posts/2015-12-15-how-bot-named-dolores-landingham-transformed-18fs-onboarding.md
index cf7287561..2f1ce57da 100644
--- a/content/posts/2015-12-15-how-bot-named-dolores-landingham-transformed-18fs-onboarding.md
+++ b/content/posts/2015-12-15-how-bot-named-dolores-landingham-transformed-18fs-onboarding.md
@@ -47,7 +47,7 @@ Naming is a fun and important step for any project. 18F already had a Slackbot n
Then, Greg Boone suggested “Landingham”, which was immediately greeted with a heart-eyes emoji reaction. There are many [West Wing](https://en.wikipedia.org/wiki/The_West_Wing) fans at 18F, and something felt right about bringing back the beloved character Dolores Landingham, who served as fictional President Bartlett’s wise and sometimes ornery secretary, to guide new employees through the turbulent waters of onboarding.
-![Screenshot of Dolores Landingham being named.]({{site.baseurl}}/assets/blog/onboarding/landingham-slack.jpg)
+{% image "assets/blog/onboarding/landingham-slack.jpg" "Screenshot of Dolores Landingham being named." %}
Voila! `Mrs. Landingham` was born.
diff --git a/content/posts/2015-12-16-useiti-whats-in-first-report.md b/content/posts/2015-12-16-useiti-whats-in-first-report.md
index 1471c5c40..880e78952 100644
--- a/content/posts/2015-12-16-useiti-whats-in-first-report.md
+++ b/content/posts/2015-12-16-useiti-whats-in-first-report.md
@@ -32,7 +32,7 @@ U.S. Department of the Interior released the first report from the
United States, a major step toward becoming [fully compliant with the global EITI standard](https://eiti.org/countries). You should
really stop reading this post and [check it out for yourself](https://useiti.doi.gov).
-![A screen shot of the new USEITI homepage]({{site.baseurl}}/assets/blog/eiti/useiti-homepage.png)
+{% image "assets/blog/eiti/useiti-homepage.png" "A screen shot of the new USEITI homepage" %}
This project is the culmination of hard work and years of effort across
many parts of the U.S. government and collaboration among the [39
@@ -59,7 +59,7 @@ for a more detailed view of where money came from. From there you can
[filter by commodity](https://useiti.doi.gov/explore/federal-revenue-by-location/#region=MN&year=2013&group=minerals&commodity=Copper) or year. You can [learn a lot by exploring the data](https://useiti.doi.gov/explore/). In some places you can watch industries grow, like [oil and gas in North Dakota](https://useiti.doi.gov/explore/federal-revenue-by-location/#region=ND&group=oilgas&year=2013). You can spot major production centers like Campbell County, WY, which produced almost [35 percent of all coal in the U.S. in
2013](https://useiti.doi.gov/explore/all-lands-production/#year=2013&product=Coal+(short+tons)®ion=WY). Nearly 88 percent of that coal was [produced on federal lands](https://useiti.doi.gov/explore/all-lands-production/#year=2013&product=Coal+(short+tons)®ion=WY), accounting for 80 percent of federal revenue [from coal](https://federalist.18f.gov/preview/18F/doi-extractives-data/dev/explore/federal-revenue-by-location/#region=WY&year=2013&group=coal).
-[![A snapshot of the total federal revenue visualization from the USEITI website]({{site.baseurl}}/assets/blog/eiti/fed-revenues.png)](https://useiti.doi.gov/explore/federal-revenue-by-location/)
+[{% image "assets/blog/eiti/fed-revenues.png" "A snapshot of the total federal revenue visualization from the USEITI website" %}](https://useiti.doi.gov/explore/federal-revenue-by-location/)
*A map from the 2015 USEITI report showing federal revenue data for all locations in 2013. [Explore other years and specific commodities on the site.](https://useiti.doi.gov/explore/federal-revenue-by-location/)*
diff --git a/content/posts/2015-12-17-plain-language-betafec-new-content-design.md b/content/posts/2015-12-17-plain-language-betafec-new-content-design.md
index 3d4921c82..a250a5ff1 100644
--- a/content/posts/2015-12-17-plain-language-betafec-new-content-design.md
+++ b/content/posts/2015-12-17-plain-language-betafec-new-content-design.md
@@ -38,7 +38,7 @@ This launch also includes a checklist of essential information for candidates an
Eventually, we’ll launch an essentials checklist for every type of FEC registrant.
-[![The new checklist for what you need to do to register with the FEC]({{site.baseurl}}/assets/blog/fec/checklist.jpg)](https://beta.fec.gov/registration-and-reporting/essentials-house-and-senate-candidates-and-committees/)
+[{% image "assets/blog/fec/checklist.jpg" "The new checklist for what you need to do to register with the FEC" %}](https://beta.fec.gov/registration-and-reporting/essentials-house-and-senate-candidates-and-committees/)
Plain language was an important goal for this project. It lowers the bar of entry for readers — we don’t want folks to **need** a lawyer just to clarify the most basic campaign finance information. We also wanted the site to be a resource for journalists and researchers looking for background information.
@@ -46,7 +46,7 @@ Because of the intricacy of campaign finance law, we had to keep some technical
Even so, we didn’t want our readers to get lost navigating the site. A glossary tool allows readers to click an icon next to legal terms and read the definition.
-[![The new integrated glossary in action on betafec.gov]({{site.baseurl}}/assets/blog/fec/glossary.jpg)](https://beta.fec.gov/registration-and-reporting/essentials-house-and-senate-candidates-and-committees/)
+[{% image "assets/blog/fec/glossary.jpg" "The new integrated glossary in action on betafec.gov" %}](https://beta.fec.gov/registration-and-reporting/essentials-house-and-senate-candidates-and-committees/)
What folks are saying
---------------------
diff --git a/content/posts/2015-12-23-looking-back-2015-our-own-words.md b/content/posts/2015-12-23-looking-back-2015-our-own-words.md
index 77999e81c..589055304 100644
--- a/content/posts/2015-12-23-looking-back-2015-our-own-words.md
+++ b/content/posts/2015-12-23-looking-back-2015-our-own-words.md
@@ -33,7 +33,7 @@ Below, everyone at 18F shares what they learned, what they did, and how they gre
“I loved organizing the accessibility hackathon and it’s been a blast working on the [micropurchase experiment](https://18f.gsa.gov/2015/10/13/open-source-micropurchasing/) and the [Agile BPA](https://18f.gsa.gov/2015/06/15/agile-bpa-is-here/) work.” - **Alan deLevie**
-![The crowd at the hackathon]({{site.baseurl}}/assets/blog/a11yhack/a11yhack.jpg)
+{% image "assets/blog/a11yhack/a11yhack.jpg" "The crowd at the hackathon" %}
_Photo: Jameson Dempesy_
## Blog
@@ -50,7 +50,7 @@ _Photo: Jameson Dempesy_
“I thoroughly enjoyed helping agencies get their .gov domains hardcoded into browsers as secure.“ - **Eric Mill**
-![Snapshot of the first HSTS preloaded government domains.]({{site.baseurl}}/assets/blog/hsts/hsts-preload-list.png)
+{% image "assets/blog/hsts/hsts-preload-list.png" "Snapshot of the first HSTS preloaded government domains." %}
_Since we wrote about it in February, 14 more.gov domains have been fully preloaded._
## Diversity Working Group
@@ -73,7 +73,7 @@ _Since we wrote about it in February, 14 more.gov domains have been fully preloa
“I feel honored to be part of the analytics.usa.gov team every time I see another government office use our open source project to make their analytics data publicly available.” - **Gabriel Ramirez**
-![The analytics.usa.gov homepage.]({{site.baseurl}}/assets/blog/dap/analytics-homepage.jpg)
+{% image "assets/blog/dap/analytics-homepage.jpg" "The analytics.usa.gov homepage." %}
### betaFEC
@@ -83,7 +83,7 @@ _Since we wrote about it in February, 14 more.gov domains have been fully preloa
“I loved working on the team that helped make betaFEC. It was especially exciting to help our partners at the FEC find how they wanted to express their agency through a modernized web experience, and build an updated look and feel with them.” - **Jennifer Thibault**
-![The betaFEC glossary]({{site.baseurl}}/assets/blog/fec/glossary.jpg)
+{% image "assets/blog/fec/glossary.jpg" "The betaFEC glossary" %}
### CALC
@@ -91,7 +91,7 @@ _Since we wrote about it in February, 14 more.gov domains have been fully preloa
“Working on [CALC](https://calc.gsa.gov/ "The CALC Tool") was meaningful to me, because I know it is saving people hours of work every week, and saving the taxpayers millions of dollars.” - **Nick Brethauer**
-![The CALC homepage]({{site.baseurl}}/assets/blog/calc-announcement/calc_homepage.jpg)
+{% image "assets/blog/calc-announcement/calc_homepage.jpg" "The CALC homepage" %}
### cloud.gov
@@ -105,7 +105,7 @@ _Since we wrote about it in February, 14 more.gov domains have been fully preloa
“Many of us have experienced firsthand how security compliance requirements may hinder the government's ability to ship new projects. I'm proud to be working on methods for accelerating the compliance process in the open and excited to see the support and contributions of the open source community.” - **Gabriel Ramirez**
-![The cloud.gov homepage]({{site.baseurl}}/assets/blog/cloud-gov/cloud-gov-homepage.jpg)
+{% image "assets/blog/cloud-gov/cloud-gov-homepage.jpg" "The cloud.gov homepage" %}
### College Scorecard
@@ -113,7 +113,7 @@ _Since we wrote about it in February, 14 more.gov domains have been fully preloa
“I really enjoyed working with USDS, 18F and the Department of Education on [https://collegescorecard.ed.gov](https://collegescorecard.ed.gov) because it demonstrated how multiple agencies can come together to build something great." - **Ozzy Johnson**
-![Paper prototype testing the college scorecard]({{site.baseurl}}/assets/blog/college-scorecard/college-scorecard-3.jpg)
+{% image "assets/blog/college-scorecard/college-scorecard-3.jpg" "Paper prototype testing the college scorecard" %}
### DATA Act
@@ -121,7 +121,7 @@ _Since we wrote about it in February, 14 more.gov domains have been fully preloa
“The best thing I worked on was the DATA Act. In 2012, I first wrote about DATA Act. In 2013, I visited my reps on Capitol Hill about voting for it. In 2014, I went to the Treasury’s federal spending data town hall and kvetched about poor data quality. And then in 2015, I worked with those same Treasury folks to get it fixed.” - **Becky Sweger**
-![Diagram of government appropriation reporting]({{site.baseurl}}/assets/blog/data-act-implementation/data-act-reporting.jpg)
+{% image "assets/blog/data-act-implementation/data-act-reporting.jpg" "Diagram of government appropriation reporting" %}
_Image courtesy of the [Data Transparency Coalition](http://www.datacoalition.org/what-is-data-transparency/data-act/)_
### Draft U.S. Web Design Standards
@@ -136,7 +136,7 @@ _Image courtesy of the [Data Transparency Coalition](http://www.datacoalition.or
“I’m proud to have [started a project](http://github.com/18F/web-design-standards-drupal "A Drupal Theme") that will make the U.S. \[Draft\] Web Design Standards easier to use for the >25% of U.S. government websites that run on Drupal. I’m working with members of the larger Drupal community as well as people in government to help these standards scale without the need for custom development.” — **Rhys Fureigh**
-![The web design standards on multiple sizes of screen]({{site.baseurl}}/assets/blog/web-design-standards/home.png)
+{% image "assets/blog/web-design-standards/home.png" "The web design standards on multiple sizes of screen" %}
_The U.S. Web Design Standards are designed to be viewed on any device._
### U.S. Extractive Industries Transparency Initiative
@@ -145,7 +145,7 @@ _The U.S. Web Design Standards are designed to be viewed on any device._
“EITI reports have traditionally been thick, printed PDFs full of statistics, meant for a specialist audience. It was so great to be a part of the U.S. process that is leading the world in making this data available online along with tons of rich contextual information to make it understandable.” - **Michelle Hertzfeld**
-![A map of the U.S. visualizing federal natural resource revenues]({{site.baseurl}}/assets/blog/eiti/fed-revenues.png)
+{% image "assets/blog/eiti/fed-revenues.png" "A map of the U.S. visualizing federal natural resource revenues" %}
### Every Kid in a Park
@@ -155,7 +155,7 @@ _The U.S. Web Design Standards are designed to be viewed on any device._
“Working on the content design for Every Kid in a Park reminded me that government websites **can** be joyful, inclusive, and easy to read.” - **Emileigh Barnes**
-![The kid-friendly 404 page for everykidinapark.gov]({{site.baseurl}}/assets/blog/every-kid-in-a-park/404.png)
+{% image "assets/blog/every-kid-in-a-park/404.png" "The kid-friendly 404 page for everykidinapark.gov" %}
_The Every Kid in a Park 404, not found page, designed for fourth graders._
### Federalist
@@ -168,7 +168,7 @@ _The Every Kid in a Park 404, not found page, designed for fourth graders._
“I’m really proud of the work I did on Federalist because it helped streamline the launch of sites that addressed [college affordability data](https://collegescorecard.ed.gov/ "College Scorecard") and the [quantity of natural resources being extracted from federal lands](https://useiti.doi.gov/ "USEITI").” - **Jeremia Kimelman**
-![The Social and Behavior Sciences homepage]({{site.baseurl}}/assets/blog/federalist/sbst-screenshot-2.jpg)
+{% image "assets/blog/federalist/sbst-screenshot-2.jpg" "The Social and Behavior Sciences homepage" %}
_The Social and Behavioral Sciences team was the first adopter for Federalist._
### SBIR-EZ
@@ -183,7 +183,7 @@ _The Social and Behavioral Sciences team was the first adopter for Federalist._
“I really enjoyed partnering with US Treasury to [craft the digital strategy](https://18f.gsa.gov/2015/07/17/the-new-10/ "18F: The new 10") for #TheNew10. We're putting a woman on the $10 bill!" - **Kara DeFrias**
-![The new $10 homepage]({{site.baseurl}}/assets/blog/the-new-10/the-new-10.jpg)
+{% image "assets/blog/the-new-10/the-new-10.jpg" "The new $10 homepage" %}
### USCIS
@@ -191,7 +191,7 @@ _The Social and Behavioral Sciences team was the first adopter for Federalist._
“This year I made [an account system](http://myaccount.uscis.dhs.gov/ "My Account, MyUSCIS") that helps immigrants keep their information up to date. It now has hundreds of thousands of users.” - **Sasha Magee**
-![The MyUSCIS homepage]({{site.baseurl}}/assets/blog/myuscis/myuscis.jpg)
+{% image "assets/blog/myuscis/myuscis.jpg" "The MyUSCIS homepage" %}
## Guides, resources, and tools
@@ -203,7 +203,7 @@ _The Social and Behavioral Sciences team was the first adopter for Federalist._
“The first thing I worked on at 18F was the Design Methods. Teaching tools of great design has been part of this job since I started, which means learning tools of great design has been part of this job since I started. I’ve never learned so much in such a small amount of time.” - **James Hupp**
-![The method cards]({{site.baseurl}}/assets/blog/design-method-cards/method-cards-banner.jpg)
+{% image "assets/blog/design-method-cards/method-cards-banner.jpg" "The method cards" %}
_The 18F Design Method cards are open source to download and print off._
### Partnership Playbook
@@ -242,7 +242,7 @@ _The 18F Design Method cards are open source to download and print off._
“I've spent the last few months working with the pesticides division of the EPA, helping them modernize the way that pesticide labels are accessed and analyzed by inspectors. Pesticide labels are a surprisingly complex and important thing to get right, because when they're wrong people can (and do) die. Bringing modern technology into the work the field inspectors do every single day is going to significantly improve their ability to do their job, and I feel incredibly lucky to get to help with that and know that what I'm doing could genuinely help save lives.” - **Lane Becker**
-![A group of government executives playing with legos.]({{site.baseurl}}/assets/blog/lego-workshop/sba-execs-legos.jpg)
+{% image "assets/blog/lego-workshop/sba-execs-legos.jpg" "A group of government executives playing with legos." %}
_We spent 90 minutes working with legos to teach the Small Business Administration agile development._
### Process and documentation
@@ -261,7 +261,7 @@ _We spent 90 minutes working with legos to teach the Small Business Administrati
“I think the best thing that I've made this year has been the Official Guide to Travel at 18F. Taking on the complexity of Concur and the rules of government travel and splitting them into manageable steps seems to have reduced confusion as well as the amount of time spent helping people stuck in various parts of the process. I'm excited to continue the work in 2016, pinpointing the remaining areas of confusion and improving the Guide to address those.” - **Ethan Heppner**
-![A test conversation with Dolores Landingham]({{site.baseurl}}/assets/blog/onboarding/dolores.jpg)
+{% image "assets/blog/onboarding/dolores.jpg" "A test conversation with Dolores Landingham" %}
### Growing our team
diff --git a/content/posts/2015-12-30-turning-learning-up-to-11.md b/content/posts/2015-12-30-turning-learning-up-to-11.md
index 25ecfa8b9..c5032d0c3 100644
--- a/content/posts/2015-12-30-turning-learning-up-to-11.md
+++ b/content/posts/2015-12-30-turning-learning-up-to-11.md
@@ -18,7 +18,7 @@ image: /assets/blog/turn-up-to-11/turn-up-to-11.jpg
hero: false
---
-[![A screenshot from the movie Spinal Tap showing a guitar amp dial that goes up to 11]({{ site.baseurl }}/assets/blog/turn-up-to-11/turn-up-to-11.jpg)](https://en.wikipedia.org/wiki/Up_to_eleven)
+[{% image "assets/blog/turn-up-to-11/turn-up-to-11.jpg" "A screenshot from the movie Spinal Tap showing a guitar amp dial that goes up to 11" %}](https://en.wikipedia.org/wiki/Up_to_eleven)
The feature that distinguishes high-performing organizations across all industries is their ability to facilitate knowledge sharing across the entire organization. Organizations that then put this knowledge to use to improve how they work have a sustained competitive advantage. Accomplishing this requires a combination of values, processes, and tools.
diff --git a/content/posts/2016-01-04-turning-learning-up-to-11-transparency.md b/content/posts/2016-01-04-turning-learning-up-to-11-transparency.md
index 5b1bb311c..2bfe1e134 100644
--- a/content/posts/2016-01-04-turning-learning-up-to-11-transparency.md
+++ b/content/posts/2016-01-04-turning-learning-up-to-11-transparency.md
@@ -14,7 +14,7 @@ image: /assets/blog/turn-up-to-11/skeleton-t-shirt.jpg
hero: false
---
-[![A man wearing a skeleton t-shirt from the movie Spinal Tap]({{ site.baseurl }}/assets/blog/turn-up-to-11/skeleton-t-shirt.jpg)](https://i.ytimg.com/vi/XuzpsO4ErOQ/maxresdefault.jpg)[*“This is my exact inner structure, done in a tee shirt. Exactly medically accurate. See?”*](http://www.imdb.com/title/tt0088258/quotes?item=qt0261729)
+[{% image "assets/blog/turn-up-to-11/skeleton-t-shirt.jpg" "A man wearing a skeleton t-shirt from the movie Spinal Tap" %}](https://i.ytimg.com/vi/XuzpsO4ErOQ/maxresdefault.jpg)[*“This is my exact inner structure, done in a tee shirt. Exactly medically accurate. See?”*](http://www.imdb.com/title/tt0088258/quotes?item=qt0261729)
In the [first post of this trilogy](https://18f.gsa.gov/2015/12/30/turning-learning-up-to-11/), I summarized my DevOps Enterprise 2015 talk that focused on transparency, autonomy, and collaboration as primary factors in producing organizational culture change. In this post, I’ll describe a few of the initiatives we’ve undertaken to increase transparency into 18F’s internal operations. While primarily for the benefit of our team members, we hope they will inspire other organizations to adopt similar models and tools.
diff --git a/content/posts/2016-01-07-announcing-the-18f-micro-purchase-platform.md b/content/posts/2016-01-07-announcing-the-18f-micro-purchase-platform.md
index af5586ae7..d7debf75e 100644
--- a/content/posts/2016-01-07-announcing-the-18f-micro-purchase-platform.md
+++ b/content/posts/2016-01-07-announcing-the-18f-micro-purchase-platform.md
@@ -30,7 +30,7 @@ We’ll be posting batches of new tasks onto the micro-purchase platform
in the coming weeks, and bidders will once again have an opportunity to
contribute open source code to our projects for $3,500 or less.
-[![The homepage of the new micro-purchase platform]({{ site.baseurl }}/assets/blog/micro-purchase/micro-purchase-homepage.jpg)
+[{% image "assets/blog/micro-purchase/micro-purchase-homepage.jpg" "The homepage of the new micro-purchase platform" %}
](http://micropurchase.18f.gov)
## Developing a posting and bidding platform
diff --git a/content/posts/2016-01-08-18f-new-years-resolution-be-even-more-open.md b/content/posts/2016-01-08-18f-new-years-resolution-be-even-more-open.md
index e70921283..187aa050e 100644
--- a/content/posts/2016-01-08-18f-new-years-resolution-be-even-more-open.md
+++ b/content/posts/2016-01-08-18f-new-years-resolution-be-even-more-open.md
@@ -69,7 +69,7 @@ to](https://github.com/18F/18f.gsa.gov/issues/1445):
be more explicit about how to contribute after finding a bug or
error.
-![Screen shot of a Slack conversation about adding language to encourage contributions to documentation.]({{ site.baseurl }}/assets/blog/open-source/documentation.jpg)
+{% image "assets/blog/open-source/documentation.jpg" "Screen shot of a Slack conversation about adding language to encourage contributions to documentation." %}
- **Communicate our needs by figuring out better ways to ask for
help**. We want to be more explicit and vocal about expressing our
diff --git a/content/posts/2016-01-12-hacking-inclusion-by-customizing-a-slack-bot.md b/content/posts/2016-01-12-hacking-inclusion-by-customizing-a-slack-bot.md
index 308f3dd2e..57e61da4b 100644
--- a/content/posts/2016-01-12-hacking-inclusion-by-customizing-a-slack-bot.md
+++ b/content/posts/2016-01-12-hacking-inclusion-by-customizing-a-slack-bot.md
@@ -42,7 +42,7 @@ Did you mean *y'all*?
Here’s what it looks like in action:
-![screenshot: Slackbot showing alternative responses to phrase 'Hey guys']({{ site.baseurl }}/assets/blog/hacking-inclusion/slackbot-replacing-guys-with-other-words.png)
+{% image "assets/blog/hacking-inclusion/slackbot-replacing-guys-with-other-words.png" "screenshot: Slackbot showing alternative responses to phrase 'Hey guys'" %}
Turns out, a little cultural hack can go a long way. It’s easy to forget these things and say guys unconsciously, but a nice, friendly, automated reminder solves that issue, and reduces the need for any kind of person-to-person conversation.
diff --git a/content/posts/2016-01-15-micro-purchase-auctions-round-2-what-we-learned.md b/content/posts/2016-01-15-micro-purchase-auctions-round-2-what-we-learned.md
index 6a15e4480..e0cbd5c91 100644
--- a/content/posts/2016-01-15-micro-purchase-auctions-round-2-what-we-learned.md
+++ b/content/posts/2016-01-15-micro-purchase-auctions-round-2-what-we-learned.md
@@ -14,7 +14,7 @@ image: /assets/blog/micro-purchase/closed-auctions.jpg
hero: false
---
-![A screenshot of two closed auctions]({{ site.baseurl }}/assets/blog/micro-purchase/closed-auctions.jpg)
+{% image "assets/blog/micro-purchase/closed-auctions.jpg" "A screenshot of two closed auctions" %}
The auctions have closed, the [bids are
in](https://micropurchase.18f.gov/), the [winners are off
diff --git a/content/posts/2016-02-12-happy-valentines-day-from-18F.md b/content/posts/2016-02-12-happy-valentines-day-from-18F.md
index 938e68ee5..1898b7013 100644
--- a/content/posts/2016-02-12-happy-valentines-day-from-18F.md
+++ b/content/posts/2016-02-12-happy-valentines-day-from-18F.md
@@ -23,17 +23,17 @@ These tools — and these Valentine’s Day cards — follow industry-standard w
So spread a little love this Valentine’s Day...because nothing says “I love you” like sharing our Draft U.S. Web Design Standards cards.
-![The draft web standards accordion with a valentines message exposed.]({{site.baseurl}}/assets/img/vday/accordion.png)
+{% image "assets/img/vday/accordion.png" "The draft web standards accordion with a valentines message exposed." %}
**Accordion to me, you’re the best.**
-![A valentines message floating above the draft web standards logo.]({{site.baseurl}}/assets/img/vday/no-standard-way.png)
+{% image "assets/img/vday/no-standard-way.png" "A valentines message floating above the draft web standards logo." %}
**There’s no standard way to say I love you this Valentine’s day.**
-![Valentines messages written on the draft web standards button templates.]({{site.baseurl}}/assets/img/vday/press-all-buttons.png)
+{% image "assets/img/vday/press-all-buttons.png" "Valentines messages written on the draft web standards button templates." %}
**You press all my buttons.**
-![A heart superimposed over the draft web standards grid]({{site.baseurl}}/assets/img/vday/entire-grid.png)
+{% image "assets/img/vday/entire-grid.png" "A heart superimposed over the draft web standards grid" %}
**My heart would fill this entire grid.**
-![A rose and a violet with a valentines message.]({{site.baseurl}}/assets/img/vday/roses-violets.png)
+{% image "assets/img/vday/roses-violets.png" "A rose and a violet with a valentines message." %}
**Roses are #E31C3D Violets are #0071BC.**
diff --git a/content/posts/2016-02-18-analytics.usa.gov-agency-specific-dashboards.md b/content/posts/2016-02-18-analytics.usa.gov-agency-specific-dashboards.md
index e435fdf76..51ddb2c5f 100644
--- a/content/posts/2016-02-18-analytics.usa.gov-agency-specific-dashboards.md
+++ b/content/posts/2016-02-18-analytics.usa.gov-agency-specific-dashboards.md
@@ -18,7 +18,7 @@ hero: false
We’ve added agency-specific dashboards to [analytics.usa.gov](https://analytics.usa.gov/)!
-![The analytics dashboard for the Department of Commerce]({{site.baseurl}}/assets/blog/dap/analytics-commerce.jpg)
+{% image "assets/blog/dap/analytics-commerce.jpg" "The analytics dashboard for the Department of Commerce" %}
Starting today, you’ll see a dropdown from the main [analytics.usa.gov](https://analytics.usa.gov/) page that allows you to view the same dashboard, but filtered for websites that are administered by one of 10 specific agencies:
@@ -38,7 +38,7 @@ What do these pages show me?
These dashboard pages allow for greater insight into how the public interacts with specific agency websites as a complement to the aggregated view available at analytics.usa.gov. In many cases, the information we see as a government-wide percentage does not perfectly mirror an individual agency’s data. For example, at time of writing this post, the domestic vs. foreign traffic on the whole of participating Digital Analytics Program (DAP) sites is about 90% to 10%, respectively. But the Veteran’s Administration specifically has a 98% to 2% ratio, while NASA has a 67% to 33% domestic to foreign visits ratio.
-![Comparison of traffic broken down by country for NASA and the VA]({{site.baseurl}}/assets/blog/dap/traffic-by-country.jpg)
+{% image "assets/blog/dap/traffic-by-country.jpg" "Comparison of traffic broken down by country for NASA and the VA" %}
The pages also allow you to see things like the most popular downloads at an agency-level. During tax season, the IRS contributes the majority of downloads in the “Top Downloads” section on analytics.usa.gov, which is logical since it is tax season. With agency dashboards, you can observe downloads at the agency level.
diff --git a/content/posts/2016-02-19-how-and-why-we-built-the-micro-purchase-platform.md b/content/posts/2016-02-19-how-and-why-we-built-the-micro-purchase-platform.md
index 03eecc806..b635245dd 100644
--- a/content/posts/2016-02-19-how-and-why-we-built-the-micro-purchase-platform.md
+++ b/content/posts/2016-02-19-how-and-why-we-built-the-micro-purchase-platform.md
@@ -30,7 +30,7 @@ is a look at how and why we built this platform.
Testing a hypothesis with a minimum viable product
--------------------------------------------------
-[![The first version of the micro-purchase experiment used a GitHub issue to track bids.]({{site.baseurl}}/assets/blog/micro-purchase/micro-purchase-issue.jpg)](https://github.com/18F/calc/issues/255)
+[{% image "assets/blog/micro-purchase/micro-purchase-issue.jpg" "The first version of the micro-purchase experiment used a GitHub issue to track bids." %}](https://github.com/18F/calc/issues/255)
For the [first micro-purchase
auction](https://github.com/18F/calc/issues/255), we launched a minimum
@@ -50,7 +50,7 @@ worked good enough but was not something we would want to keep using.
Building a platform
-------------------
-[![The micro-purchase platform site.]({{site.baseurl}}/assets/blog/micro-purchase/micro-purchase-homepage2.jpg)](https://micropurchase.18f.gov)
+[{% image "assets/blog/micro-purchase/micro-purchase-homepage2.jpg" "The micro-purchase platform site." %}](https://micropurchase.18f.gov)
After the initial auction, our hypothesis was proven: many vendors
placed bids, and the winning vendor successfully delivered the
diff --git a/content/posts/2016-02-29-informing-the-future-of-the-federal-front-door.md b/content/posts/2016-02-29-informing-the-future-of-the-federal-front-door.md
index f36311889..d9672ecdf 100644
--- a/content/posts/2016-02-29-informing-the-future-of-the-federal-front-door.md
+++ b/content/posts/2016-02-29-informing-the-future-of-the-federal-front-door.md
@@ -119,7 +119,7 @@ right, that there are negative consequences for doing something wrong,
and their request is being treated as a potentially fraudulent rather
than coming from a place of real need.
-![An infographic showing sources of pressure and types of emotions a person might feel after different interactions with the government.]({{site.baseurl}}/assets/blog/federal-front-door/image02.jpg)
+{% image "assets/blog/federal-front-door/image02.jpg" "An infographic showing sources of pressure and types of emotions a person might feel after different interactions with the government." %}
### Choice overload
@@ -154,7 +154,7 @@ websites and services.
-
+{% image "assets/blog/federal-front-door/image01.jpg" "A two-by-two grid showing how people think when confidence is plotted against resilience. When confidence and resilience are both high, people “will keep trying until a goal is achieved.” When confidence is high but resilience is low, people may apply once but will give up if it doesn't go well. With resilience high and low confidence, people may try a few times but will doubt themselves. And when both resilience and confidence are low, they probably won't apply at all." %}
Before using a government service or applying for benefits, people
@@ -188,7 +188,7 @@ is required for the specific interaction. How people feel about
providing that information, and how it might be used both for their
current interaction and potential future ones is a bit of a mixed bag.
-![A graphic showing how people might view sharing information. Some never want their information shared, and others are on a continuum.]({{site.baseurl}}/assets/blog/federal-front-door/image03.jpg)
+{% image "assets/blog/federal-front-door/image03.jpg" "A graphic showing how people might view sharing information. Some never want their information shared, and others are on a continuum." %}
### Access to personal information
@@ -198,7 +198,7 @@ government, manage requests for their information, see who is accessing
their information, and understand that their information is secure and
not being shared outside of the federal government.
-![An infographic illustrating that people expect personal information like medical records, family information, and financial records to be safe from ID thieves, advertisers and third parties.]({{site.baseurl}}/assets/blog/federal-front-door/image00.jpg)
+{% image "assets/blog/federal-front-door/image00.jpg" "An infographic illustrating that people expect personal information like medical records, family information, and financial records to be safe from ID thieves, advertisers and third parties." %}
### **What’s next?**
diff --git a/content/posts/2016-03-02-strategies-people-use-when-interacting-with-the-federal-government.md b/content/posts/2016-03-02-strategies-people-use-when-interacting-with-the-federal-government.md
index de65c02fe..37388a6a3 100644
--- a/content/posts/2016-03-02-strategies-people-use-when-interacting-with-the-federal-government.md
+++ b/content/posts/2016-03-02-strategies-people-use-when-interacting-with-the-federal-government.md
@@ -24,7 +24,7 @@ _This is part two of a series detailing the findings of a team of researchers fr
_In yesterday’s post, we [detailed our initial research questions](https://18f.gsa.gov/2016/03/01/what-we-learned-after-interviewing-people-about-their-interactions-with-the-federal-government/) and what we learned. Today, we’re sharing the strategies people use when interacting with the government. Later this week, we’ll detail how people navigate government services and what we learned about people’s views on transparency._
-![screenshot of labs.usa.gov]({{site.baseurl}}/assets/blog/federal-front-door/ffd-microsite.jpg)
+{% image "assets/blog/federal-front-door/ffd-microsite.jpg" "screenshot of labs.usa.gov" %}
## Interaction strategies and attitudes toward government
diff --git a/content/posts/2016-03-03-five-questions-for-the-nasa-chief-historian.md b/content/posts/2016-03-03-five-questions-for-the-nasa-chief-historian.md
index b44260f38..669055dc1 100644
--- a/content/posts/2016-03-03-five-questions-for-the-nasa-chief-historian.md
+++ b/content/posts/2016-03-03-five-questions-for-the-nasa-chief-historian.md
@@ -17,11 +17,11 @@ NASA’s design choices — in particular, their iconic [“meatball”](http://
**Kate Garklavs**: NASA switched from “the meatball” logo, pictured here:
-![NASA's meatball logo]({{site.baseurl}}/assets/blog/nasa-historian/meatball.jpg)
+{% image "assets/blog/nasa-historian/meatball.jpg" "NASA's meatball logo" %}
to “the worm”, pictured here:
-![NASA's meatball logo]({{site.baseurl}}/assets/blog/nasa-historian/worm-logo.jpg)
+{% image "assets/blog/nasa-historian/worm-logo.jpg" "NASA's meatball logo" %}
in 1975 — how was that decision received, internally? How did the public react to this transition, and how did the public reaction reflect (or deviate from) what NASA expected?
@@ -37,7 +37,7 @@ Among those involved in the redesign, the expectation was probably that the newe
**BB:** Among those who were alive at the time (and many who have come since), the highly visible NASA insignia during the Apollo program came to be visual shorthand for everything that they imagined NASA stood for. The meatball is not only recognized in the U.S. — everywhere I've traveled in the world, people instantly recognize the meatball as meaning NASA.
-![NASA's space historian, Bill Barry]({{site.baseurl}}/assets/blog/nasa-historian/nasa-historian.jpg)
+{% image "assets/blog/nasa-historian/nasa-historian.jpg" "NASA's space historian, Bill Barry" %}
**KG:** Changing gears a bit, what’s the most interesting (and perhaps surprising) thing you’ve learned about NASA since starting as their Chief Historian in 2010?
diff --git a/content/posts/2016-03-03-how-people-learn-to-navigate-government-services.md b/content/posts/2016-03-03-how-people-learn-to-navigate-government-services.md
index cd97fef60..5ce2f06cf 100644
--- a/content/posts/2016-03-03-how-people-learn-to-navigate-government-services.md
+++ b/content/posts/2016-03-03-how-people-learn-to-navigate-government-services.md
@@ -41,7 +41,7 @@ Only one person interviewed reported that they learned about a new program by br
### Digital Literacy
-![An inforgraphic showing that people with low digital literacy depend on family and friends for help, people with medium digital literacy can perform simple tasks but get more frustrated as processes become more complex, and people with high digital literacy say their main barrier is trust.]({{site.baseurl}}/assets/blog/federal-front-door/image06.jpg)
+{% image "assets/blog/federal-front-door/image06.jpg" "An inforgraphic showing that people with low digital literacy depend on family and friends for help, people with medium digital literacy can perform simple tasks but get more frustrated as processes become more complex, and people with high digital literacy say their main barrier is trust." %}
Digital literacy exists on a spectrum.
@@ -53,7 +53,7 @@ At the low end of the spectrum are people who are unable to tell that the **www*
### Digital Access
-![An infographic showing that people with low digital access depend on public resources or a social network, whereas people with high digital access have no technical issues connecting to online services.]({{site.baseurl}}/assets/blog/federal-front-door/image04.jpg)
+{% image "assets/blog/federal-front-door/image04.jpg" "An infographic showing that people with low digital access depend on public resources or a social network, whereas people with high digital access have no technical issues connecting to online services." %}
A correlation exists between digital literacy and digital access. People who are able to afford good internet access at home and own multiple devices are also more likely to be digitally literate. These people have no technical issues connecting to online resources.
@@ -63,7 +63,7 @@ People without access to any devices or the internet are also the least likely t
### English proficiency
-![An infographic showing that people with low English proficiency depending on family and friends for help, people with medium English proficiency can use English-based sites if the language is clear and simple, and people with high English proficiency prefer English services of websites.]({{site.baseurl}}/assets/blog/federal-front-door/image05.jpg)
+{% image "assets/blog/federal-front-door/image05.jpg" "An infographic showing that people with low English proficiency depending on family and friends for help, people with medium English proficiency can use English-based sites if the language is clear and simple, and people with high English proficiency prefer English services of websites." %}
English fluency also exists on a scale, and low fluency presents its own barriers to interacting with the government. In general, bilingual speakers find that non-English translations of government sites are inaccurate or incomplete. They complained that when government sites are available in their native languages, those sites are direct translations from English, and as such are unintelligible.
diff --git a/content/posts/2016-03-04-how-people-use-proxies-to-interact-with-the-government.md b/content/posts/2016-03-04-how-people-use-proxies-to-interact-with-the-government.md
index ea629cf89..92792d2ef 100644
--- a/content/posts/2016-03-04-how-people-use-proxies-to-interact-with-the-government.md
+++ b/content/posts/2016-03-04-how-people-use-proxies-to-interact-with-the-government.md
@@ -23,7 +23,7 @@ _This is part four of a series detailing the findings of a team of researchers f
_In yesterday’s post, we [detailed how people learn to navigate government services](https://18f.gsa.gov/2016/03/03/how-people-learn-to-navigate-government-services/) and what barriers exist to access services. Today we’ll detail how people interact with the government using proxies._
-![screenshot of labs.usa.gov]({{site.baseurl}}/assets/blog/federal-front-door/ffd-microsite.jpg)
+{% image "assets/blog/federal-front-door/ffd-microsite.jpg" "screenshot of labs.usa.gov" %}
## Interacting with the government using proxies
diff --git a/content/posts/2016-03-07-the-need-for-transparency-in-government.md b/content/posts/2016-03-07-the-need-for-transparency-in-government.md
index 8d2a161b1..c251a71dc 100644
--- a/content/posts/2016-03-07-the-need-for-transparency-in-government.md
+++ b/content/posts/2016-03-07-the-need-for-transparency-in-government.md
@@ -23,17 +23,17 @@ _This is part five of a series detailing the findings of a team of researchers f
_In yesterday’s post, we [outlined how people interact with the government using proxies](https://18f.gsa.gov/2016/03/04/how-people-use-proxies-to-interact-with-the-government/). Today we’ll detail the need for transparency in government so that the public can “see” the process they’re undergoing when they’re interacting with federal agencies and programs._
-![screenshot of labs.usa.gov]({{site.baseurl}}/assets/blog/federal-front-door/ffd-microsite.jpg)
+{% image "assets/blog/federal-front-door/ffd-microsite.jpg" "screenshot of labs.usa.gov" %}
## The black box of government
-![Infographic showing ways people can become confused when interacting with government services]({{site.baseurl}}/assets/blog/federal-front-door/image09.jpg)
+{% image "assets/blog/federal-front-door/image09.jpg" "Infographic showing ways people can become confused when interacting with government services" %}
### The need for transparency: understanding a process
Members of the public want to be able to “see” the process they’re undergoing when they’re interacting with federal agencies and programs. This includes knowing when their information has been received and reviewed, understanding all steps in the process from start to finish, and having greater overall clarity into why the process takes as long as it does. People expect to wait, but the reasons why and the causes for delay continue to be a mystery — and continue to erode people’s trust in the government.
-![Infographic showing that when people call the government, they're not always told where their information is or whether it has been reviewed]({{site.baseurl}}/assets/blog/federal-front-door/image08.jpg)
+{% image "assets/blog/federal-front-door/image08.jpg" "Infographic showing that when people call the government, they're not always told where their information is or whether it has been reviewed" %}
People are more comfortable providing their personal information or undergoing difficult processes if they understand why these things are necessary. Interviewees complained of forms asking for personal or sensitive information when it didn’t seem relevant. For example, Danica R. complained about having to provide her son’s new address to HUD when he moved out before age 18. Her relationship with her son was strained, and she didn’t know where he was living at the time. She said, “I was already struggling to maintain the relationship, why do you have to make it harder?” She wondered why telling HUD that he had moved out wasn’t enough.
@@ -43,7 +43,7 @@ Generally speaking, people want insight into the process they’re preparing to
### Personal and governmental pressures
-![Infographic showing personal and governmental pressures that may be on a person when they are trying to interact with the government]({{site.baseurl}}/assets/blog/federal-front-door/image07.jpg)
+{% image "assets/blog/federal-front-door/image07.jpg" "Infographic showing personal and governmental pressures that may be on a person when they are trying to interact with the government" %}
When interacting with the federal government, a person may be under considerable pressure. One source of this pressure could be the life event that is triggering the interaction, such as the loss of a job. That said, pressure also results from the government process itself. People worry that they only get one shot to get their paperwork right and that there may be negative consequences for doing something wrong. They also worry when long periods of time pass without updates, and when interactions are difficult. Some may worry that their request might be viewed as fraudulent rather than coming from a place of real need.
diff --git a/content/posts/2016-03-08-san-diego-summit-opens-doors-to-technology-partnerships.md b/content/posts/2016-03-08-san-diego-summit-opens-doors-to-technology-partnerships.md
index f71dcf16c..42b32c43f 100644
--- a/content/posts/2016-03-08-san-diego-summit-opens-doors-to-technology-partnerships.md
+++ b/content/posts/2016-03-08-san-diego-summit-opens-doors-to-technology-partnerships.md
@@ -11,7 +11,7 @@ description: "On March 18, the U.S. General Services Administration (GSA) will c
image: /assets/blog/events/san-diego.jpg
---
-![San Diego skyline]({{site.baseurl}}/assets/blog/events/san-diego.jpg)
+{% image "assets/blog/events/san-diego.jpg" "San Diego skyline" %}
*Originally published on [GSA’s
blog](http://gsablogs.gsa.gov/gsablog/2016/03/07/san-diego-summit-opens-doors-to-technology-partnerships/)*.
diff --git a/content/posts/2016-03-08-too-many-options-make-complicated-decisions-harder.md b/content/posts/2016-03-08-too-many-options-make-complicated-decisions-harder.md
index 00cb807e8..8f8894697 100644
--- a/content/posts/2016-03-08-too-many-options-make-complicated-decisions-harder.md
+++ b/content/posts/2016-03-08-too-many-options-make-complicated-decisions-harder.md
@@ -23,7 +23,7 @@ _This is part six of a series detailing the findings of a team of researchers fr
_In yesterday’s post, we detailed [how transparency helps build public trust](https://18f.gsa.gov/2016/03/07/the-need-for-transparency-in-government/). Today we'll talk about how choice overload affects decision-making._
-![screenshot of labs.usa.gov]({{site.baseurl}}/assets/blog/federal-front-door/ffd-microsite.jpg)
+{% image "assets/blog/federal-front-door/ffd-microsite.jpg" "screenshot of labs.usa.gov" %}
## The burden of choice overload
diff --git a/content/posts/2016-03-09-trust-as-a-two-way-street.md b/content/posts/2016-03-09-trust-as-a-two-way-street.md
index 608e110e9..9a99ae1e1 100644
--- a/content/posts/2016-03-09-trust-as-a-two-way-street.md
+++ b/content/posts/2016-03-09-trust-as-a-two-way-street.md
@@ -23,7 +23,7 @@ _This is part seven of a series detailing the findings of a team of researchers
_In yesterday’s post, we [talked about choice overload affecting decision-making.](https://18f.gsa.gov/2016/03/08/too-many-options-make-complicated-decisions-harder/). Today we'll detail when people decide to trust the federal government and how they view the federal government vs. private companies._
-![screenshot of labs.usa.gov]({{site.baseurl}}/assets/blog/federal-front-door/ffd-microsite.jpg)
+{% image "assets/blog/federal-front-door/ffd-microsite.jpg" "screenshot of labs.usa.gov" %}
## Trust is reciprocal
diff --git a/content/posts/2016-03-10-what-people-think-about-before-sharing-personal-information.md b/content/posts/2016-03-10-what-people-think-about-before-sharing-personal-information.md
index 77c38dfee..8c541f454 100644
--- a/content/posts/2016-03-10-what-people-think-about-before-sharing-personal-information.md
+++ b/content/posts/2016-03-10-what-people-think-about-before-sharing-personal-information.md
@@ -23,11 +23,11 @@ _This is part eight of a series detailing the findings of a team of researchers
_In yesterday’s post, we [detailed when people decide to trust the federal government](https://18f.gsa.gov/2016/03/09/trust-as-a-two-way-street/). Today we'll share what people think about before deciding to share personal information with the government._
-![screenshot of labs.usa.gov]({{site.baseurl}}/assets/blog/federal-front-door/ffd-microsite.jpg)
+{% image "assets/blog/federal-front-door/ffd-microsite.jpg" "screenshot of labs.usa.gov" %}
## Sharing personal information
-![A graphic showing how people might view sharing information. Some never want their information shared, and others are on a continuum.]({{site.baseurl}}/assets/blog/federal-front-door/image03.jpg)
+{% image "assets/blog/federal-front-door/image03.jpg" "A graphic showing how people might view sharing information. Some never want their information shared, and others are on a continuum." %}
### The desire for privacy exists on a spectrum
@@ -43,7 +43,7 @@ Others want to avoid providing their information to the government as much as po
Although many people accept that they need to share information — sometimes very personal information — with the government, their acceptance shouldn’t be mistaken for eagerness. Most people would prefer forms collect less information and do so more judiciously.
-![An infographic illustrating that people expect personal information like medical records, family information, and financial records to be safe from ID thieves, advertisers and third parties.]({{site.baseurl}}/assets/blog/federal-front-door/image00.jpg)
+{% image "assets/blog/federal-front-door/image00.jpg" "An infographic illustrating that people expect personal information like medical records, family information, and financial records to be safe from ID thieves, advertisers and third parties." %}
### Information sharing between agencies
diff --git a/content/posts/2016-03-11-designing-services-that-are-accessible-transparent-and-easy-to-use.md b/content/posts/2016-03-11-designing-services-that-are-accessible-transparent-and-easy-to-use.md
index f768881a5..3f8cf562d 100644
--- a/content/posts/2016-03-11-designing-services-that-are-accessible-transparent-and-easy-to-use.md
+++ b/content/posts/2016-03-11-designing-services-that-are-accessible-transparent-and-easy-to-use.md
@@ -23,7 +23,7 @@ _This is the final installment of a series detailing the findings of a team of r
_Yesterday, we shared [what people think about before deciding to share personal information with the government](https://18f.gsa.gov/2016/03/10/what-people-think-about-before-sharing-personal-information/). Today we end our series with a look at what we’ll focus on in the next stage of research._
-![screenshot of labs.usa.gov]({{site.baseurl}}/assets/blog/federal-front-door/ffd-microsite.jpg)
+{% image "assets/blog/federal-front-door/ffd-microsite.jpg" "screenshot of labs.usa.gov" %}
## What's next?
diff --git a/content/posts/2016-03-15-treasury-and-the-data-act-full-of-sunshine.md b/content/posts/2016-03-15-treasury-and-the-data-act-full-of-sunshine.md
index 441d7eade..557e1a416 100644
--- a/content/posts/2016-03-15-treasury-and-the-data-act-full-of-sunshine.md
+++ b/content/posts/2016-03-15-treasury-and-the-data-act-full-of-sunshine.md
@@ -37,7 +37,7 @@ getting feedback, and incorporating it into subsequent versions. DATA
Act is the [first government-wide agile
project](http://fedspendingtransparency.github.io/act-ivity/2016/02/29/first-government-wide-agile-project/).
-![Representatives from the Department of Education, the Department of the Interior, the Department of the Treasury, and the Pension Benefit Guaranty Corporation gather for a sandbox testing session.]({{site.baseurl}}/assets/blog/data-act-implementation/data-act-meeting.jpg)
+{% image "assets/blog/data-act-implementation/data-act-meeting.jpg" "Representatives from the Department of Education, the Department of the Interior, the Department of the Treasury, and the Pension Benefit Guaranty Corporation gather for a sandbox testing session." %}
*Representatives from the Department of Education, the Department of the Interior, the Department of the Treasury, and the Pension Benefit Guaranty Corporation gather for a sandbox testing session.*
## The DATA Act schema
diff --git a/content/posts/2016-03-16-making-the-draft-web-design-standards-better-through-feedback.md b/content/posts/2016-03-16-making-the-draft-web-design-standards-better-through-feedback.md
index 66dd3441e..8e9d70117 100644
--- a/content/posts/2016-03-16-making-the-draft-web-design-standards-better-through-feedback.md
+++ b/content/posts/2016-03-16-making-the-draft-web-design-standards-better-through-feedback.md
@@ -13,7 +13,7 @@ excerpt: "Since our launch of the Draft U.S. Web Design Standards last September
description: "Since our launch of the Draft U.S. Web Design Standards last September, hundreds of people have provided feedback on the project through GitHub issues and via email. In addition, user research done by the Federal Front Door team has produced some interesting finding for the team."
image: /assets/blog/web-design-standards/home.png
---
-![The Draft U.S. Web Design Standards homepage on multiple devices]({{site.baseurl}}/assets/blog/web-design-standards/home.png)
+{% image "assets/blog/web-design-standards/home.png" "The Draft U.S. Web Design Standards homepage on multiple devices" %}
Since [our
launch](https://18f.gsa.gov/2015/09/28/web-design-standards/) of the
diff --git a/content/posts/2016-03-18-how-user-archetypes-informed-the-draft-us-web-design-standards.md b/content/posts/2016-03-18-how-user-archetypes-informed-the-draft-us-web-design-standards.md
index b619cd171..9383db519 100644
--- a/content/posts/2016-03-18-how-user-archetypes-informed-the-draft-us-web-design-standards.md
+++ b/content/posts/2016-03-18-how-user-archetypes-informed-the-draft-us-web-design-standards.md
@@ -23,7 +23,7 @@ For the first phase of our research, we decided to focus on this group and give
Jumping off from an idea suggested by Julia Elman (the project lead on the 18F side), Colin MacArthur and I created a series of user archetypes inspired by [this article on the TED blog](http://hello.ted.com/2013/10/08/whats-your-ted-habit/). User archetypes presented a way of concisely describing the behaviors and needs of the people who would be using the standards. We based our initial archetypes on preliminary discussions and user interviews, recognizing that they’d evolve during the course of the project and as we got more research under our belts. With that in mind, we kept the descriptions loose and the images sketchy to indicate the “work in progress” status that we intended. Following some quick interviews and brainstorming sessions, we came up with the following archetypes.
-
+{% image_with_class "assets/blog/web-design-standards/vision-provider.jpg" "width-400px" "Stick figure zapping two Pantone chips." %}
### The Vision Provider
@@ -39,7 +39,7 @@ They want a cohesive resource they can point their team and contractors to so th
They may face challenges convincing less experienced folks on their team on why the Draft Standards are important, or they may themselves not want to override the brand identity for their agency that has already been developed. They wonder how much they can customize the Draft Standards before they defeat the purpose of a unified user experience.
-
+{% image_with_class "assets/blog/web-design-standards/newbie.jpg" "width-400px" "Stick figure of a person with an I heart gov shirt and a coffee cup." %}
### The Newbie
@@ -53,7 +53,7 @@ They’re excited to prove their mettle, but they may not be experienced enough
They don’t fully understand the need for design standards. They may resist using design standards because they don’t want their creativity to be stifled.
-
+{% image_with_class "assets/blog/web-design-standards/lone-ranger.jpg" "width-200px" "Stick figure of a cowboy." %}
### The Lone Ranger
@@ -69,7 +69,7 @@ They will use the Draft Standards to cut down on design and development time, an
The Lone Ranger wants to be able to get started with the Draft Standards quickly and not have to fuss with a lot of compatibility issues. They worry about tying their projects to a resource without knowing whether or not it will be maintained.
-
+{% image_with_class "assets/blog/web-design-standards/master-builder.jpg" "width-200px" "Stick figure wearing a hard hat." %}
### The Master Builder
@@ -83,7 +83,7 @@ They see their code as their personal craft and value clean, semantic markup tha
The Master Builder doesn’t want to have to do mindless “grunt work” such as styling tables or making form fields accessible, and would rather focus their attention on more creative problem solving.
-
+{% image_with_class "assets/blog/web-design-standards/reviewer.jpg" "width-400px" "Stick figure looking at a website with a magnifying glass." %}
### The Reviewer
@@ -95,7 +95,7 @@ The Reviewer is charged with inspecting other teammates’ code or designs and m
The reviewer wants to point to the Draft Standards to help these folks implement good front end code, reducing the amount of emergency clean-up they have to deal with. They may refer to the Draft Standards documentation when reviewing code.
-
+{% image_with_class "assets/blog/web-design-standards/decider.jpg" "width-400px" "Stick figure holding onto a yes/no switch." %}
### The Decider
@@ -107,7 +107,7 @@ The decider chooses whether or not to use the Draft Standards on a project. They
They will ask questions about how the Draft Standards will be maintained and how they will integrate with existing technology stacks and work-flows.
-
+{% image_with_class "assets/blog/web-design-standards/macgyver.jpg" "width-400px" "A monitor duct taped together." %}
### The MacGyver
@@ -119,7 +119,7 @@ The MacGyver is a back end developer who has been charged with front end design
They would like a resource with downloadable templates and components so they stand up sites quickly can get back to what they love — arguing data schematics.
-
+{% image_with_class "assets/blog/web-design-standards/pinch-hitter.jpg" "width-200px" "Stick figure with a baseball bat." %}
### The Pinch Hitter
@@ -133,7 +133,7 @@ They rely on the pattern library components to work out of the box, and they nee
They are concerned about conflicts with existing frameworks because these are difficult to resolve with their limited development experience.
-
+{% image_with_class "assets/blog/web-design-standards/influencer.jpg" "width-400px" "Stick figure posing next to a monitor that says new and shiny." %}
### The Influencer
@@ -141,7 +141,7 @@ They are concerned about conflicts with existing frameworks because these are di
The Influencer likes the idea of creating a consistent user experience across government websites and wants to empower government employees to work toward this goal. They play a key role in advocating for adoption of the standards, and they want the site itself to offer language and resources to help them out.
-
+{% image_with_class "assets/blog/web-design-standards/contract-manager.jpg" "width-400px" "Blind-folded stick finger pointing at three numbered doors." %}
### The Contract Manager
@@ -153,7 +153,7 @@ The Contract Manager is in charge of managing work for — you guessed it — go
They want their projects to benefit from quality design and front end development work, but do not necessarily know what it looks like or how to enforce it. They want to be able to specify that contractors follow web design standards with specific legalese.
-
+{% image_with_class "assets/blog/web-design-standards/clock-racer.jpg" "width-400px" "Stick figure coding with clocks in the background." %}
### The Clock Racer
diff --git a/content/posts/2016-03-22-helping-california-buy-a-new-child-welfare-system.md b/content/posts/2016-03-22-helping-california-buy-a-new-child-welfare-system.md
index bbbda68ea..7af340b32 100644
--- a/content/posts/2016-03-22-helping-california-buy-a-new-child-welfare-system.md
+++ b/content/posts/2016-03-22-helping-california-buy-a-new-child-welfare-system.md
@@ -39,7 +39,7 @@ results that users of the system actually need. We offer our partners
[a different
approach](https://18f.gsa.gov/2015/03/30/new-rfp-ghostwriting-service-to-improve-contract-success/).
-![The team from the State of California, Code for America, and 18F at the end of day two of the workshop.]({{site.baseurl}}/assets/blog/ca-child-welfare/ca-team.jpg)
+{% image "assets/blog/ca-child-welfare/ca-team.jpg" "The team from the State of California, Code for America, and 18F at the end of day two of the workshop." %}
*The team from the State of California, Code for America, and 18F at the end of day two of the workshop.*
Through a partnership with HHS, 18F was able to work on behalf of HHS with California’s Department of Social Services and Office of Systems Integration and Code for America to simplify the contracting documents and to incorporate
diff --git a/content/posts/2016-03-24-video-highlights-from-18f-speeches-over-the-last-year.md b/content/posts/2016-03-24-video-highlights-from-18f-speeches-over-the-last-year.md
index 0af3e4546..1d74570ca 100644
--- a/content/posts/2016-03-24-video-highlights-from-18f-speeches-over-the-last-year.md
+++ b/content/posts/2016-03-24-video-highlights-from-18f-speeches-over-the-last-year.md
@@ -20,7 +20,7 @@ team."
image: /assets/blog/anniversary/speaking-locations-map-fy15-16.jpg
---
-![A map of where 18F staffers spoke about our work in 2015 and 2016.]({{site.baseurl}}/assets/blog/anniversary/speaking-locations-map-fy15-16.jpg)
+{% image "assets/blog/anniversary/speaking-locations-map-fy15-16.jpg" "A map of where 18F staffers spoke about our work in 2015 and 2016." %}
*A map of where 18F staffers spoke about our work in 2015 and 2016. This
map only records one dot per city, so multiple events only appear as a
single dot.*
diff --git a/content/posts/2016-03-28-interesting-things-we-learned-from-examining-traffic-patterns-on-analytics-usa-gov.md b/content/posts/2016-03-28-interesting-things-we-learned-from-examining-traffic-patterns-on-analytics-usa-gov.md
index 94d3bbb68..2a25848c6 100644
--- a/content/posts/2016-03-28-interesting-things-we-learned-from-examining-traffic-patterns-on-analytics-usa-gov.md
+++ b/content/posts/2016-03-28-interesting-things-we-learned-from-examining-traffic-patterns-on-analytics-usa-gov.md
@@ -11,7 +11,7 @@ description: "Ten federal agencies now have public dashboards and datasets for t
image: /assets/blog/dap/epa-analytics.jpg
---
-[![A screenshot of the Environmental Protection Agency's dashboard on analytics.usa.gov]({{site.baseurl}}/assets/blog/dap/epa-analytics.jpg)](https://analytics.usa.gov/environmental-protection-agency/)
+[{% image "assets/blog/dap/epa-analytics.jpg" "A screenshot of the Environmental Protection Agency's dashboard on analytics.usa.gov" %}](https://analytics.usa.gov/environmental-protection-agency/)
Ten federal agencies [now have public dashboards and datasets](https://18f.gsa.gov/2016/02/18/analytics.usa.gov-agency-specific-dashboards/) for their web traffic on analytics.usa.gov. The dashboards show insights into how the public interacts with specific agency websites.
diff --git a/content/posts/2016-03-29-best-practices-for-building-an-accessible-website-using-the-draft-us-web-design-standards.md b/content/posts/2016-03-29-best-practices-for-building-an-accessible-website-using-the-draft-us-web-design-standards.md
index 688f76344..3384c8a29 100644
--- a/content/posts/2016-03-29-best-practices-for-building-an-accessible-website-using-the-draft-us-web-design-standards.md
+++ b/content/posts/2016-03-29-best-practices-for-building-an-accessible-website-using-the-draft-us-web-design-standards.md
@@ -113,7 +113,7 @@ Checker](http://webaim.org/resources/contrastchecker/))
to test foreground and background options and adjust their lightness and
darkness until they pass contrast requirements.
-![Neutral text on a variety of color backgrounds.]({{site.baseurl}}/assets/blog/web-design-standards/color-palette.jpg)
+{% image "assets/blog/web-design-standards/color-palette.jpg" "Neutral text on a variety of color backgrounds." %}
By implementing these practices and leveraging the Draft Standards, we
hope to help create guidelines that will set you on the path to creating
diff --git a/content/posts/2016-03-30-how-we-shared-a-visual-style-across-multiple-sites.md b/content/posts/2016-03-30-how-we-shared-a-visual-style-across-multiple-sites.md
index 23f67a5df..1056b7349 100644
--- a/content/posts/2016-03-30-how-we-shared-a-visual-style-across-multiple-sites.md
+++ b/content/posts/2016-03-30-how-we-shared-a-visual-style-across-multiple-sites.md
@@ -14,7 +14,7 @@ image: /assets/blog/cloud-gov/style-guide.jpg
In developing a redesign for cloud.gov, our team found we had multiple sites with separate codebases, sometimes written in different programming languages with different frameworks that all had a shared visual style. When figuring out a technical solution to coding the visual style that was mocked up for us, we needed a solution that would scale to all these different sites without requiring us to copy code. Our solution to this problem is our “shared style library”, a library of CSS, JavaScript, images, and fonts that can be distributed to multiple codebases to create a shared visual style. Our style library includes a build process to package and optimize all the assets, versioning to ensure consumer sites receive the correct features of the style library, and a distribution method that allows multiple types of sites in different frameworks to consume the library. The library is called "cloudgov-style", or "cg-style" and is available [on GitHub](https://github.com/18F/cg-style) and [npm](https://www.npmjs.com/package/cloudgov-style).
-[![A screenshot of the cloud.gov style library]({{site.baseurl}}/assets/blog/cloud-gov/style-guide.jpg)](https://pages.18f.gov/cg-style/)
+[{% image "assets/blog/cloud-gov/style-guide.jpg" "A screenshot of the cloud.gov style library" %}](https://pages.18f.gov/cg-style/)
## Design
The idea of cloudgov-style started with a redesign of cloud.gov itself, which included a styleguide, mockups for the [main cloud.gov landing page](https://cloud.gov), and the [cloud.gov docs site](https://docs.cloud.gov). The visual style was designed using the [Draft U.S. Web Design Standards](https://playbook.cio.gov/designstandards/) as it was a good starting point to ensure the design incorporated the same values as other government sites. Plus, starting with existing code made creating our visual style much faster.
@@ -165,7 +165,7 @@ Having these different options allows different consumer sites with different bu
## Style guide
Another feature of cloudgov-style is a minimal, coded, style guide to allow for visual regression testing of new code and for developers to see what components are available and how to implement them. This style guide is created with a simple Jekyll site in the [cloudgov-style repo](https://github.com/18F/cg-style/tree/master/documentation). The style guide has each component displayed in an example use case along with a code sample to show implementation.
-[![An example of components being displayed next to their code on the cloudgov-style site.]({{site.baseurl}}/assets/blog/cloud-gov/style-guide-components.jpg)](https://pages.18f.gov/cg-style/)
+[{% image "assets/blog/cloud-gov/style-guide-components.jpg" "An example of components being displayed next to their code on the cloudgov-style site." %}](https://pages.18f.gov/cg-style/)
While all the components are displayed on the homepage, each component also has an individual page where it's displayed in isolation. This is done to create a "clean" environment for visual regression testing. By placing each component on it's own page, there won't be any false negatives in visual regression testing when there are layout changes to the components. We decided to use a hand-coded style guide built on Jekyll rather than using a tool like [KSS](http://warpspire.com/kss/) to make it easier to place each component on it’s own page.
diff --git a/content/posts/2016-03-31-new-guide-provides-tools-for-product-leads.md b/content/posts/2016-03-31-new-guide-provides-tools-for-product-leads.md
index e0785fa1f..cfe1a2faf 100644
--- a/content/posts/2016-03-31-new-guide-provides-tools-for-product-leads.md
+++ b/content/posts/2016-03-31-new-guide-provides-tools-for-product-leads.md
@@ -12,7 +12,7 @@ description: "To help our product managers, newcomers and veterans alike, wear t
image: /assets/blog/product-guide/product-guide.jpg
---
-[![A screenshot of the 18F Product Guide]({{site.baseurl}}/assets/blog/product-guide/product-guide.jpg)](https://pages.18f.gov/product-guide)
+[{% image "assets/blog/product-guide/product-guide.jpg" "A screenshot of the 18F Product Guide" %}](https://pages.18f.gov/product-guide)
*The 18F Product Guide*
A product lead can wear many hats over the course of a project. Being a
diff --git a/content/posts/2016-04-04-national-earthquake-information-centers-open-source-team.md b/content/posts/2016-04-04-national-earthquake-information-centers-open-source-team.md
index 1d6bdf1b9..601e03513 100644
--- a/content/posts/2016-04-04-national-earthquake-information-centers-open-source-team.md
+++ b/content/posts/2016-04-04-national-earthquake-information-centers-open-source-team.md
@@ -10,7 +10,7 @@ description: The National Earthquake Information Center’s web team is committe
excerpt: I visited the Earthquakes team at their office on the Colorado School of Mines campus in Golden, CO, to learn about this open source team’s role in public service.
---
-![A mountain and some buildings as seen from National Earthquake Information Center’s office on the Colorado School of Mines campus in Golden, CO.]({{site.baseurl}}/assets/blog/earthquake-center/earthquakecenter.jpg)
+{% image "assets/blog/earthquake-center/earthquakecenter.jpg" "A mountain and some buildings as seen from National Earthquake Information Center’s office on the Colorado School of Mines campus in Golden, CO." %}
*The view from the National Earthquake Information Center’s office on the Colorado School of Mines campus in Golden, CO.*
On January 28, 2016 people living at the Jersey Shore felt a shake. New
diff --git a/content/posts/2016-04-05-three-teams-using-the-draft-us-web-design-standards-talk-about-their-experiences.md b/content/posts/2016-04-05-three-teams-using-the-draft-us-web-design-standards-talk-about-their-experiences.md
index 3f4155ab8..335f7e7c4 100644
--- a/content/posts/2016-04-05-three-teams-using-the-draft-us-web-design-standards-talk-about-their-experiences.md
+++ b/content/posts/2016-04-05-three-teams-using-the-draft-us-web-design-standards-talk-about-their-experiences.md
@@ -41,7 +41,7 @@ incredibly useful and something that is needed across government
websites. The USAGov team then started connecting with the core team of
developers and designers to get this effort kicked off.
-![A USA.gov form that uses the Draft U.S. Web Design Standards]({{site.baseurl}}/assets/blog/web-design-standards/cfpb-form.jpg)
+{% image "assets/blog/web-design-standards/cfpb-form.jpg" "A USA.gov form that uses the Draft U.S. Web Design Standards" %}
[USA.gov](https://www.usa.gov/) has adopted the Draft Standards with
some of the forms that are used by our users and agency partners to
@@ -68,7 +68,7 @@ We are currently mapping components from the USAGov platform with the
ones included into the draft release of the Standards and will continue
to incorporate them in the future.
-[![The vote.usa.gov homepage]({{site.baseurl}}/assets/blog/vote-usa-gov/vote.jpg)](http://vote.usa.gov/)
+[{% image "assets/blog/vote-usa-gov/vote.jpg" "The vote.usa.gov homepage" %}](http://vote.usa.gov/)
**LK:** Our team was very excited about the branding and dropdown
components featured in the Standards. Because of the short runway to
diff --git a/content/posts/2016-04-08-making-more-consistent-decisions-with-design-principles-a-new-18f-guide.md b/content/posts/2016-04-08-making-more-consistent-decisions-with-design-principles-a-new-18f-guide.md
index 932861909..4e845de96 100644
--- a/content/posts/2016-04-08-making-more-consistent-decisions-with-design-principles-a-new-18f-guide.md
+++ b/content/posts/2016-04-08-making-more-consistent-decisions-with-design-principles-a-new-18f-guide.md
@@ -48,7 +48,7 @@ principles themselves. The team should have the freedom to experiment
and push the boundaries without breaking the spirit of the design
principles.
-[![A screenshot of the 18F Design Principles Guide]({{site.baseurl}}/assets/blog/design/design-principles-guide.jpg)
+[{% image "assets/blog/design/design-principles-guide.jpg" "A screenshot of the 18F Design Principles Guide" %}
](https://pages.18f.gov/design-principles-guide/create)
Check out the [Design Principles
diff --git a/content/posts/2016-04-12-7-18f-projects-that-state-and-local-governments-can-reuse.md b/content/posts/2016-04-12-7-18f-projects-that-state-and-local-governments-can-reuse.md
index 7a4fdc120..1a235cec6 100644
--- a/content/posts/2016-04-12-7-18f-projects-that-state-and-local-governments-can-reuse.md
+++ b/content/posts/2016-04-12-7-18f-projects-that-state-and-local-governments-can-reuse.md
@@ -22,7 +22,7 @@ highlighting seven below:
Public website analytics
----------------------------------------------
-[![A screen shot of the City of Boulder's analytics dashboard]({{site.baseurl}}/assets/blog/reusable-tools/analytics.jpg)](https://bouldercolorado.gov/stats)
+[{% image "assets/blog/reusable-tools/analytics.jpg" "A screen shot of the City of Boulder's analytics dashboard" %}](https://bouldercolorado.gov/stats)
We worked with the [Digital Analytics
Program](https://www.digitalgov.gov/services/dap/), the [U.S. Digital
@@ -44,7 +44,7 @@ for their own use.
Quick mini-sites for content
--------------------------------------------------
-[![A screen shot of an 18F guide on the pages platform]({{site.baseurl}}/assets/blog/reusable-tools/pages.jpg)](https://pages.18f.gov/agile/)
+[{% image "assets/blog/reusable-tools/pages.jpg" "A screen shot of an 18F guide on the pages platform" %}](https://pages.18f.gov/agile/)
We built a responsive, accessible [website
template](https://pages.18f.gov/) (based on open source work by the
@@ -63,7 +63,7 @@ domain.
Insight into how people interact with government
----------------------------------------------------------------------
-[![People depend on others (for example, family members, friends, and public library staff) for help with government websites, but government services are not set up to support this type of assistance.]({{site.baseurl}}/assets/blog/reusable-tools/depend.jpg)](https://labs.usa.gov/files/FFD_ResearchReport.pdf)
+[{% image "assets/blog/reusable-tools/depend.jpg" "People depend on others (for example, family members, friends, and public library staff) for help with government websites, but government services are not set up to support this type of assistance." %}](https://labs.usa.gov/files/FFD_ResearchReport.pdf)
Over the last several months, staff from General Service
Administration’s USAGov and 18F teams have been talking to Americans
@@ -78,7 +78,7 @@ learned](https://18f.gsa.gov/tags/federal-front-door/) on the 18F blog.
Market research for procurement
-----------------------------------------------------
-[![An animated demo of how to use the CALC tool]({{site.baseurl}}/assets/blog/calc-announcement/calc_demo.gif)](https://calc.gsa.gov/)
+[{% image "assets/blog/calc-announcement/calc_demo.gif" "An animated demo of how to use the CALC tool" %}](https://calc.gsa.gov/)
We developed [a tool](https://calc.gsa.gov/) that helps you easily
conduct market research across a number of categories for acquiring
@@ -90,7 +90,7 @@ conduct market research.
Vocabulary for user-centered design
---------------------------------------------------------
-[![Some of our Design Method Cards]({{site.baseurl}}/assets/blog/reusable-tools/method-cards.jpg)](https://methods.18f.gov/)
+[{% image "assets/blog/reusable-tools/method-cards.jpg" "Some of our Design Method Cards" %}](https://methods.18f.gov/)
We [released](https://18f.gsa.gov/2015/08/10/18f-design-methods/) a
[deck of method cards](https://methods.18f.gov/) that help research
@@ -100,7 +100,7 @@ agencies.
Task management
---------------
-[![A screenshot of our Checklistomania tool showing two sample tasks]({{site.baseurl}}/assets/blog/reusable-tools/checklistomania.jpg)](https://github.com/18F/checklistomania)
+[{% image "assets/blog/reusable-tools/checklistomania.jpg" "A screenshot of our Checklistomania tool showing two sample tasks" %}](https://github.com/18F/checklistomania)
We recently developed a [checklist
program](https://github.com/18F/checklistomania) that help users manage
@@ -113,7 +113,7 @@ task four is completed by an employee.
Help small businesses find opportunities
-----------------------------------------
-[![The FBopen homepage]({{site.baseurl}}/assets/blog/reusable-tools/fbopen.jpg)](https://fbopen.gsa.gov/)
+[{% image "assets/blog/reusable-tools/fbopen.jpg" "The FBopen homepage" %}](https://fbopen.gsa.gov/)
[FBOpen](https://fbopen.gsa.gov/) is a set of open source tools to
help small businesses search for opportunities to work with the U.S.
diff --git a/content/posts/2016-04-19-looking-at-the-different-ways-to-test-content.md b/content/posts/2016-04-19-looking-at-the-different-ways-to-test-content.md
index a11989884..ad433c469 100644
--- a/content/posts/2016-04-19-looking-at-the-different-ways-to-test-content.md
+++ b/content/posts/2016-04-19-looking-at-the-different-ways-to-test-content.md
@@ -37,7 +37,7 @@ depending on the age of your audience. Finding appropriate ways to test
our content helps us improve and find best practice patterns for
creating copy.
-![A graph with comprehension and confusion at the top and bottom of the y-axis and failure and success on the left and right of the x axis. The desired spot for content is in the upper right quadrant between comprehension and success. ]({{site.baseurl}}/assets/blog/content-testing/content-graph.jpg)
+{% image "assets/blog/content-testing/content-graph.jpg" "A graph with comprehension and confusion at the top and bottom of the y-axis and failure and success on the left and right of the x axis. The desired spot for content is in the upper right quadrant between comprehension and success. " %}
*Christine’s graph of good content. The star marks
the sweet spot.*
@@ -78,7 +78,7 @@ Kid in a Park project to keep pressure low and still measure how well
kids understood the website. For example, one question we asked was,
“How would you use this website to sign up for Every Kid in a Park?”
-[![A screenshot of the Every Kid in a Park homepage]({{site.baseurl}}/assets/blog/every-kid-in-a-park/every-kid-in-a-park-homepage.jpg)](https://www.everykidinapark.gov)
+[{% image "assets/blog/every-kid-in-a-park/every-kid-in-a-park-homepage.jpg" "A screenshot of the Every Kid in a Park homepage" %}](https://www.everykidinapark.gov)
*The Every Kid in a Park homepage reads at a 4.5 grade level and was
tested with kids through the University of Maryland’s HCI lab.*
@@ -101,7 +101,7 @@ experienced in the previous two weeks. The feelings listed by users in
testing were matched to the ones already in the app — plus the feelings
people had written into the “add your own” field.
-![A grid of possible words such as OK, anxious, angry, and happy under the heading "How you feel right now"]({{site.baseurl}}/assets/blog/content-testing/choose-words.jpg)
+{% image "assets/blog/content-testing/choose-words.jpg" "A grid of possible words such as OK, anxious, angry, and happy under the heading "How you feel right now"" %}
The goal was to test whether the feelings chosen for the app were
representative and appropriate.
@@ -129,7 +129,7 @@ asking users to sign up as organ donors. For example:
The sign-up rate for each piece of content was measured and the most
successful was:
-![A screenshot of the GOV.UK screen with "Please join the NHS Organ Donor Register" on a thank you page.]({{site.baseurl}}/assets/blog/content-testing/ab-test.jpg))
+{% image "assets/blog/content-testing/ab-test.jpg" "A screenshot of the GOV.UK screen with "Please join the NHS Organ Donor Register" on a thank you page." %})
Each content variant the NHS tested used plain language and could be
easily understood. The A/B test showed which call to action was *most
@@ -160,7 +160,7 @@ she accepted synonyms as answers. She was hoping to get test scores of
50 percent or greater accuracy; in practice, FEC’s Cloze test scores ranged
from 65 percent to 98 percent, even better than she hoped.
-![An example of a page from beta.fec.gov that used a Close test.]({{site.baseurl}}/assets/blog/content-testing/cloze-testing.jpg)
+{% image "assets/blog/content-testing/cloze-testing.jpg" "An example of a page from beta.fec.gov that used a Close test." %}
*This page from [beta.FEC.gov](https://beta.fec.gov) is one of several tested using a Cloze
test.*
diff --git a/content/posts/2016-04-20-a-clear-audience-makes-for-a-good-blog-post.md b/content/posts/2016-04-20-a-clear-audience-makes-for-a-good-blog-post.md
index 715b1ceff..144babb7c 100644
--- a/content/posts/2016-04-20-a-clear-audience-makes-for-a-good-blog-post.md
+++ b/content/posts/2016-04-20-a-clear-audience-makes-for-a-good-blog-post.md
@@ -25,7 +25,7 @@ and exit as a closed issue in the “approved” milestone after they’ve
been edited by a member of our blog team and sent through our approval
process.
-![An example of an issue for a blog post.]({{site.baseurl}}/assets/blog/blogging-guide/blogging-metadata.jpg)
+{% image "assets/blog/blogging-guide/blogging-metadata.jpg" "An example of an issue for a blog post." %}
*An example of an issue for a blog post.*
Each issue has five metadata headings, including audience, that the
diff --git a/content/posts/2016-04-21-checklistomania-makes-it-easy-to-keep-track-of-relative-tasks.md b/content/posts/2016-04-21-checklistomania-makes-it-easy-to-keep-track-of-relative-tasks.md
index ee5a0f63e..8d2ed60e1 100644
--- a/content/posts/2016-04-21-checklistomania-makes-it-easy-to-keep-track-of-relative-tasks.md
+++ b/content/posts/2016-04-21-checklistomania-makes-it-easy-to-keep-track-of-relative-tasks.md
@@ -22,7 +22,7 @@ you have to sign into your work email before you can set up two-factor
authentication or view your first paycheck. Keeping track of these tasks
and how they relate to each other is difficult and time consuming.
-![Screenshot of the tasks screen in Checklistomania]({{site.baseurl}}/assets/blog/checklistomania/tasks.jpg)
+{% image "assets/blog/checklistomania/tasks.jpg" "Screenshot of the tasks screen in Checklistomania" %}
Enter [Checklistomania](https://github.com/18F/checklistomania). We
developed the tool at 18F specifically for onboarding. It’s used by new
@@ -33,13 +33,13 @@ features:
- The checklists are centrally defined, so any member of an organization can subscribe to the authoritative checklist.
-![Screenshot of various checklists you can sign up for]({{site.baseurl}}/assets/blog/checklistomania/users.jpg)
+{% image "assets/blog/checklistomania/users.jpg" "Screenshot of various checklists you can sign up for" %}
- Deadlines can be set according to a fixed date or relative to completion of other items. For example, if Task B must be completed three days after Task A (but only after Task A has been completed), the due date will shift accordingly.
- We can view each other’s checklists, which makes it easy to see everyone's status at a glance.
-![Screenshot of the users screen in Checklistomania]({{site.baseurl}}/assets/blog/checklistomania/users.jpg)
+{% image "assets/blog/checklistomania/users.jpg" "Screenshot of the users screen in Checklistomania" %}
[Checklistomania](https://github.com/18F/checklistomania) is an open
source project in the public domain and may be adapted by any
diff --git a/content/posts/2016-04-25-lean-on-me-asking-for-help-on-the-content-team.md b/content/posts/2016-04-25-lean-on-me-asking-for-help-on-the-content-team.md
index 91b1bd7a6..87fb73216 100644
--- a/content/posts/2016-04-25-lean-on-me-asking-for-help-on-the-content-team.md
+++ b/content/posts/2016-04-25-lean-on-me-asking-for-help-on-the-content-team.md
@@ -16,7 +16,7 @@ skills — we put this to good use by regularly asking each other for help
with projects. Here’s a diagrammatic look into some of our recent
collaboration.*
-![A circle of head shots of the Content Team with lines connecting them]({{site.baseurl}}/assets/blog/content/collaborate-content.jpg)
+{% image "assets/blog/content/collaborate-content.jpg" "A circle of head shots of the Content Team with lines connecting them" %}
[Emileigh](https://18f.gsa.gov/team/emileigh/)
------------------------------------------------
diff --git a/content/posts/2016-04-26-thinking-about-the-future-of-the-post-office-an-interview-with-amanda-weaver.md b/content/posts/2016-04-26-thinking-about-the-future-of-the-post-office-an-interview-with-amanda-weaver.md
index 33744f5af..549bc1bfa 100644
--- a/content/posts/2016-04-26-thinking-about-the-future-of-the-post-office-an-interview-with-amanda-weaver.md
+++ b/content/posts/2016-04-26-thinking-about-the-future-of-the-post-office-an-interview-with-amanda-weaver.md
@@ -26,7 +26,7 @@ I’m going to list some of our current projects and things we’re thinking abo
First, we’re trying to [understand their revealed preferences](https://www.uspsoig.gov/sites/default/files/document-library-files/2015/rarc-wp-15-012.pdf) using the latest scientific techniques from neuroscience. Second, we’re focused on innovations within the mail itself. How can we use the latest technology to make the physical mail piece more digitally interactive and thus more appealing to the digital natives?
-[![A map of potential pieces of the internet of postal things]({{site.baseurl}}/assets/blog/partners-in-government/internet-of-postal-things.jpg)](https://www.uspsoig.gov/document/internet-postal-things)
+[{% image "assets/blog/partners-in-government/internet-of-postal-things.jpg" "A map of potential pieces of the internet of postal things" %}](https://www.uspsoig.gov/document/internet-postal-things)
*A page from the [report on the Internet of Postal Things](https://www.uspsoig.gov/document/internet-postal-things)*
**The Internet of Postal Things.** We’re imagining [how the rich infrastructure of the Postal Service could be used](https://www.uspsoig.gov/document/internet-postal-things) if it were outfitted with sensors and interconnected with each other as well as the internet. This would create useful information to make the postal system smarter, and allow it to collect really useful information to the localities as a byproduct — think about sensors that could measure road conditions, the strength of mobile signals, or monitor air quality. We are currently expanding on this concept in another paper to explain how the Internet of Postal Things could aid in the efforts of “Smart Cities.”
@@ -95,7 +95,7 @@ These opportunities would compare with those of certain foreign postal organizat
Here’s a photo of one of our whiteboards, where we track complaints of the RARCers who bike to work everyday.
-![A whiteboard with stick figures for every day o fthe week and a chart about the benefits of biking to work.]({{site.baseurl}}/assets/blog/partners-in-government/rarc.jpg)
+{% image "assets/blog/partners-in-government/rarc.jpg" "A whiteboard with stick figures for every day o fthe week and a chart about the benefits of biking to work." %}
Check out these links ([1](https://www.instagram.com/rootchopper/), [2](https://www.flickr.com/photos/rootchopper/sets/72157662509216092), [3](https://rootchopper.wordpress.com/2015/12/11/the-office-bike-commuting-matrix/)) to see where others have been posted by another RARCer, John Pickett:
diff --git a/content/posts/2016-04-27-making-a-distributed-design-team-work.md b/content/posts/2016-04-27-making-a-distributed-design-team-work.md
index 559753134..36758c0b2 100644
--- a/content/posts/2016-04-27-making-a-distributed-design-team-work.md
+++ b/content/posts/2016-04-27-making-a-distributed-design-team-work.md
@@ -29,7 +29,7 @@ room or even the same time zone.
- **Keep it sketchy.** Just because something is destined to be a digital product doesn’t mean it needs to be clean, precise, and pretty. When video chatting, hold your notebook up to the camera, or take a picture of your sketch and upload it to Slack. Colin Macarthur (in Somerville, Massachusetts) adds that when you’re doing things remotely, you spend a lot of time looking at the screen, so you start to think that the computer is the right place to be working through ideas. Often, paper is the more efficient and creative place to be doing that thinking. He uses a document camera in addition to regular video calls to make it faster to show others what he’s thinking through on paper sketches.
-![Three example sketches of graphs, maps, and page wireframes]({{site.baseurl}}/assets/blog/design/sketches.jpg)
+{% image "assets/blog/design/sketches.jpg" "Three example sketches of graphs, maps, and page wireframes" %}
*Examples of sketches we’ve shared across our distributed design team.*
- **Design in pairs.** Thinking through design challenges together at the same time can still happen when you’re not co-located. Tools like ScreenHero that allow you to share control of your desktop with a coworker are great ways to capture gestures or process movements. We’ve found that this works especially well for moving from visual design mockups to front end design implementation, or for visual brainstorming. Other shared workspace tools like Mural.ly are great for paired synthesis work, where you may have a handful of us bringing what we’ve learned together from interview sprints. Designing in pairs is also a useful learning and teaching opportunity, since you can walk through trouble spots on the same screen.
@@ -61,11 +61,11 @@ How to get started
-![Three pictures of desks including one in an office and two at home. ]({{site.baseurl}}/assets/blog/design/desks1.jpg)
+{% image "assets/blog/design/desks1.jpg" "Three pictures of desks including one in an office and two at home. " %}
*From left to right: Lindsay in Washington, D.C.; Jen in New York, NY; and Jeremy in Brooklyn, NY*
-![Three pictures of desks with varying workplace styles.]({{site.baseurl}}/assets/blog/design/desks2.jpg)
+{% image "assets/blog/design/desks2.jpg" "Three pictures of desks with varying workplace styles." %}
*From left to right: Leah in San Francisco, CA; Noah in Portland, OR; and Josh in Charlottesville, VA*
This is by no means a comprehensive list of what we’ve learned, so we’ll
diff --git a/content/posts/2016-05-02-from-spreadsheet-to-api-to-app-a-better-contract-forecast-tool.md b/content/posts/2016-05-02-from-spreadsheet-to-api-to-app-a-better-contract-forecast-tool.md
index fe301c70e..2c6f962f3 100644
--- a/content/posts/2016-05-02-from-spreadsheet-to-api-to-app-a-better-contract-forecast-tool.md
+++ b/content/posts/2016-05-02-from-spreadsheet-to-api-to-app-a-better-contract-forecast-tool.md
@@ -21,7 +21,7 @@ Executive branch agencies of the federal government are required by law to tell
The [GSA Office of Small Business Utilization](http://www.gsa.gov/portal/category/21015) (OSBU) is required to compile projections of contracting opportunities that small, disadvantaged, and women-owned businesses may be able to perform. However, GSA was only publishing their own agency data — thus requiring businesses to go to dozens of agency web sites just to find forecast information for those agencies.
-![A screenshot of a OSBU's original spreadsheet]({{site.baseurl}}/assets/blog/osbu-forecast/spreadsheet.jpg)
+{% image "assets/blog/osbu-forecast/spreadsheet.jpg" "A screenshot of a OSBU's original spreadsheet" %}
*OSBU's original vendor forecast featured thousands of rows of
complex data*
@@ -35,7 +35,7 @@ We also uploaded five additional agencies’ forecasting data into the tool to a
The beta version of the site is available at [gsaforecast.gsa.gov](https://gsaforecast.gsa.gov) and you can read OSBU Director Jerome Fletcher’s announcement post about the tool [on the GSA blog](http://gsablogs.gsa.gov/gsablog/2016/03/15/new-gsa-small-business-contracting-forecast-tool-will-drive-community-economic-development/).
-![The homepage of the new OSBU forecast tool]({{site.baseurl}}/assets/blog/osbu-forecast/forecast-tool.jpg)
+{% image "assets/blog/osbu-forecast/forecast-tool.jpg" "The homepage of the new OSBU forecast tool" %}
*The new GSA forecast tool is mobile optimized and allows for
keyword searching across multiple agencies.*
diff --git a/content/posts/2016-05-06-the-day-90-kids-came-to-code-with-18f.md b/content/posts/2016-05-06-the-day-90-kids-came-to-code-with-18f.md
index 3d77f9872..2c113e9f3 100644
--- a/content/posts/2016-05-06-the-day-90-kids-came-to-code-with-18f.md
+++ b/content/posts/2016-05-06-the-day-90-kids-came-to-code-with-18f.md
@@ -44,7 +44,7 @@ together.
The two girls later wrote this note:
-![A hand-written note that says: Codeing is fun, but also tricky but we did our best]({{site.baseurl}}/assets/blog/kids-to-work-day/kids-to-work-note.jpg)
+{% image "assets/blog/kids-to-work-day/kids-to-work-note.jpg" "A hand-written note that says: Codeing is fun, but also tricky but we did our best" %}
“Codeing [sic] is fun, but also tricky but we did our best.”
diff --git a/content/posts/2016-05-10-building-a-modern-shared-authentication-platform.md b/content/posts/2016-05-10-building-a-modern-shared-authentication-platform.md
index ca9b270b9..765ffe2f4 100644
--- a/content/posts/2016-05-10-building-a-modern-shared-authentication-platform.md
+++ b/content/posts/2016-05-10-building-a-modern-shared-authentication-platform.md
@@ -14,7 +14,7 @@ description: "18F is working iteratively with a team of technologists from acros
image: /assets/blog/login-gov/diagram.png
---
-![A conceptual diagram showing a user using a single token to authenticate with several .gov domains]({{site.baseurl}}/assets/blog/login-gov/diagram.png)
+{% image "assets/blog/login-gov/diagram.png" "A conceptual diagram showing a user using a single token to authenticate with several .gov domains" %}
_A shared login platform creates easier and more secure
transactions for the public_
diff --git a/content/posts/2016-05-10-gsa-invests-in-18fs-work-with-new-service.md b/content/posts/2016-05-10-gsa-invests-in-18fs-work-with-new-service.md
index e1237433d..6633a1dc6 100644
--- a/content/posts/2016-05-10-gsa-invests-in-18fs-work-with-new-service.md
+++ b/content/posts/2016-05-10-gsa-invests-in-18fs-work-with-new-service.md
@@ -27,7 +27,7 @@ and others have done in helping the government adopt and develop
innovative and modern technologies and practices is being
institutionalized into the core mission of GSA.
-![A large group picture of the more than 170 18F team members]({{site.baseurl}}/assets/blog/join-us/18F-IRL-2016.jpg)
+{% image "assets/blog/join-us/18F-IRL-2016.jpg" "A large group picture of the more than 170 18F team members" %}
*The 18F staff at our May meeting.*
This new service is an investment by GSA in the long-term work of
diff --git a/content/posts/2016-05-11-tackling-challenges-facing-cities-in-collaboration-with-all-levels-of-government.md b/content/posts/2016-05-11-tackling-challenges-facing-cities-in-collaboration-with-all-levels-of-government.md
index f906a3643..d97607c08 100644
--- a/content/posts/2016-05-11-tackling-challenges-facing-cities-in-collaboration-with-all-levels-of-government.md
+++ b/content/posts/2016-05-11-tackling-challenges-facing-cities-in-collaboration-with-all-levels-of-government.md
@@ -17,7 +17,7 @@ Back in San Francisco, Krista pitched the idea to Chief Innovation Officer Jay N
The General Services Administration (GSA) is partnering with the San Francisco Mayor’s [Office of Civic Innovation](http://innovatesf.com/) and the [City Innovate Foundation](http://cityinnovate.org/) to launch a new collaborative government workspace in the heart of San Francisco. The first-of-its-kind innovation lab, called [Superpublic](http://cityinnovate.org/superpublic/), will bring members of federal, state, and local governments together to collaborate with academia and private industry to foster innovative solutions to common city problems. The 5,000 sq. ft. lab will be located on the top floor of 50 U.N. Plaza and will host design workshops, prototype development, training sessions, and daily coworking.
-![An aerial picture of 50 U.N. Plaza]({{site.baseurl}}/assets/blog/superpublic/50-un-plaza.jpg) *50 U.N. Plaza, which will house Superpublic.*
+{% image "assets/blog/superpublic/50-un-plaza.jpg" "An aerial picture of 50 U.N. Plaza" %} *50 U.N. Plaza, which will house Superpublic.*
“Superpublic presents a unique opportunity to solve common problems that persist at all levels of government and demonstrate a model for collaboration that can be replicated in other cities across the United States,” said Denise Turner Roth, GSA Administrator. “This is a great example of how the General Services Administration is finding new and innovative ways to improve the way we work. Both as a catalyst for community economic development, and as a provider of modern IT services.”
diff --git a/content/posts/2016-05-12-introducing-18fs-new-visual-identity.md b/content/posts/2016-05-12-introducing-18fs-new-visual-identity.md
index 2e6ec4a16..1773f4792 100644
--- a/content/posts/2016-05-12-introducing-18fs-new-visual-identity.md
+++ b/content/posts/2016-05-12-introducing-18fs-new-visual-identity.md
@@ -66,7 +66,7 @@ now we’ve iterated on our logo, too. Our goal was to refresh the mark
while nodding to the past, to create a straightforward update that’s
accessible, bold, modern, and flexible.”
-![The old blue 18F logo and the new black 18F logo]({{site.baseurl}}/assets/blog/visual-identity/logo.jpg)
+{% image "assets/blog/visual-identity/logo.jpg" "The old blue 18F logo and the new black 18F logo" %}
Speaking to the technical considerations that impacted the logo refresh,
Eric continued, “We retained the square shape in our refresh as a nod to
@@ -82,7 +82,7 @@ members use as desktop art, weren’t exactly the highest priority “need”
item, but they were a fast way to show the team how the new system could
begin to flex in more exciting ways than just templates.
-![Text over a picture of 18F's staff and an image of a cloud against a sky, both with 18F's new logo.]({{site.baseurl}}/assets/blog/visual-identity/desktops.jpg)
+{% image "assets/blog/visual-identity/desktops.jpg" "Text over a picture of 18F's staff and an image of a cloud against a sky, both with 18F's new logo." %}
*[Sky photo](https://commons.wikimedia.org/wiki/File:Jet-sky.jpg)*
Though we’ve made great progress, our work is far from over. For now,
diff --git a/content/posts/2016-05-13-how-18f-handles-information-security-and-third-party-applications.md b/content/posts/2016-05-13-how-18f-handles-information-security-and-third-party-applications.md
index 31389ceb0..22871145e 100644
--- a/content/posts/2016-05-13-how-18f-handles-information-security-and-third-party-applications.md
+++ b/content/posts/2016-05-13-how-18f-handles-information-security-and-third-party-applications.md
@@ -34,7 +34,7 @@ assessment of GSA policies and operations.
Here’s what happened
--------------------
-[![An example screenshot of what a Google Drive preview looks like in Slack]({{site.baseurl}}/assets/blog/ig/slack-gdrive.jpg)](https://get.slack.help/hc/en-us/articles/205875058-Sharing-Google-Drive-files-in-Slack)
+[{% image "assets/blog/ig/slack-gdrive.jpg" "An example screenshot of what a Google Drive preview looks like in Slack" %}](https://get.slack.help/hc/en-us/articles/205875058-Sharing-Google-Drive-files-in-Slack)
In October 2015, one of our Slack administrators enabled [a Slack
option](https://get.slack.help/hc/en-us/articles/205875058-Sharing-Google-Drive-files-in-Slack)
diff --git a/content/posts/2016-05-17-reimagining-federal-websites-with-the-draft-us-web-design-standards.md b/content/posts/2016-05-17-reimagining-federal-websites-with-the-draft-us-web-design-standards.md
index bdc9fcb34..598ca6e17 100644
--- a/content/posts/2016-05-17-reimagining-federal-websites-with-the-draft-us-web-design-standards.md
+++ b/content/posts/2016-05-17-reimagining-federal-websites-with-the-draft-us-web-design-standards.md
@@ -52,7 +52,7 @@ Standards were able to seamlessly blend accessibility with minimal and
lightweight visual guidelines that could be scaled up and adapted to
meet the specific needs of any application; I was hooked immediately.
-![An example of cia.gov redesigned with the Draft U.S. Web Design Standards]({{site.baseurl}}/assets/blog/web-design-standards/cia-redesign.jpg)
+{% image "assets/blog/web-design-standards/cia-redesign.jpg" "An example of cia.gov redesigned with the Draft U.S. Web Design Standards" %}
*Andrew Miller used the Draft Standards pattern library to
prototype a new cia.gov experience as a design exercise.*
@@ -82,7 +82,7 @@ to relate to people who wouldn't otherwise know about the continued
effort of 18F, the USDS, and the work [President Obama spoke about at
SXSW](https://www.youtube.com/watch?v=wfsIZioIpdI).
-![An example of irs.gov redesigned with the Draft U.S. Web Design Standards]({{site.baseurl}}/assets/blog/web-design-standards/irs-redesign.jpg)
+{% image "assets/blog/web-design-standards/irs-redesign.jpg" "An example of irs.gov redesigned with the Draft U.S. Web Design Standards" %}
*Andrew Miller used the Draft Standards pattern library to
prototype a new irs.gov experience as a design exercise.*
diff --git a/content/posts/2016-05-19-content-debt-what-it-is-where-to-find-it-and-how-to-prevent-it-in-the-first-place.md b/content/posts/2016-05-19-content-debt-what-it-is-where-to-find-it-and-how-to-prevent-it-in-the-first-place.md
index d7acb35e5..80dc64e0a 100644
--- a/content/posts/2016-05-19-content-debt-what-it-is-where-to-find-it-and-how-to-prevent-it-in-the-first-place.md
+++ b/content/posts/2016-05-19-content-debt-what-it-is-where-to-find-it-and-how-to-prevent-it-in-the-first-place.md
@@ -39,7 +39,7 @@ post, I list some potential sources of content-related debt, list ways
to identify it, and then share strategies for preventing it in the first
place.
-[![A 1940s photos of students standing over a pile of scrap paper]({{site.baseurl}}/assets/blog/content/scrap-paper.jpg)](https://commons.wikimedia.org/wiki/File:Victory_Program._After_bringing_their_scrap_paper_to_school,_8c34784v.jpg)
+[{% image "assets/blog/content/scrap-paper.jpg" "A 1940s photos of students standing over a pile of scrap paper" %}](https://commons.wikimedia.org/wiki/File:Victory_Program._After_bringing_their_scrap_paper_to_school,_8c34784v.jpg)
*Students in Washington D.C. taking part in a 1942 program to collect scrap paper.*
Sources of content and documentation debt
diff --git a/content/posts/2016-05-20-get-your-pass-for-kids-to-parks-day.md b/content/posts/2016-05-20-get-your-pass-for-kids-to-parks-day.md
index 8c05e6fc0..0c609ffba 100644
--- a/content/posts/2016-05-20-get-your-pass-for-kids-to-parks-day.md
+++ b/content/posts/2016-05-20-get-your-pass-for-kids-to-parks-day.md
@@ -29,7 +29,7 @@ Just like Kids to Parks Day, the Every Kid in a Park program and website
share one goal: to get families outside, exploring natural wonders and
historic sites.
-[![The Every Kid in a Park homepage]({{site.baseurl}}/assets/blog/every-kid-in-a-park/every-kid-in-a-park-homepage.jpg)](https://www.everykidinapark.gov)
+[{% image "assets/blog/every-kid-in-a-park/every-kid-in-a-park-homepage.jpg" "The Every Kid in a Park homepage" %}](https://www.everykidinapark.gov)
Whether you’re a seasoned traveler or looking for a new experience, this
May is the perfect time to plan an adventure. And if you’re lucky enough
diff --git a/content/posts/2016-05-24-the-user-centered-redesign-of-identitytheft-gov.md b/content/posts/2016-05-24-the-user-centered-redesign-of-identitytheft-gov.md
index 8e8e08aa3..8fa1c316b 100644
--- a/content/posts/2016-05-24-the-user-centered-redesign-of-identitytheft-gov.md
+++ b/content/posts/2016-05-24-the-user-centered-redesign-of-identitytheft-gov.md
@@ -14,7 +14,7 @@ description: "IdentityTheft.gov is user-friendly and intentional. We talk to the
image: /assets/blog/identity-theft/identitytheft-home.jpg
---
-![The homepage of identitytheft.gov]({{site.baseurl}}/assets/blog/identity-theft/identitytheft-home.jpg)
+{% image "assets/blog/identity-theft/identitytheft-home.jpg" "The homepage of identitytheft.gov" %}
I first came across the redesigned IdentityTheft.gov on Reddit, of all places.
@@ -52,7 +52,7 @@ However, to serve our primary audience well we had to focus, and not try to spea
**JS and NF:** We introduced checklists in our previous iteration of identity theft guidance in 2012 — a print booklet and series of articles on [consumer.ftc.gov](http://consumer.ftc.gov). So using checklists to help users is not new for us. But I can elaborate on why we use them.
-![An example checklist from identitytheft.gov]({{site.baseurl}}/assets/blog/identity-theft/checklist.jpg)
+{% image "assets/blog/identity-theft/checklist.jpg" "An example checklist from identitytheft.gov" %}
The recovery process for an identity theft victim can vary a lot and include many tasks. We wanted a format for people using the site that was easy-to-follow. We wanted to shift the situation from a person feeling totally overwhelmed to feeling in control and that the steps are doable because we’ve laid them out in a step-by-step plan. People use checklists all the time. They’re familiar and give people a sense of agency. They also show progress. It feels good to check items off the list.
@@ -77,13 +77,13 @@ We also paid attention to potential areas of confusion when we did usability tes
One feature that people have been really excited about is the ability to create letters to send to credit bureaus, businesses, and debt collectors. It takes the guesswork out of the letter writing process.
-![A template letter that users can send to credit reporting agencies ]({{site.baseurl}}/assets/blog/identity-theft/letter.jpg)
+{% image "assets/blog/identity-theft/letter.jpg" "A template letter that users can send to credit reporting agencies " %}
We’ve also heard from a lot of victim advocates and local law enforcement, who say that they feel confident sending people to IdentityTheft.gov, knowing that the site will help them.
**MK: I really like the bar at the top, which basically tells people which phase of the project they’re in. It reminds me of something I read in the Federal Front Door [research report](https://labs.usa.gov/#research-report), which is that people want transparency into government processes. How did you think about design elements and topics like transparency?**
-![A graphic element of identitytheft.gov that shows users where they are in in a series of six labeled steps]({{site.baseurl}}/assets/blog/identity-theft/steps.jpg)
+{% image "assets/blog/identity-theft/steps.jpg" "A graphic element of identitytheft.gov that shows users where they are in in a series of six labeled steps" %}
**JS and NF:** We tried to set proper expectations at each turn for our users. For example, there’s [a page](https://www.identitytheft.gov/Information) right before you jump into the detailed questions that explains that the answers will be used to build your Identity Theft Affidavit and your personal recovery plan. These are the two main tools we provide on the site to help victims recover from identity theft. We wanted people to know why they were answering questions and what they were going to get at the end of it. In the recovery plan, we included additional information in expandable note boxes, in case users didn’t understand why we were recommending certain steps to them.
@@ -107,4 +107,4 @@ After both test cycles, we were able to make quick responsive changes to content
**JS and NF:** Yes, the total number of identity theft reports we receive has increased and the method of reporting has shifted more to the website, rather than phone. We also have a healthy portion of reports being submitted on mobile devices, which wasn’t possible before.
-[![Two pie charts that show the percentage of users reporting their identity theft online has grown from 39 percent before the launch to 68 percent post launch, including 15 percent on mobile devices.]({{site.baseurl}}/assets/blog/identity-theft/users.jpg)](https://labs.usa.gov/#research-report)
+[{% image "assets/blog/identity-theft/users.jpg" "Two pie charts that show the percentage of users reporting their identity theft online has grown from 39 percent before the launch to 68 percent post launch, including 15 percent on mobile devices." %}](https://labs.usa.gov/#research-report)
diff --git a/content/posts/2016-06-14-prototype-early-prototype-often-lesson-from-the-data-act.md b/content/posts/2016-06-14-prototype-early-prototype-often-lesson-from-the-data-act.md
index 4a3dba5df..b8cf06b76 100644
--- a/content/posts/2016-06-14-prototype-early-prototype-often-lesson-from-the-data-act.md
+++ b/content/posts/2016-06-14-prototype-early-prototype-often-lesson-from-the-data-act.md
@@ -21,7 +21,7 @@ About a year before the law is due to be implemented, Treasury will be able to a
[We’ve written before about our work on the project](https://18f.gsa.gov/tags/data-act/), and several of our 18F teammates have spoken about the work we’ve done to help implement this law. Time is an underrepresented factor in discussions of government projects like this. Decisions need to be made, and when you’re trying to coordinate multiple agencies with different systems and different priorities to do something they’ve never done before, that can take a while.
-![The DATA Act Logo]({{site.baseurl}}/assets/blog/data-act-implementation/logo.png)
+{% image "assets/blog/data-act-implementation/logo.png" "The DATA Act Logo" %}
Despite that, Kaitlin Devine, the product owner on the DATA Act implementation team, said “the team, a blend of 18F staff, contractors, and Treasury employees, is moving very fast compared to similar projects of comparable size.” Early on, when the team was much smaller and important decisions were still in flux, the team chose to build a working prototype that was flexible enough to change with the data standard. The prototype was a “data broker” that could take in spending data, validate it, and convert it into a standard format. With the broker in place, policymakers at Treasury could refine the standard and start testing data from agencies early to make sure it’d work with the system, and the team could focus on important use cases without getting distracted by edge cases. Without the broker, the development team would have spent a lot of time sitting on their hands until all the policy decisions were finalized.
@@ -32,7 +32,7 @@ Data standards are hard: Computers can read data in specific formats like XML, J
“The 18F prototype allowed actual data to drive feature development of both the schema and the application,” Devine said. This flexibility allowed us to work out technical problems while refining the data standard and “saved us months, maybe years, of learning some of these early lessons the hard way.” In addition to informing May’s milestone 1.0 release of the [DATA Act Schema](http://fedspendingtransparency.github.io/data-model/), those lessons also informed our prototype’s successor: the [official version of the DATA Act broker](https://github.com/fedspendingtransparency/data-act-broker-backend), released in alpha a few weeks ago.
@@ -42,4 +42,4 @@ Treasury took advantage of nearly every service we could offer them, all with th
The statutory deadline is less than a year away, and we will continue to work with Treasury to help them get to a successful launch, ensuring the product meets user needs from the start. Want to help the team move forward? [Treasury launched an open beta of the new USASpending.gov in November 2015, head there and send the team your feedback today](https://openbeta.usaspending.gov/).
-[![Screenshot of the USASpending.gov open beta.]({{site.baseurl}}/assets/blog/data-act-implementation/usaspendingbeta.png)](https://openbeta.usaspending.gov/)
+[{% image "assets/blog/data-act-implementation/usaspendingbeta.png" "Screenshot of the USASpending.gov open beta." %}](https://openbeta.usaspending.gov/)
diff --git a/content/posts/2016-06-15-two-agencies-participating-in-the-digital-acquisition-accelerator-pilot.md b/content/posts/2016-06-15-two-agencies-participating-in-the-digital-acquisition-accelerator-pilot.md
index 04e26a2e2..6b2ef8d9a 100644
--- a/content/posts/2016-06-15-two-agencies-participating-in-the-digital-acquisition-accelerator-pilot.md
+++ b/content/posts/2016-06-15-two-agencies-participating-in-the-digital-acquisition-accelerator-pilot.md
@@ -18,7 +18,7 @@ description: "Today, we’re thrilled to reveal that we’ve selected the Federa
image: /assets/blog/digital-acquisition-accelerator/daa-pilot-homepage.jpg
---
-[![The Digital Acquisition Accelerator homepage]({{site.baseurl}}/assets/blog/digital-acquisition-accelerator/daa-pilot-homepage.jpg)](https://pages.18f.gov/digitalaccelerator/)
+[{% image "assets/blog/digital-acquisition-accelerator/daa-pilot-homepage.jpg" "The Digital Acquisition Accelerator homepage" %}](https://pages.18f.gov/digitalaccelerator/)
Today, we’re thrilled to announce that we’ve selected the Federal Bureau
of Investigation and the U.S. Department of the Treasury as the first
diff --git a/content/posts/2016-06-16-emanuel-feld-talks-about-his-vizualization-of-government-github-organizations.md b/content/posts/2016-06-16-emanuel-feld-talks-about-his-vizualization-of-government-github-organizations.md
index 865538b12..cf9d6bc3e 100644
--- a/content/posts/2016-06-16-emanuel-feld-talks-about-his-vizualization-of-government-github-organizations.md
+++ b/content/posts/2016-06-16-emanuel-feld-talks-about-his-vizualization-of-government-github-organizations.md
@@ -13,13 +13,13 @@ image: /assets/blog/emanuel-feld/github-repositories.jpg
What does the global government open source community look like? That’s the question that Emanuel Feld, a civic technologist in Washington D.C., wanted to answer when [he created a visualization](https://emanuelfeld.github.io/blog/2016/04/27/government-github-ecosystem.html) showing how government repos on GitHub are connected and interrelated.
-[![A diagram of GitHub contributions by many government agencies]({{site.baseurl}}/assets/blog/emanuel-feld/contribution.svg)](https://emanuelfeld.github.io/assets/images/contribution.svg)
+[{% image "assets/blog/emanuel-feld/contribution.svg" "A diagram of GitHub contributions by many government agencies" %}](https://emanuelfeld.github.io/assets/images/contribution.svg)
Feld used the GitHub API to create a database of government GitHub
organizations and repositories, and then used that information to
examine how the government repos interact with one another.
-[![A diagram of government GitHub repositories]({{ site.baseurl }}/assets/blog/emanuel-feld/repository.svg)](https://emanuelfeld.github.io/assets/images/repository.svg)
+[{% image "assets/blog/emanuel-feld/repository.svg" "A diagram of government GitHub repositories" %}](https://emanuelfeld.github.io/assets/images/repository.svg)
The above graph, for instance, shows how government organizations fork
code from other government organizations. This information is
diff --git a/content/posts/2016-06-17-exciting-additions-to-analytics-usa-gov.md b/content/posts/2016-06-17-exciting-additions-to-analytics-usa-gov.md
index 95358133e..726edb9d2 100644
--- a/content/posts/2016-06-17-exciting-additions-to-analytics-usa-gov.md
+++ b/content/posts/2016-06-17-exciting-additions-to-analytics-usa-gov.md
@@ -22,11 +22,11 @@ hero: false
We’ve expanded [analytics.usa.gov](https://analytics.usa.gov/) to include 15(!) more agency-specific dashboard pages. We now offer agency-specific analytics data pages for a total of 25 major federal agencies, and each one is accessible from the dropdown menu at the top of the site.
-![The analytics.usa.gov homepage pointing out the participating websites menu]({{ site.baseurl }}/assets/blog/dap/analytics-homepage-2016.png)
+{% image "assets/blog/dap/analytics-homepage-2016.png" "The analytics.usa.gov homepage pointing out the participating websites menu" %}
Additionally, we’ve moved the downloadable datasets to their own pages, rather than be located on the dashboard pages themselves. The page to download aggregated data for all participating sites is now [analytics.usa.gov/data](https://analytics.usa.gov/data), and each agency-specific page has a [corresponding data page](https://analytics.usa.gov/justice/data/), as well.
-![Screenshot of the new standalone downloads page]({{ site.baseurl }}/assets/blog/dap/analytics-downloads-2016.png)
+{% image "assets/blog/dap/analytics-downloads-2016.png" "Screenshot of the new standalone downloads page" %}
We’re excited to offer the public this expanded view of web analytics data, and we hope you find it useful!
diff --git a/content/posts/2016-06-21-using-plain-language-to-bridge-the-gap-between-government-and-industry.md b/content/posts/2016-06-21-using-plain-language-to-bridge-the-gap-between-government-and-industry.md
index 4ecd43897..dd1dbe96f 100644
--- a/content/posts/2016-06-21-using-plain-language-to-bridge-the-gap-between-government-and-industry.md
+++ b/content/posts/2016-06-21-using-plain-language-to-bridge-the-gap-between-government-and-industry.md
@@ -98,7 +98,7 @@ brainstorming sessions to write a [step by step
guide](http://www.gsa.gov/portal/category/100406) to what people need
to know when submitting an offer for an IT Schedule 70 contract.
-[![A screenshot from the IT Schedule 70 guide]({{site.baseurl}}/assets/blog/content/schedule-70.jpg)](http://www.gsa.gov/portal/category/100406)
+[{% image "assets/blog/content/schedule-70.jpg" "A screenshot from the IT Schedule 70 guide" %}](http://www.gsa.gov/portal/category/100406)
This project might seem out of the norm for 18F. Maybe it doesn’t seem
high-tech enough to fit in with the kind of work we do — it’s all words
diff --git a/content/posts/2016-07-06-illinois-fourth-grade-class-uses-every-kid-in-a-park-to-explore.md b/content/posts/2016-07-06-illinois-fourth-grade-class-uses-every-kid-in-a-park-to-explore.md
index 5b9e139cb..d37bff797 100644
--- a/content/posts/2016-07-06-illinois-fourth-grade-class-uses-every-kid-in-a-park-to-explore.md
+++ b/content/posts/2016-07-06-illinois-fourth-grade-class-uses-every-kid-in-a-park-to-explore.md
@@ -28,7 +28,7 @@ Each student selected a state at the beginning of the year to build a background
These projects were then displayed for our open house.
-![Models of the Statue of Liberty and other national parks created by the fourth grade students.]({{ site.baseurl }}/assets/blog/every-kid-in-a-park/nps-models.jpg)
+{% image "assets/blog/every-kid-in-a-park/nps-models.jpg" "Models of the Statue of Liberty and other national parks created by the fourth grade students." %}
*Monuments from National Park Service sites that were created by fourth graders in Monticello, IL.*
@@ -40,7 +40,7 @@ Lastly, students used the internet to find the distance from Monticello, IL to t
The students were amazed by the size of the protected land and the beautiful sites. We watched bits and pieces of the PBS program on the National Parks, which endeared them to President Theodore Roosevelt, President Franklin Roosevelt, and John Muir. In turn, they found pages of quotes on the websites which we included on another wall of the gym.
-![Stamps for Glacier, Glacier Bay, Canyonlands, and other national parks drawn and colored by the fourth graders.]({{ site.baseurl }}/assets/blog/every-kid-in-a-park/nps-stamps.jpg)
+{% image "assets/blog/every-kid-in-a-park/nps-stamps.jpg" "Stamps for Glacier, Glacier Bay, Canyonlands, and other national parks drawn and colored by the fourth graders." %}
*Students made stamps for their National Park, which hung in the school gymnasium.*
diff --git a/content/posts/2016-07-14-elaine-kamlley-a-developer-commited-diversity.md b/content/posts/2016-07-14-elaine-kamlley-a-developer-commited-diversity.md
index 17d5a625e..3466684f6 100644
--- a/content/posts/2016-07-14-elaine-kamlley-a-developer-commited-diversity.md
+++ b/content/posts/2016-07-14-elaine-kamlley-a-developer-commited-diversity.md
@@ -11,11 +11,10 @@ front-end developer and a member of our Outreach Team"
description: "All throughout the summer, we’ll be profiling members
across the 18F team. We’re starting with Elaine Kamlley, who is both a
front-end developer and a member of our Outreach Team*.*"
-image: /assets/img/team/elaine.jpg
hero: false
---
diff --git a/content/posts/2016-07-19-strategies-for-starting-your-own-writing-lab.md b/content/posts/2016-07-19-strategies-for-starting-your-own-writing-lab.md
index bc88859dc..c1f841dc2 100644
--- a/content/posts/2016-07-19-strategies-for-starting-your-own-writing-lab.md
+++ b/content/posts/2016-07-19-strategies-for-starting-your-own-writing-lab.md
@@ -14,7 +14,7 @@ hero: false
---
diff --git a/content/posts/2016-07-21-buying-better-digital-products-part-1-proto-personas-and-understanding-the-problem.md b/content/posts/2016-07-21-buying-better-digital-products-part-1-proto-personas-and-understanding-the-problem.md
index 2d3bf07f9..921fea436 100644
--- a/content/posts/2016-07-21-buying-better-digital-products-part-1-proto-personas-and-understanding-the-problem.md
+++ b/content/posts/2016-07-21-buying-better-digital-products-part-1-proto-personas-and-understanding-the-problem.md
@@ -68,7 +68,7 @@ strategic planning internally but should not be viewed as a substitute
for talking with actual users.
@@ -78,7 +78,7 @@ they were asked to create a name then outline that user’s demographic
information, needs, and goals as well as behaviors and beliefs, like
below:
-
+{% image "assets/blog/digital-acquisition-accelerator/persona-sketch.jpg" "A template for sketching personas to give to participants." %}
Then, agency teams determined a series of 5-7 traits to compare across
proto-personas. Using these traits, teams narrowed down their options
@@ -92,7 +92,7 @@ for the solicitation in the coming weeks. Here’s an example of a
completed persona:
diff --git a/content/posts/2016-07-26-buying-better-digital-products-part-2-setting-the-product-vision-and-strategy.md b/content/posts/2016-07-26-buying-better-digital-products-part-2-setting-the-product-vision-and-strategy.md
index 4cc04c42b..248bcb6b6 100644
--- a/content/posts/2016-07-26-buying-better-digital-products-part-2-setting-the-product-vision-and-strategy.md
+++ b/content/posts/2016-07-26-buying-better-digital-products-part-2-setting-the-product-vision-and-strategy.md
@@ -62,7 +62,7 @@ product. As the sticky notes piled up, the teams clustered similar ideas
together and labeled those groups.
diff --git a/content/posts/2016-07-26-new-pilot-aims-to-streamline-notice-and-comment-process.md b/content/posts/2016-07-26-new-pilot-aims-to-streamline-notice-and-comment-process.md
index a84c830da..13cbc833d 100644
--- a/content/posts/2016-07-26-new-pilot-aims-to-streamline-notice-and-comment-process.md
+++ b/content/posts/2016-07-26-new-pilot-aims-to-streamline-notice-and-comment-process.md
@@ -15,7 +15,7 @@ image: /assets/blog/eregs-comments/eregs-comment.gif
hero: false
---
@@ -35,7 +35,7 @@ This step is a critical function in our democracy. Many of the details of govern
While many commenters continue to use paper or email, the current digital process for public comment limits the submitter to a single 5,000 character text field, with attachments (like spreadsheets, PDFs, etc.). Unless the submitter explicitly adds it, this format includes no contextual information — regulators won’t know which sections of the proposal are being critiqued. When proposed rules are often hundreds of pages of nuanced language, it can be difficult to provide constructive feedback. These rules can sometimes receive thousands of comments, which must be manually or semi-automatically sorted by federal agencies. Without a clear connection between comments and relevant sections of a proposed rule, agencies have to spend a huge amount of time analyzing, sorting, and responding to comments. This is a costly and error-prone endeavor; we can do better.
diff --git a/content/posts/2016-07-29-live-streamed-demos-for-exponential-transparency-and-information-sharing.md b/content/posts/2016-07-29-live-streamed-demos-for-exponential-transparency-and-information-sharing.md
index bbf3ccb59..0d6c79c9b 100644
--- a/content/posts/2016-07-29-live-streamed-demos-for-exponential-transparency-and-information-sharing.md
+++ b/content/posts/2016-07-29-live-streamed-demos-for-exponential-transparency-and-information-sharing.md
@@ -24,7 +24,7 @@ So we explored some options and landed on a creative option — livestreaming ou
government agencies, doesn’t require extraneous plugins to operate, allows you to easily stream, but also automatically creates a viewable
file afterwards at the same URL. YouTube is widely accessible behind government firewalls, and has useful functionality for both presenters (Hangouts On Air, an enhanced version of the video chat program) and viewers. After mistakenly launching and ending the first live attempt before it was supposed to go live, we learned how to use the tool, and it really helped us share information across many agencies, teams, and individuals. We’re also excited about this serving as an archive of our work.
-![A screenshot of a youtube video used to demo the e-regs work.]({{ site.baseurl }}/assets/blog/eregs/demo-video.jpg)
+{% image "assets/blog/eregs/demo-video.jpg" "A screenshot of a youtube video used to demo the e-regs work." %}
### Major lessons and benefits that made this work:
diff --git a/content/posts/2016-08-02-jacob-harris-from-big-data-journalism-to-micro-purchase-platforms.md b/content/posts/2016-08-02-jacob-harris-from-big-data-journalism-to-micro-purchase-platforms.md
index 2e6b4cf32..69ba658bd 100644
--- a/content/posts/2016-08-02-jacob-harris-from-big-data-journalism-to-micro-purchase-platforms.md
+++ b/content/posts/2016-08-02-jacob-harris-from-big-data-journalism-to-micro-purchase-platforms.md
@@ -8,12 +8,11 @@ tags:
- micro-purchase platforms
- how we work
excerpt: "Jacob Harris joined 18F in May of 2015 after nine years working as a developer at The New York Times. He currently works on the Micro-purchase Platform, which enables vendors to place bids on opportunities to deliver open source code that costs $3,500 or less."
-image: /assets/img/team/jacobharris.jpg
hero: false
---
diff --git a/content/posts/2016-08-10-patterns-for-managing-multi-tenant-cloud-environments.md b/content/posts/2016-08-10-patterns-for-managing-multi-tenant-cloud-environments.md
index feea7c3f7..4d5eecc1d 100644
--- a/content/posts/2016-08-10-patterns-for-managing-multi-tenant-cloud-environments.md
+++ b/content/posts/2016-08-10-patterns-for-managing-multi-tenant-cloud-environments.md
@@ -56,7 +56,7 @@ Systems built on cloud infrastructure must assume the infrastructure is unreliab
To extend the expiry date and prevent infrastructure and the systems sitting on them being garbage collected, you must register the system — and its owner — in [Chandika](https://github.com/18F/chandika), our system registry (see below). In this way, we can ensure we can trace every resource in every account to the system it belongs to and the owner of that system, and bill the operational cost of that system correctly. We also prevent our AWS account from becoming cluttered up with zombie infrastructure — random servers, S3 buckets, or load balancers whose purpose is unknown but which we must continue to pay for in case turning them off causes the failure of some critical system.
diff --git a/content/posts/2016-08-11-holly-allen-helping-engineer-a-better-18F.md b/content/posts/2016-08-11-holly-allen-helping-engineer-a-better-18F.md
index cb94cd699..f1e66b3e9 100644
--- a/content/posts/2016-08-11-holly-allen-helping-engineer-a-better-18F.md
+++ b/content/posts/2016-08-11-holly-allen-helping-engineer-a-better-18F.md
@@ -8,11 +8,10 @@ tags:
- college scorecard
excerpt: "Holly Allen came to 18F from Dreamworks Animation and the Public Library of Science. She joined 18F in pursuit of a way \"to use technology to address big societal problems.\" After hearing about the U.S. Digital Service and 18F from US Chief Technology Officer, Megan Smith, she was inspired to join."
description: "Holly Allen came to 18F from Dreamworks Animation and the Public Library of Science. She joined 18F in pursuit of a way \"to use technology to address big societal problems.\" After hearing about the U.S. Digital Service and 18F from US Chief Technology Officer, Megan Smith, she was inspired to join."
-image: /assets/img/team/holly.jpg
hero: false
---
diff --git a/content/posts/2016-08-25-micro-purchase-design-philosophy-do-one-thing-well.md b/content/posts/2016-08-25-micro-purchase-design-philosophy-do-one-thing-well.md
index a4ba67b1e..ab8618ac1 100644
--- a/content/posts/2016-08-25-micro-purchase-design-philosophy-do-one-thing-well.md
+++ b/content/posts/2016-08-25-micro-purchase-design-philosophy-do-one-thing-well.md
@@ -118,7 +118,7 @@ nil — for instance, a NullBid object with similar methods to the Bid
model is returned when the auction’s winning bid is not available. Do
you notice the trend?
-![Objects playing the role of Controller, Service, Validator, and Rule]({{ site.baseurl}}/assets/blog/micro-purchase/roles.png)
+{% image "assets/blog/micro-purchase/roles.png" "Objects playing the role of Controller, Service, Validator, and Rule" %}
### Population control
@@ -219,7 +219,7 @@ Service Objects (which contains all of the shared code); the controller
just needs to convert the input and output as appropriate.
-![Both API and HTML controllers use PlaceBid Service]({{ site.baseurl }}/assets/blog/micro-purchase/service.png)
+{% image "assets/blog/micro-purchase/service.png" "Both API and HTML controllers use PlaceBid Service" %}
### Other applications
diff --git a/content/posts/2016-08-29-data-act-prototype-simplicty-is-key.md b/content/posts/2016-08-29-data-act-prototype-simplicty-is-key.md
index 3b96ea54f..916654c90 100644
--- a/content/posts/2016-08-29-data-act-prototype-simplicty-is-key.md
+++ b/content/posts/2016-08-29-data-act-prototype-simplicty-is-key.md
@@ -83,7 +83,7 @@ recommend against falling into this trap; your small code base will
quickly grow larger than anticipated and your early technical decisions
have had long-lasting ramifications.
-![Diagram matching above description]({{ site.baseurl }}/assets/blog/data-act-implementation/diagram.png)
+{% image "assets/blog/data-act-implementation/diagram.png" "Diagram matching above description" %}
## Simplicity avoids scaring away agencies
diff --git a/content/posts/2016-09-06-nicole-fenton-a-wordsmith-joins-government.md b/content/posts/2016-09-06-nicole-fenton-a-wordsmith-joins-government.md
index 2c3688e44..56abb1885 100644
--- a/content/posts/2016-09-06-nicole-fenton-a-wordsmith-joins-government.md
+++ b/content/posts/2016-09-06-nicole-fenton-a-wordsmith-joins-government.md
@@ -13,11 +13,10 @@ description: Nicole Fenton joined 18F in September of 2015. Before 18F, Nicole w
a content strategist at Facebook, Lab Zero, and Mule Design in San Francisco. She
started her professional writing practice at Apple, where she served as communications
lead for five years and helped launch the original iPhone and iPad.
-image: "/assets/img/team/nicole-fenton.jpg"
hero: false
---
diff --git a/content/posts/2016-09-12-james-scott-automating-engineering-better-government.md b/content/posts/2016-09-12-james-scott-automating-engineering-better-government.md
index c13153b51..2351463fc 100644
--- a/content/posts/2016-09-12-james-scott-automating-engineering-better-government.md
+++ b/content/posts/2016-09-12-james-scott-automating-engineering-better-government.md
@@ -7,11 +7,10 @@ tags:
- cloud.gov
excerpt: "James Scott's career has taken him from The University of Virginia to Intel before landing at 18F. Here, he has worked on cloud.gov and our diversity guild. His advice for people thinking about joining us: Do it."
description: "James Scott's career has taken him from The University of Virginia to Intel before landing at 18F. Here, he has worked on cloud.gov and our diversity guild. His advice for people thinking about joining us: Do it."
-image: /assets/img/team/jamesscott.jpg
hero: false
---
diff --git a/content/posts/2016-09-27-usa-gov-updates-vote-gov-now-leaner-faster-multilingual.md b/content/posts/2016-09-27-usa-gov-updates-vote-gov-now-leaner-faster-multilingual.md
index 1db724722..cd55b7120 100644
--- a/content/posts/2016-09-27-usa-gov-updates-vote-gov-now-leaner-faster-multilingual.md
+++ b/content/posts/2016-09-27-usa-gov-updates-vote-gov-now-leaner-faster-multilingual.md
@@ -8,11 +8,10 @@ tags:
- user-centered design
excerpt: "One year ago this week, we launched vote.gov. It was a concise and simple site with a single mission: direct citizens through the voter registration process as quickly as possible. Today, on National Voter Registration Day, we're launching this new version."
description: "One year ago this week, we launched vote.gov. It was a concise and simple site with a single mission: direct citizens through the voter registration process as quickly as possible. Today, on National Voter Registration Day, we're launching this new version."
-image: /assets/blog/vote-usa-gov/vote-gov.jpg
hero: false
---
diff --git a/content/posts/2016-10-14-iterative-workplace-design-denver-federal-center.md b/content/posts/2016-10-14-iterative-workplace-design-denver-federal-center.md
index 36320b8a7..06dcdb17d 100644
--- a/content/posts/2016-10-14-iterative-workplace-design-denver-federal-center.md
+++ b/content/posts/2016-10-14-iterative-workplace-design-denver-federal-center.md
@@ -16,7 +16,7 @@ Not long ago, the General Service Administration’s [regional headquarters on t
Cubicles and private offices have a certain appeal to them: You can leave things there overnight, put up photos of your family, and keep your work organized on your desk. They also take up a lot of space, much more than most people actually need, and constrain people to working in the same space all the time. When Myers, his colleague Shelly Baxter, and the design team started thinking about how to make more space in the office, they started with the cube walls. “One of the designers took the existing furniture and came up with a pretty creative layout,” Baxter said.
@@ -27,7 +27,7 @@ When tenants tour the GSA space today, they see standing desks, huddle rooms wit
Part of GSA’s mission is to find innovative ways to [design workplaces that make the federal government more efficient and productive](http://www.gsa.gov/portal/content/134874). The Rocky Mountain Region houses 28 tenants on the Denver Federal Center campus. Myers and Baxter said they set up several workplaces in the building as working showrooms. Each room had different furniture and layouts and the staff would offer tours for their tenants to gauge their reactions and show them what was possible for their own offices.
@@ -36,14 +36,14 @@ PBS was, in a way, exercising [play 1 from the Digital Services Playbook](https:
From these showrooms, they learned their tenants all had more employees to squeeze into smaller spaces than they had designed for. They also learned what worked and what people wanted more of. They learned they’d need to create a distraction-free space so people could get away from the noisy, high traffic parts of the building and get work done, and spaces to take phone calls or meet with each other without disturbing others. To meet these needs, they created a quiet zone and another area with a wide mix of phone booths and conference rooms, so whether you’re on the phone by yourself, or in a group of 20, there’s a place for you to meet.
Over time, they’ve learned subtler things about the space: “Better access to wifi … added electrical outlets … we enhanced white noise,” said Baxter, and they’ve learned a lot about how human behavior didn’t match their assumptions. “We’ve noticed that certain people are magnets,” said Myers, “if you’re a manager and you sit somewhere, for whatever reason, your team ends up sitting near you.” Whether that’s because of unspoken pressure from managers to be near their employees, or personal preference, it was an unexpected outcome they hadn’t really designed for.
@@ -52,6 +52,6 @@ It’s been a little over a year since the redesign took place, but the work is
Redesigning the GSA’s workplace has been an iterative effort to discover how people want to work, how they can be most productive, and designing around those needs. It’s a great example of how human-centered design manifests itself in spaces outside of the tech world.
diff --git a/content/posts/2016-10-25-three-small-steps-you-can-take-to-reboot-agile-in-your-organization.md b/content/posts/2016-10-25-three-small-steps-you-can-take-to-reboot-agile-in-your-organization.md
index d12dbc833..1c0650488 100644
--- a/content/posts/2016-10-25-three-small-steps-you-can-take-to-reboot-agile-in-your-organization.md
+++ b/content/posts/2016-10-25-three-small-steps-you-can-take-to-reboot-agile-in-your-organization.md
@@ -76,7 +76,7 @@ simple tool whereby tasks are organized, grouped, and tracked across a
segment of time, or sprints. As these tasks moved forward, we could use
the dedicated cards to monitor progress:
-![A Trello card from the NTIS team.]({{site.baseurl}}/assets/blog/agile-workshop/3-steps-trello-card.jpg)
+{% image "assets/blog/agile-workshop/3-steps-trello-card.jpg" "A Trello card from the NTIS team." %}
## Step three: Monitor your progress
@@ -103,7 +103,7 @@ always be there, but they can be mitigated if they make things easier,
and gradually introducing agile processes can encourage broader
adoption.
-![Comments on the team's Trello board.]({{site.baseurl}}/assets/blog/agile-workshop/3-steps-trello-comments.jpg)
+{% image "assets/blog/agile-workshop/3-steps-trello-comments.jpg" "Comments on the team's Trello board." %}
## What we learned
**Agile doesn’t have to be a “rip and replace” process**. Perhaps one of
diff --git a/content/posts/2016-10-26-writing-for-web-easy-writing-for-users-not.md b/content/posts/2016-10-26-writing-for-web-easy-writing-for-users-not.md
index b65aba56c..7bb74c491 100644
--- a/content/posts/2016-10-26-writing-for-web-easy-writing-for-users-not.md
+++ b/content/posts/2016-10-26-writing-for-web-easy-writing-for-users-not.md
@@ -44,7 +44,7 @@ help projects develop a singular voice and maintain consistent style and
tone.
diff --git a/content/posts/2016-12-14-how-to-run-an-efficient-meeting.md b/content/posts/2016-12-14-how-to-run-an-efficient-meeting.md
index 97d4852a6..c2a884f69 100644
--- a/content/posts/2016-12-14-how-to-run-an-efficient-meeting.md
+++ b/content/posts/2016-12-14-how-to-run-an-efficient-meeting.md
@@ -99,7 +99,7 @@ You should work to **develop a presentation style** through iterative practice a
When leading a discussion, pay attention to who has a loud voice in the room and **elevate other voices** to ensure the meeting is useful to everyone. You can seek feedback with a show of hands and call on people that didn’t talk as much in the meeting. When moving on from a topic, be deliberate and don’t allow someone to keep the conversation frozen because they are emphatic — that rewards their insistence and harms your authority.
-
+{% image "assets/blog/meeting-facilitation/workshopping.jpg" "Members of the 18F team at a workshop meeting." %}
### Wrapping up
diff --git a/content/posts/2017-01-04-tracking-the-us-governments-progress-on-moving-https.md b/content/posts/2017-01-04-tracking-the-us-governments-progress-on-moving-https.md
index d794fc652..c42b6df81 100644
--- a/content/posts/2017-01-04-tracking-the-us-governments-progress-on-moving-https.md
+++ b/content/posts/2017-01-04-tracking-the-us-governments-progress-on-moving-https.md
@@ -12,7 +12,7 @@ image: /assets/blog/https-progress/white-house-https.png
hero: false
---
-![WhiteHouse.gov using HTTPS.]({{site.baseurl}}/assets/blog/https-progress/white-house-https.png)
+{% image "assets/blog/https-progress/white-house-https.png" "WhiteHouse.gov using HTTPS." %}
[HTTPS](https://https.cio.gov/faq/#what-does-https-do%3f) is a protocol to create secure and private connections to websites or services on the internet. You're using HTTPS to read this article, as indicated by the `https://` and lock icon in your browser's location bar above. Because we use HTTPS for our website, it's very difficult for anyone to modify or inspect the communication between your device and our servers. If we used plain HTTP, it would be very easy for an attacker to insert malware or tracking information into your browser. HTTPS is the [minimum baseline that users should expect](https://18f.gsa.gov/2014/11/13/why-we-use-https-in-every-gov-website-we-make/) from any website they visit, government or otherwise.
@@ -62,13 +62,13 @@ For "parent" federal .gov domains (for example, gsa.gov), we have 18 months of s
Over the last 18 months, HTTPS and HSTS implementation among parent .gov domains has gone up substantially, with the use and enforcement of HTTPS moving from a minority to a majority:
-![HTTPS among "parent" .gov domains in the executive branch moved from around 30% to around 75%.]({{ site.baseurl }}/assets/blog/https-progress/chart-1-https-parent-domains.png)
+{% image "assets/blog/https-progress/chart-1-https-parent-domains.png" "HTTPS among "parent" .gov domains in the executive branch moved from around 30% to around 75%." %}
In particular, HSTS use among .gov domains was almost non-existent (2%) before M-15-13, and most or all of that was from [an 18F effort in February 2015 to preload the first 20 .gov domains](https://18f.gsa.gov/2015/02/09/the-first-gov-domains-hardcoded-into-your-browser-as-all-https/). HSTS is now present on almost half (43%) of live executive branch parent .gov domains.
Though we don't have time series data for subdomains, we can compare a snapshot of where the approximately 1,000 parent domains and a sizeable collection of approximately 26,000 subdomains ended up on December 31, 2016:
-![HTTPS usage as of December 31, 2016 for .gov parent domains and subdomains in the executive branch.]({{ site.baseurl }}/assets/blog/https-progress/chart-2-https-all-domains.png)
+{% image "assets/blog/https-progress/chart-2-https-all-domains.png" "HTTPS usage as of December 31, 2016 for .gov parent domains and subdomains in the executive branch." %}
When broadened to include subdomains, the numbers are lower than when only measuring parent domains. This is likely in part because identifying parent domains is much easier (even inside an agency), and in part because most agencies have a "long tail" of unused, abandoned, testing, or staging subdomains.
@@ -84,7 +84,7 @@ As of right now, that list has about 1,700 "live" federal websites that use a .g
When we break out how many of those visits went to sites that use and enforce HTTPS and use an HSTS policy, the numbers are much higher than if we just measured all subdomains without weighting by traffic:
-![HTTPS usage for .gov domains in the executive branch when measured by amount of web visits.]({{ site.baseurl }}/assets/blog/https-progress/chart-3-https-by-web-traffic.png)
+{% image "assets/blog/https-progress/chart-3-https-by-web-traffic.png" "HTTPS usage for .gov domains in the executive branch when measured by amount of web visits." %}
Of course, this isn't a complete dataset either — none of these are. And each one of them points to more work for federal agencies to do to eliminate the use of insecure connections to their services.
diff --git a/content/posts/2017-01-06-open-source-collaboration-across-agencies-to-improve-https-deployment.md b/content/posts/2017-01-06-open-source-collaboration-across-agencies-to-improve-https-deployment.md
index 854380d11..2aaf50498 100644
--- a/content/posts/2017-01-06-open-source-collaboration-across-agencies-to-improve-https-deployment.md
+++ b/content/posts/2017-01-06-open-source-collaboration-across-agencies-to-improve-https-deployment.md
@@ -12,7 +12,7 @@ image: /assets/blog/pshtt-post/https-report-title.png
hero: false
---
-![Cover of HTTPS report delivered by DHS to agency security offices.]({{site.baseurl}}/assets/blog/pshtt-post/https-report-title.png)
+{% image "assets/blog/pshtt-post/https-report-title.png" "Cover of HTTPS report delivered by DHS to agency security offices." %}
Sometimes, to accomplish a worthy goal, people and organizations benefit from a little push.
@@ -71,9 +71,9 @@ Together, `pshtt`'s analysis can determine whether a domain fully requires HTTPS
Here's an example of what our reports look like:
-![Chart showing HTTPS progress for the Office of Personnel Management.]({{site.baseurl}}/assets/blog/pshtt-post/opm-chart.png)
+{% image "assets/blog/pshtt-post/opm-chart.png" "Chart showing HTTPS progress for the Office of Personnel Management." %}
-![Table showing HTTPS progress for the Office of Personnel Management.]({{site.baseurl}}/assets/blog/pshtt-post/opm-table.jpg)
+{% image "assets/blog/pshtt-post/opm-table.jpg" "Table showing HTTPS progress for the Office of Personnel Management." %}
_(OPM has since fixed, or has plans to fix, the findings in this image.)_
diff --git a/content/posts/2017-01-11-the-best-way-to-build-big-is-to-start-small.md b/content/posts/2017-01-11-the-best-way-to-build-big-is-to-start-small.md
index 189258b61..e32718f09 100644
--- a/content/posts/2017-01-11-the-best-way-to-build-big-is-to-start-small.md
+++ b/content/posts/2017-01-11-the-best-way-to-build-big-is-to-start-small.md
@@ -34,7 +34,7 @@ Big software systems happen in two major varieties:
Before diving into the best way to mix and match these patterns, I want to describe each of their growth patterns and risks.
A monolith is one big application. Monoliths are easy to understand
@@ -62,8 +62,8 @@ applications. Sometimes they’ll be forced to sign into many
applications.
Given that monoliths are simpler than services, why would we ever
@@ -77,8 +77,8 @@ developers have a hard time finding the code they need to get their work
done. They have a hard time managing the complexity and the bugs.
Monoliths that grow too large stagger under their own weight. Product
diff --git a/content/posts/2017-02-02-cloud-gov-is-now-fedramp-authorized.md b/content/posts/2017-02-02-cloud-gov-is-now-fedramp-authorized.md
index 7debc4e63..8c7429f4a 100644
--- a/content/posts/2017-02-02-cloud-gov-is-now-fedramp-authorized.md
+++ b/content/posts/2017-02-02-cloud-gov-is-now-fedramp-authorized.md
@@ -1,5 +1,6 @@
---
title: cloud.gov is now FedRAMP Authorized for use by federal agencies
+layout: post
authors:
- britta-gustafson
- jameshupp
@@ -12,19 +13,13 @@ tags:
- devops
excerpt: We’re delighted to announce that cloud.gov is now FedRAMP Authorized, which enables agencies to quickly transition their web-based services to efficient and easy-to-use cloud hosting. FedRAMP Authorized status marks completion of a comprehensive security and compliance assessment that enables federal agencies to start using cloud.gov with significantly reduced effort. cloud.gov is a government-customized hosting platform that takes care of technical infrastructure and security compliance requirements.
description: what
-images:
-- /assets/blog/cloud-gov/logo-badge.png
-- /assets/blog/cloud-gov/fedramp-badge.jpg
-- /assets/blog/cloud-gov/fedramp-ready.png
-- /assets/blog/cloud-gov/intro-diagram.svg
-- /assets/blog/cloud-gov/cloud-gov-chart.svg
hero: false
---
-
-
-
-
+
We’re delighted to announce that [cloud.gov](https://cloud.gov/) is
@@ -99,7 +94,7 @@ Your development team sets up the application on cloud.gov, and
cloud.gov handles the security, maintenance, and compliance of the
underlying platform. Here’s what that looks like:
-
+{% image "assets/blog/cloud-gov/intro-diagram.svg" "" %}
You set up and maintain your web application code.
You can run your application on the programming language stacks that cloud.gov maintains. Or you can run it on a custom programming language stack that you maintain.
@@ -121,7 +116,7 @@ implementations for the remaining 15 controls, such as ensuring you make
data backups and using reliable DNS (Domain Name System) name servers
for your websites.
-![A bar chart showing the portion of security controls handled by customers, cloud.gov, and shared between the two.]({{site.baseurl}}{{page.images[4]}})
+{% image "assets/blog/cloud-gov/cloud-gov-chart.svg" "A bar chart showing the portion of security controls handled by customers, cloud.gov, and shared between the two." %}
cloud.gov is also a building block for vendors and contractors that
supply services to federal agencies. They can submit proposals to
diff --git a/content/posts/2017-03-13-us-web-design-standards-releases-version-10.md b/content/posts/2017-03-13-us-web-design-standards-releases-version-10.md
index 40ba183fb..f5b91c045 100644
--- a/content/posts/2017-03-13-us-web-design-standards-releases-version-10.md
+++ b/content/posts/2017-03-13-us-web-design-standards-releases-version-10.md
@@ -14,7 +14,7 @@ The U.S. Web Design Standards are a library of design guidelines and code to hel
By using the well-tested and easy-to-implement code from the Standards, developers can quickly create new websites or have a leg-up in updating existing services to have a modern, consistent feel. It includes code and guidelines for forms, typography, buttons, alerts, and more. The Standards are open source and free to use, but our team is also available to work closely with federal agencies to develop custom features or train teams on implementing the Standards.
diff --git a/content/posts/2017-04-27-remembering-larry-matthias-early-partner-excellent-civil-servant.md b/content/posts/2017-04-27-remembering-larry-matthias-early-partner-excellent-civil-servant.md
index fb98f73bc..5ab9519d2 100644
--- a/content/posts/2017-04-27-remembering-larry-matthias-early-partner-excellent-civil-servant.md
+++ b/content/posts/2017-04-27-remembering-larry-matthias-early-partner-excellent-civil-servant.md
@@ -11,7 +11,7 @@ tags:
excerpt: "We’re writing this to remember and pay tribute to Larry Mathias, who passed away unexpectedly this month. Larry was a senior contracting officer at the General Services Administration. He managed technology systems for the OASIS program and was instrumental in helping GSA launch this new contract vehicle. Larry was also an early believer in 18F."
---
-![Larry Mathias was an early partner for 18F]({{site.baseurl}}/assets/blog/larry/larry.jpg)
+{% image "assets/blog/larry/larry.jpg" "Larry Mathias was an early partner for 18F" %}
We’re writing this to remember and pay tribute to Larry Mathias, who passed away unexpectedly this month.
@@ -41,6 +41,6 @@ Larry connected us to other civil servants who also wanted to make government be
Larry was passionate about making things. Between meetings we talked about photography and 3D printing and Arduinos and NeoPixels. We loved him so much we named our GitHub bot after him:
-![A screenshot of the Larrybot notifying the team of a pull request being closed]({{site.baseurl}}/assets/blog/larry/larrybot.png)
+{% image "assets/blog/larry/larrybot.png" "A screenshot of the Larrybot notifying the team of a pull request being closed" %}
We miss him.
diff --git a/content/posts/2017-05-25-from-launch-to-landing-how-nasa-took-control-of-its-https-mission.md b/content/posts/2017-05-25-from-launch-to-landing-how-nasa-took-control-of-its-https-mission.md
index 11b0fb41e..f600e5b1a 100644
--- a/content/posts/2017-05-25-from-launch-to-landing-how-nasa-took-control-of-its-https-mission.md
+++ b/content/posts/2017-05-25-from-launch-to-landing-how-nasa-took-control-of-its-https-mission.md
@@ -65,14 +65,14 @@ For NASA, tool selection began with delving into use of [`pshtt`](https://github
We also augmented reports to track targets longitudinally, monitoring for endpoints that disappeared or changed between scans. This sort of analysis was helpful for one-on-one troubleshooting, which the core team supported by offering spot check scans for system administrators that were unable to run `pshtt` independently. For these purposes, the agency core team maintained a troubleshooting branch off of the canonical `pshtt` master branch to support checks with multiple timeouts to account for many of NASA's high-latency targets, and to use an augmented trust store that included the Federal Common Policy CA.
diff --git a/content/posts/2017-05-30-the-new-fec.md b/content/posts/2017-05-30-the-new-fec.md
index 63f38bac1..88fa03e99 100644
--- a/content/posts/2017-05-30-the-new-fec.md
+++ b/content/posts/2017-05-30-the-new-fec.md
@@ -8,8 +8,6 @@ tags:
- agency work
- product launch
excerpt: "Last week, the Federal Election Commission (FEC) unveiled their new website at FEC.gov. This new site is the result of a years-long collaboration with GSA’s 18F and features completely revamped tools for exploring campaign finance data."
-image: /assets/blog/fec/0-herofecbig.png
-image_figcaption: "The previous and new FEC website designs"
---
Last week, the Federal Election Commission (FEC) unveiled their new website at [FEC.gov](https://www.fec.gov/). This new site is the result of a years-long collaboration with GSA’s 18F and features completely revamped tools for exploring campaign finance data. It provides user-centered content for understanding the reporting and compliance requirements for people participating in federal elections, redesigned tools for exploring legal resources, and more.
@@ -35,21 +33,21 @@ The first thing most visitors familiar with the old FEC.gov will notice is the c
When the [U.S. Web Design Standards](https://standards.usa.gov/) launched, we started using their components with the new FEC styles — even contributing back to the project as a use case for research on how to use the Standards with your own styles. Since the site is responsive, it looks great no matter what device you’re using. And whereas the old FEC.gov presented users with over ten different top-level navigation elements, the new FEC.gov reduces the primary navigation to three main items to reflect the three primary focus areas that users need when coming to the site.
The campaign finance data section has grown since the initial beta launch to include even more datasets — like the ability to get all raw data from electronic filings as soon as it comes in, right alongside processed data — and we redesigned major features like the candidate and committee profile pages based on user feedback.
The legal resources section allows users to search through multiple types of resources at once, which previously wasn’t possible. It also includes new ways to explore advisory opinions, which are the official Commission responses to questions about how federal campaign finance law applies to specific, factual situations.
@@ -57,7 +55,7 @@ The legal resources section allows users to search through multiple types of res
The help for candidates and committees section unifies content that previously lived across several sections and multiple PDFs into a single, user-centered set of pages, giving users one place to look for information.
@@ -70,14 +68,14 @@ We are now in a transition phase for FEC.gov. There is a new home page and major
### Pre-flip
### Post-flip, with hybrid transition pages
diff --git a/content/posts/2017-09-07-opening-the-nations-crime-data.md b/content/posts/2017-09-07-opening-the-nations-crime-data.md
index 9c933df6c..f3c8e3144 100644
--- a/content/posts/2017-09-07-opening-the-nations-crime-data.md
+++ b/content/posts/2017-09-07-opening-the-nations-crime-data.md
@@ -27,7 +27,7 @@ The UCR Program is one of the nation’s most sought after crime datasets, and,
Broadening access to this data helps people better understand crime in their communities. It also helps promote citizen engagement, improve resource allocation for communities, and will lead to more transparency and accountability within law enforcement agencies. Further, law enforcement can use this tool to benchmark their progress and see how reported crime rates compare across the nation.
-![Screen: Discovery Homepage]({{site.baseurl}}/assets/blog/fbi-crime-data/az-breakdown.gif)
+{% image "assets/blog/fbi-crime-data/az-breakdown.gif" "Screen: Discovery Homepage" %}
Specifically, users of the site can:
diff --git a/content/posts/2017-12-12-renata-maziarz-model-civil-servant.md b/content/posts/2017-12-12-renata-maziarz-model-civil-servant.md
index 3639755f3..f7cfd49d0 100644
--- a/content/posts/2017-12-12-renata-maziarz-model-civil-servant.md
+++ b/content/posts/2017-12-12-renata-maziarz-model-civil-servant.md
@@ -9,7 +9,7 @@ tags:
excerpt: "In the course of our engagements, we’ve had many amazing partners who have been practicing similar innovative techniques long before 18F existed, but usually in isolation. Today, we’re highlighting one of those amazing partners: Renata Maziarz, at the Bureau of Fiscal Service in the Department of the Treasury."
---
Although 18F talks a lot about technology, agile software development, and user-centered design, these aren’t the real products we’re selling. While these tools help, they’re the means and not the end. What 18F really seeks when working with a partner is sustained, organizational change that helps agencies deliver on their mission more effectively, whether that's through better technology and design practices, or some other way.
diff --git a/content/posts/2018-01-30-getting-prepared-to-prototype.md b/content/posts/2018-01-30-getting-prepared-to-prototype.md
index aac080775..34f335154 100644
--- a/content/posts/2018-01-30-getting-prepared-to-prototype.md
+++ b/content/posts/2018-01-30-getting-prepared-to-prototype.md
@@ -25,7 +25,7 @@ Here are a list of factors that governments should consider to become better pre
You can create prototypes in [many different forms](https://github.com/18F?utf8=%E2%9C%93&q=prototype), and you don’t necessarily have to [write software code](https://18f.gsa.gov/2015/01/06/protosketch/). You can use prototypes as a way to get feedback from real or anticipated users, or you can use them as a way to test hypotheses or validate technology choices.
@@ -46,7 +46,7 @@ Thinking clearly ahead of time about the reasons for building a prototype, and t
Through our work, we’ve learned firsthand that finding users to evaluate a prototype [can sometimes be a challenge](https://18f.gsa.gov/2017/11/08/four-lessons-we-learned-while-building-our-own-design-research-recruiting-tool/). Identifying users that can provide meaningful feedback and reaching out to recruit them can require multiple steps, and often prior approvals. As a general rule of thumb, the larger the call for feedback, the more hurdles you’ll have to overcome to identify and contact volunteers.
diff --git a/content/posts/2018-02-06-getting-partners-on-board-with-research-findings.md b/content/posts/2018-02-06-getting-partners-on-board-with-research-findings.md
index 97980f516..deffec450 100644
--- a/content/posts/2018-02-06-getting-partners-on-board-with-research-findings.md
+++ b/content/posts/2018-02-06-getting-partners-on-board-with-research-findings.md
@@ -28,7 +28,7 @@ After spending the first two weeks of a six-week project interviewing various us
Once our partners had bought into what we had seen and heard during our research, we asked them to prioritize the findings. This request left them a bit confused. “Aren’t _you_ supposed to tell us what the priorities should be?” they asked. We told them that while we certainly had an opinion on what the highest priority issues were, especially from a user-experience perspective, it was important for us to know what _their_ organizational priorities were.
We conducted this exercise using a very low-tech approach: writing findings on sticky notes, then asking the partner to put them into low-priority, medium-priority, and high-priority groups.
diff --git a/content/posts/2018-02-22-new-home-for-the-federal-plain-language-community.md b/content/posts/2018-02-22-new-home-for-the-federal-plain-language-community.md
index 73d723071..da2623478 100644
--- a/content/posts/2018-02-22-new-home-for-the-federal-plain-language-community.md
+++ b/content/posts/2018-02-22-new-home-for-the-federal-plain-language-community.md
@@ -17,7 +17,7 @@ redirect_from:
The Plain Language Action and Information Network (PLAIN) is one of the longest-standing champions for great content and user experience in government. Since the 90s, this incredible community has shepherded the adoption of plain language in federal regulations and communications with the public. Last year, we were honored to partner with them to update and redesign [plainlanguage.gov](https://www.plainlanguage.gov/).
diff --git a/content/posts/2018-04-05-ask-18f-form-design.md b/content/posts/2018-04-05-ask-18f-form-design.md
index 7cf74a78e..9bec6b3eb 100644
--- a/content/posts/2018-04-05-ask-18f-form-design.md
+++ b/content/posts/2018-04-05-ask-18f-form-design.md
@@ -51,7 +51,7 @@ You can also start off with a out-of-the-box solution like [Survey Monkey]( http
Here is an example of a form that applies principles like text alignment, grouping, and typography hierarchy.
#### Helpful links and examples:
diff --git a/content/posts/2018-10-16-exploring-a-new-way-to-make-eligibility-rules-easier-to-implement.md b/content/posts/2018-10-16-exploring-a-new-way-to-make-eligibility-rules-easier-to-implement.md
index 4e3fdc342..cfdea0e37 100644
--- a/content/posts/2018-10-16-exploring-a-new-way-to-make-eligibility-rules-easier-to-implement.md
+++ b/content/posts/2018-10-16-exploring-a-new-way-to-make-eligibility-rules-easier-to-implement.md
@@ -20,7 +20,7 @@ These programs are managed at the federal level, but administered at the state a
This translation of federal policy into many state systems, with many
technology partners in between, creates opportunities for implementation errors and represents significant duplicated effort, since most states (and territories, and sometimes each county and tribal organization) manage their own separate IT system(s) to run these programs.
-![Animation: describing the scale of the challenge. Text reads: Sometimes eligibility criteria for federal programs change. When this happens states review the changes, identify needed system changes to implement the policy, prioritize system changes against all their other work, turn policy into business requirements, and procure or conduct implementation work. Federal oversight of this progress happens all along. And after all the time, effort, and money, sometimes the process is a success, and sometimes it’s not. And this happens over and over, in every state, and every territory, and sometimes in tribal organizations as well.]({{site.baseurl}}/assets/blog/eligibility-rules-policy/rules-policy-review.gif)
+{% image "assets/blog/eligibility-rules-policy/rules-policy-review.gif" "Animation: describing the scale of the challenge. Text reads: Sometimes eligibility criteria for federal programs change. When this happens states review the changes, identify needed system changes to implement the policy, prioritize system changes against all their other work, turn policy into business requirements, and procure or conduct implementation work. Federal oversight of this progress happens all along. And after all the time, effort, and money, sometimes the process is a success, and sometimes it’s not. And this happens over and over, in every state, and every territory, and sometimes in tribal organizations as well." %}
Given all this duplicative effort and the [corresponding risk](https://www.standishgroup.com/sample_research_files/Haze4.pdf),
we got to thinking about opportunities for improvement.
@@ -32,7 +32,7 @@ In learning more about this problem, we thought to ourselves...
**What if a federal agency coded their program’s eligibility
criteria into a single, central** ***web service*** **that states could use to help determine eligibility?**
-![Animation: describing the eligibility rules service concept. Text reads: When someone applies to a program, their data is evaluated against eligibility criteria by a rules engine the state operates. Most states operate their own. Each state’s rules engine needs to change when the policies change how eligibility is determined. (This is where all the effort and risk comes in.) But there is a way that a single, central rules service could be accessed by many states so they wouldn’t have to manage their own. States would still have their own systems but the rules part would be handled by a central rules service which would be managed by the federal agency. The state systems would talk to the rules service over the internet using an application programming interface or API.]({{site.baseurl}}/assets/blog/eligibility-rules-policy/eligibility-process.gif)
+{% image "assets/blog/eligibility-rules-policy/eligibility-process.gif" "Animation: describing the eligibility rules service concept. Text reads: When someone applies to a program, their data is evaluated against eligibility criteria by a rules engine the state operates. Most states operate their own. Each state’s rules engine needs to change when the policies change how eligibility is determined. (This is where all the effort and risk comes in.) But there is a way that a single, central rules service could be accessed by many states so they wouldn’t have to manage their own. States would still have their own systems but the rules part would be handled by a central rules service which would be managed by the federal agency. The state systems would talk to the rules service over the internet using an application programming interface or API." %}
A web service is an application or data source that’s accessible over the internet. Web services communicate with other computer systems, not directly with users. They function behind-the-scenes to allow separate systems to work together.
diff --git a/content/posts/2018-10-23-two-exercises-for-improving-design-research-through-reflective-practice.md b/content/posts/2018-10-23-two-exercises-for-improving-design-research-through-reflective-practice.md
index ed6e22358..edda54551 100644
--- a/content/posts/2018-10-23-two-exercises-for-improving-design-research-through-reflective-practice.md
+++ b/content/posts/2018-10-23-two-exercises-for-improving-design-research-through-reflective-practice.md
@@ -164,7 +164,7 @@ describing research across various levels:
I also shared this local-maxima diagram I learned about from [Joshua Porter’s 52 Weeks of UX](http://52weeksofux.com/post/694598769/the-local-maximum).
-![Animation: local-maxima diagram showing the differences between your design and a better design]({{site.baseurl}}/assets/blog/design-research-reflective-practice/locmax.gif)
+{% image "assets/blog/design-research-reflective-practice/locmax.gif" "Animation: local-maxima diagram showing the differences between your design and a better design" %}
I explained that foundational research is useful for breaking out of
“local maximas” and understanding the landscape in which the team is
diff --git a/content/posts/2019-10-29-culture-climate-survey.md b/content/posts/2019-10-29-culture-climate-survey.md
index 32288c8c0..6479dffe3 100644
--- a/content/posts/2019-10-29-culture-climate-survey.md
+++ b/content/posts/2019-10-29-culture-climate-survey.md
@@ -80,7 +80,7 @@ others that showed where our culture needs improvement. Some questions
had dramatically positive results:
-![Chart - "It is easy to ask other members of this team for help"]({{site.baseurl}}/assets/blog/culture-climate-survey-2019/chart-easy-to-ask-for-help.svg)
+{% image "assets/blog/culture-climate-survey-2019/chart-easy-to-ask-for-help.svg" "Chart - "It is easy to ask other members of this team for help"" %}
@@ -112,7 +112,7 @@ had dramatically positive results:
-![Chart - "On this team, I can voice a contrary opinion without fear of negative consequences"]({{site.baseurl}}/assets/blog/culture-climate-survey-2019/chart-contrary-opinion.svg)
+{% image "assets/blog/culture-climate-survey-2019/chart-contrary-opinion.svg" "Chart - "On this team, I can voice a contrary opinion without fear of negative consequences"" %}
@@ -147,7 +147,7 @@ Other questions also showed strengths, but with more room for
improvement — trending at 5 instead of 7.
-![Chart - "I am satisfied with my work"]({{site.baseurl}}/assets/blog/culture-climate-survey-2019/chart-satisfied-with-my-work.svg)
+{% image "assets/blog/culture-climate-survey-2019/chart-satisfied-with-my-work.svg" "Chart - "I am satisfied with my work"" %}
@@ -182,7 +182,7 @@ improvement — trending at 5 instead of 7.
-![Chart - "I feel I am growing as an engineer"]({{site.baseurl}}/assets/blog/culture-climate-survey-2019/chart-growing-as-engineer.svg)
+{% image "assets/blog/culture-climate-survey-2019/chart-growing-as-engineer.svg" "Chart - "I feel I am growing as an engineer"" %}
diff --git a/content/posts/2019-12-3-long-term-teams.md b/content/posts/2019-12-3-long-term-teams.md
index c14febdcb..7b0ed9816 100644
--- a/content/posts/2019-12-3-long-term-teams.md
+++ b/content/posts/2019-12-3-long-term-teams.md
@@ -19,7 +19,7 @@ This particular grant is for a three-year period. How should you plan to allocat
In government, it wouldn't be uncommon to spend most of the grant upfront, paying a vendor to write the software, and then hand it off to an IT team for Operations and Maintenance, or O&M, post-launch:
-![Chart showing the trajectory of a software project that launches, goes through a flat "Operations and Maintenance" plateau, and then sunsets]({{site.baseurl}}/assets/blog/long-term-teams/o-and-m.png)
+{% image "assets/blog/long-term-teams/o-and-m.png" "Chart showing the trajectory of a software project that launches, goes through a flat "Operations and Maintenance" plateau, and then sunsets" %}
Although this is a common approach, it is a very risky one, because:
@@ -38,7 +38,7 @@ All of this learning should be documented along the way, in the form of user res
That said, if the ***entire*** team is disbanded in an abrupt handoff, a tremendous amount of knowledge is lost. All the context about decisions, user needs, stakeholders, and technical choices must be rebuilt from scratch. Anyone who has ever tried to pick up a job just from reading the notes of a predecessor knows how difficult this is and how much time it can waste!
-![Chart showing learning increasing over time, but then dropping sharply when an abrupt handoff happens]({{site.baseurl}}/assets/blog/long-term-teams/abrupt-handoff.png)
+{% image "assets/blog/long-term-teams/abrupt-handoff.png" "Chart showing learning increasing over time, but then dropping sharply when an abrupt handoff happens" %}
In knowledge work, this is a major loss. While team composition will naturally change over time, steady change is better than abrupt handoff to preserve team learning and context.
@@ -54,7 +54,7 @@ Instead of dividing your grant funding into "build" and "operation & maintenance
3. ***Ongoing Development ➡️ Sunset***: Nothing lasts forever, especially on the web. The last phase of a project is concerned with how to responsibly and thoughtfully shut it down and help users move to a better solution.
-![Chart of the three legs of the software creation process]({{site.baseurl}}/assets/blog/long-term-teams/happy-path.png)
+{% image "assets/blog/long-term-teams/happy-path.png" "Chart of the three legs of the software creation process" %}
Consider security. Security is a vital area of work at every stage. It can't ever be finished, since the external landscape changes all the time. A long-running engineering team has the benefit of understanding the product itself and a responsibility to keep it secure. In this scenario, teams can discover opportunities to improve the security, rather than spending all their time reactively. (See "[DevOps and Security on a Small Team](https://medium.com/nyc-planning-digital/devops-and-security-on-a-small-team-8709cfc5b0aa)" by TTS's own Aidan Feldman for a wonderful municipal example.)
@@ -74,7 +74,7 @@ The Open Forest effort explored potential partnerships with other internal gover
What advice does Aaron have for other agencies embarking on a similar agile journey? "Choose a low-risk option to build your pilot. We didn't choose a complex permitting process to start. Starting small mitigates risk as you develop new services, and allows you to identify capability and skill gaps."
-![GitHub commit graph showing ongoing techical development work]({{site.baseurl}}/assets/blog/long-term-teams/github-graph.png)
+{% image "assets/blog/long-term-teams/github-graph.png" "GitHub commit graph showing ongoing techical development work" %}
This screenshot of development work from the Open Forest GitHub repository shows sustained development over time. The Open Forest site launched in February — so the graph hints at ongoing improvement, iteration, and feature-building post launch!
diff --git a/content/posts/2020-05-12-rapid-implementation-of-policy-as-code.md b/content/posts/2020-05-12-rapid-implementation-of-policy-as-code.md
index dfa91ac6b..ea07e313c 100644
--- a/content/posts/2020-05-12-rapid-implementation-of-policy-as-code.md
+++ b/content/posts/2020-05-12-rapid-implementation-of-policy-as-code.md
@@ -40,7 +40,7 @@ In collaboration with policy experts at the federal level, we created an experim
We characterize this work as a [prototype](https://18f.gsa.gov/2018/01/30/getting-prepared-to-prototype/) because it’s meant to be a small and lightweight proof of concept. To visualize the kind of application that our eligibility API can power, we created a pre-screener:
-![GIF of Eligibility API Pre-Screener]({{site.baseurl}}/assets/blog/rapid-implementation-of-policy-as-code/prescreener-gif.gif)
+{% image "assets/blog/rapid-implementation-of-policy-as-code/prescreener-gif.gif" "GIF of Eligibility API Pre-Screener" %}
So far, our prototype has been focused on the financial aspects of SNAP eligibility. When SNAP’s eligibility policy changed in response to the current crisis, this provided an opportunity to test the value of our approach.
diff --git a/content/posts/2020-08-03-introducing-the-ux-guide.md b/content/posts/2020-08-03-introducing-the-ux-guide.md
index 8ff049d23..922a063bb 100644
--- a/content/posts/2020-08-03-introducing-the-ux-guide.md
+++ b/content/posts/2020-08-03-introducing-the-ux-guide.md
@@ -23,7 +23,7 @@ Most of us serve 2-to-4-year terms with 18F, which means people leave and join t
In creating this guide, we reflected on what the role of UX designer at 18F entails, what we choose to do in this role, and why.
-![Screenshot from a collaborative brainstorming session. Blue squares are responses contributed by 18F UX team members.]({{ site.baseurl }}/assets/blog/collaborative-brainstorming-session.png)
+{% image "assets/blog/collaborative-brainstorming-session.png" "Screenshot from a collaborative brainstorming session. Blue squares are responses contributed by 18F UX team members." %}
The resulting guide is a distillation of our perspectives on UX design in government—it documents effective approaches we’ve seen and describes how the 18F UX team works today and how we would like it to work in the future. The guide was developed collaboratively by our team and reflects the combined learnings, expertise, and contributions of many folks who have done UX work at 18F over the years.
diff --git a/content/posts/2020-12-14-a-dashboard-for-privacy-offices.md b/content/posts/2020-12-14-a-dashboard-for-privacy-offices.md
index 9c2c748f0..2579b4e25 100644
--- a/content/posts/2020-12-14-a-dashboard-for-privacy-offices.md
+++ b/content/posts/2020-12-14-a-dashboard-for-privacy-offices.md
@@ -18,7 +18,7 @@ Through work funded by [10x](https://10x.gsa.gov/), a team from 18F investigated
## The problem
-![Newspaper clip with the headline: "Huge C.I.A. operation reported in U.S. against antiwar forces, other dissidents in Nixon Years"]({{ site.baseurl }}/assets/blog/image1.png)
+{% image "assets/blog/image1.png" "Newspaper clip with the headline: "Huge C.I.A. operation reported in U.S. against antiwar forces, other dissidents in Nixon Years"" %}
The Privacy Act of 1974 was passed in the Watergate era, at a time when scandals involving the abuse of people’s privacy by the government were in the headlines. The new law required all federal government agencies to notify the public about any information systems (Systems of Records) they operate that contain personally identifiable information about individuals (the ‘Category of Records’ in the system).
@@ -38,7 +38,7 @@ Our first goal was to create a minimum viable product that our partners could us
In the end, we had something that looked like [this dashboard](http://cg-9341b8ea-025c-4fe2-aa6c-850edbebc499.app.cloud.gov/site/18f/privacy-dashboard/).
-![Gif of the PII inventory dashboard of a user looking for the term social security number]({{ site.baseurl }}/assets/blog/image2.gif)
+{% image "assets/blog/image2.gif" "Gif of the PII inventory dashboard of a user looking for the term social security number" %}
Our prototype was simple, but it immediately delivered impact for our partners. The dashboard saved them from having to resort to manual processes that take hours upon hours of their valuable time. It also increased their confidence in their analysis and reporting, which helped them answer questions and collaborate more effectively with other departments.
@@ -52,7 +52,7 @@ In the next phase, we want to take what we’ve learned from our initial partner
There are a few important things that we learned through building this prototype. First, it is important to meet partners where they are and give them tools that are immediately useful. It was important to us not to make life more difficult for GSA’s privacy office by making them learn a new tool. Instead, we made the decision to use Google Sheets as the backend for this prototype, which meant that our partners could make changes to the data behind the tool without our assistance.
-![Steps for data to go into dashboard: First a google sheet with backend data store and edit access is created, then updated in Github, and finally published though Federalist]({{ site.baseurl }}/assets/blog/image3.png)
+{% image "assets/blog/image3.png" "Steps for data to go into dashboard: First a google sheet with backend data store and edit access is created, then updated in Github, and finally published though Federalist" %}
Next, we learned that taking a ‘compliance hacking’ approach to building a prototype was an effective way to deliver a tool that our partners can continue to use after we leave. Because our technical stack is made of components that have already been given the Authority to Operate (ATO), our partners can continue to use the tool in their regular work without further investment. Though an ATO will be required for the version of this tool that we build at scale, this approach allowed us to provide real value to our partners first and prove that there is a demand for our tool before going through the ATO process.
diff --git a/content/posts/2021-03-02-using-agile-and-devops-to-get-better-results-than-a-change-control-board.md b/content/posts/2021-03-02-using-agile-and-devops-to-get-better-results-than-a-change-control-board.md
index 8b8a34091..2f449480e 100644
--- a/content/posts/2021-03-02-using-agile-and-devops-to-get-better-results-than-a-change-control-board.md
+++ b/content/posts/2021-03-02-using-agile-and-devops-to-get-better-results-than-a-change-control-board.md
@@ -63,7 +63,7 @@ To achieve these goals, we needed to understand the needs of various users and b
Below is an example roadmap from the project that shows how we broke up the problem into smaller pieces and prioritized. While this roadmap describes the features to be developed, an underlying backlog incorporated security, compliance and accessibility tasks to contextualize feature development.
-![Table labeled Thin Slice "first step" Features. It has three rows first, next and later. Each row has proposed functionality like "submit a complaint" and the functionality is color coded to show internal vs. external features]({{ site.baseurl }}/assets/blog/image2.png "Thin Slice \"First Step\" Features")
+{% image "assets/blog/image2.png" "Table labeled Thin Slice “first step” Features. It has three rows first, next and later. Each row has proposed functionality like “submit a complaint” and the functionality is color coded to show internal vs. external features" %}
Roadmaps are a great starting point but it is important to remember that they are not a list of requirements—the point of agile development is to make changes as you learn more about your users, problem space, and the other realities of your project. The relative importance of any particular feature may not be what you thought after you implement some and learn more about your needs.
@@ -131,11 +131,11 @@ The DOJ-18F team currently has automated tests for:
* Ensuring code is written and formatted to an industry standard
* Accessibility
-![Slide showing launch prep testing guidance]({{ site.baseurl }}/assets/blog/image3.png "Launch Test Prep Guide")
+{% image "assets/blog/image3.png" "Slide showing launch prep testing guidance" %}
Automated testing doesn't replace the need for people with context who approve new work, but it does reduce the risk of introducing errors or vulnerabilities. It can make sure certain bugs are not reintroduced, catch common security vulnerabilities, and accessibility errors.
-![Slide showing a launch prep automated testing and deployment pipeline, including: 1. PR Review, 2. Release QA, and 3. Production release]({{ site.baseurl }}/assets/blog/image1.png "Automated testing and deployment pipeline")
+{% image "assets/blog/image1.png" "Slide showing a launch prep automated testing and deployment pipeline, including: 1. PR Review, 2. Release QA, and 3. Production release" %}
### Step one, PR review:
diff --git a/content/posts/2021-03-31-18f-public-benefits-portfolio-reflects-on-the-last-year.md b/content/posts/2021-03-31-18f-public-benefits-portfolio-reflects-on-the-last-year.md
index 743d8fdf1..16c47ed02 100644
--- a/content/posts/2021-03-31-18f-public-benefits-portfolio-reflects-on-the-last-year.md
+++ b/content/posts/2021-03-31-18f-public-benefits-portfolio-reflects-on-the-last-year.md
@@ -37,7 +37,7 @@ After years of collaboration and coaching, in 2020 **we were able to wind down 1
Today, **our CMS partners have an established design research practice in place, and are successfully leading a full development team on their own**. Since 18F left, they have expanded the beta program to more states, and are making steady progress towards fully launching eAPD later this year. By bringing this product management capacity in-house, our CMS partners are now well-situated to lead other impactful digital services efforts themselves, and use these skills to better support their state partners in their efforts to improve their Medicaid systems as well.
-![A screenshot of the Alaska APD Home page. Showing the Summary budget by activity for FFY21]({{ site.baseurl }}/assets/blog/ak-apd-homepage.png "eAPD product (2021)")
+{% image "assets/blog/ak-apd-homepage.png" "A screenshot of the Alaska APD Home page. Showing the Summary budget by activity for FFY21" %}
We’ve leveraged human-centered design and research to take a product from concept to reality – and now we’ve shipped, tested, and are continuing to refine the eAPD to meet user needs and deliver value early and often. We aren’t done yet!
diff --git a/content/posts/2021-04-27-we_asked_our_coworkers_why_did_you_join_18f.md b/content/posts/2021-04-27-we_asked_our_coworkers_why_did_you_join_18f.md
index 89a326372..1b775fa76 100644
--- a/content/posts/2021-04-27-we_asked_our_coworkers_why_did_you_join_18f.md
+++ b/content/posts/2021-04-27-we_asked_our_coworkers_why_did_you_join_18f.md
@@ -33,133 +33,133 @@ Interested in joining our team? Check out open positions and how to apply [on th
[Back to the table of contents](#chapters)
-
+{% image_with_class "assets/blog/ponce_laura.png" "height-card-lg" "Laura Ponce (she/her) smiling confidently to the camera" %}
The 18F Methods site was my first impression of 18F. I was thrilled to learn more about the team within the federal government that is sharing user-centered design practices and putting everything out in the open for others to use. I wanted to be part of the organization that’s helping improve the user experience of government.
- Laura Ponce, UX Designer
-
+{% image_with_class "assets/blog/mike_gintz_headshot.jpg" "height-card-lg" "Mike Gintz (he/him) holding his really cute black dog smiling at the camera" %}
I wanted to spend my days doing mission-driven work that would help people, and in 18F I saw a recognition that even though technology is often where problems manifest, it isn’t necessarily where those problems originate. I was super excited about how 18F uses technology as a forcing function to have powerful and human conversations about communication, transparency, equity, trust, etc. — all the things that make for a functioning team (or government) — and I was like ‘I gotta be part of this!’ Still feel lucky to be here.
- Mike Gintz, Change Strategist
-
+{% image_with_class "assets/blog/peterson_ben.jpg" "height-card-lg" "Ben Peterson (he/him) wearing a cap smiling at the camera" %}
I was drawn to 18F because I wanted to help make sure the government validates that the things it wants to create are the things that will help the public, by asking the public about it.
- Ben Peterson, UX Designer
-
+{% image_with_class "assets/blog/18f-logo-l.png" "height-card-lg" "No image available, instead we used the 18F logo" %}
There’s a lot of talk in the tech sector about ‘making the world a better place,’ but there are few arenas of social and civic life more capable of meaningful change than government. I work at 18F because successfully delivering on the mission, and at the scale of government, is crucial to the health and well-being of our democracy and our communities. And when you work at 18F, you get to work with some of the smartest, most dedicated public servants you’ll ever find.
- Ryan Johnson, Content Strategist
-
+{% image_with_class "assets/blog/strenio_erin.jpg" "height-card-lg" "Erin Strenio (she/her) smiling at the camera" %}
“I had worked in journalism and start-ups, mostly in the food space, but was craving something more, and felt a calling to be more civically engaged. I never really pictured myself working in government, but when I found out about 18F—wait, they have a team dedicated to making government services easier for people to use and understand?—I wanted to be a part of it, and have felt grateful to work with such a passionate, dedicated group of public servants ever since.”
- Erin Zimmer Strenio, Content Strategist
-
+{% image_with_class "assets/blog/strothman_julie.jpg" "height-card-lg" "Julie Strothman (she/her) smiling calmly at the camera" %}
I wanted my design work to focus on increasing equity for people, and I’d seen 18F make government services more accessible and share their work so people could build off of it. I was drawn to 18F’s humility in the way they describe their work, and their deep commitment to user-centered design. Those impressions proved true: I found a place I really want to bring my energy.
- Julie Strothman, UX Designer
-
+{% image_with_class "assets/blog/jeff-durland.jpg" "height-card-lg" "Jeff Durland (he/him) looking confident as he poses to the camera" %}
I had long wanted to work in public service in some way, but never thought there was a place for me in government. When I learned about 18F, I thought ‘Here’s my chance! A government organization that does real user-centered design and cares deeply about delivering for the American people.’ It’s a privilege to make government interactions easier for the public — and for public servants.
- Jeff Durland, Content Strategist
-
+{% image_with_class "assets/blog/mattdobson2.jpg" "height-card-lg" "Matt Dobson (he/him) smiling happily at the camera" %}
I’d been paying attention to 18F for a few years and saw a lot of parallels between the work in government and the digital transformation work I was part of inside a large health insurance company. I loved the idea of working directly with partners to teach and empower them to thrive on their own. I thought joining 18F would be a great opportunity to do the kind of work I was already doing, in a place where I could make some meaningful impact. I’m really grateful to have the opportunity to be a part of this team and to help improve the way technology helps America.
- Matt Dobson, UX Designer
-
+{% image_with_class "assets/blog/pham_jacklynn.jpg" "height-card-lg" "Jacklynn Pham (she/her) smiling confidently at the camera" %}
I believe that design is impactful and can change people’s lives. So, I wanted to spend my time and use my skills to make services better for those who need it. I joined 18F because I believe in the work that’s done here.
- Jacklynn Pham, UX Designer
-
+{% image_with_class "assets/blog/korenfeld_igor.jpg" "height-card-lg" "Black and white picture of Igor Korenfeld (he/him) smiling calmly at the camera" %}
I wanted to join 18F because it was a place where I could work on improving the interface between the government and the public - to ease people’s access to public services, remove barriers and frustrations, and to increase trust in the government.”
- Igor Korenfeld, Product Designer
-
+{% image_with_class "assets/blog/lindpaintner_julia.png" "height-card-lg" "Julia Lindpainter (she/her) smiling confidently at the camera" %}
I enjoyed my work at past jobs, but at the end of the day I didn’t always feel that I was contributing to something I truly believed in. I wanted to join 18F because I felt confident that while the work might be hard (and it is!), I would know that it matters and I’d be doing it alongside incredible colleagues who are committed to making a difference.
- Julia Lindpaintner, Product Designer
-
+{% image_with_class "assets/blog/carpenter_malaika.jpeg" "height-card-lg" "Malaika Carpenter (she/her) smiling confidently at the camera" %}
“When two people, who are now my colleagues at 18F, excitedly told me about this organization, I was truly surprised that it existed in government. In my previous roles at other organizations, I was a lone content strategist, pushing teams to communicate in innovative ways for better impact. I joined 18F to be a part of a supportive group of content and UX professionals who are committed to doing the same within government for greater social impact.”
- Malaika Carpenter, Content Strategist
-
+{% image_with_class "assets/blog/rago_michelle.jpg" "height-card-lg" "Michelle Rago (she/her) smiles confidently to the camera" %}
I came to 18F from another agency. I was looking for a mission-driven organization where I could learn, grow, and contribute to making government work better for everyone. I am so grateful to be working alongside the smart, kind, and curious people of 18F!
- Michelle Rago, Content Strategist
-
+{% image_with_class "assets/blog/18f-logo-l.png" "height-card-lg" "No image available, instead we used the 18F logo" %}
I read the The Color of Law when it was first published. Between that book and my formative experience as a technologist in rural parts of the country, I developed a better lens for the divergence in experiences many people have with government. It motivated me to leverage my skills to design impact at scale. I don’t have any illusions that I alone can remedy decades of harm and distrust, but I believe we have an obligation to use the tools we have at our disposal to improve systems and services rapidly.
- Ron Bronson, Content Strategist
-
+{% image_with_class "assets/blog/princessojiaku.jpg" "height-card-lg" "Princess Ojiaku confidently looking at the distance away from the camera" %}
I care deeply about making information easier for the public to understand, access, and use to make decisions. I was working toward those aims as a journalist and a technologist when I learned about 18F. I had no idea that there was a government agency working on that as well! I joined 18F to help build public access and understanding so that the government can move closer to the ideal state – serving its entire public well.
- Princess Ojiaku, Content Strategist
-
+{% image_with_class "assets/blog/oskow_aviva.jpg" "height-card-lg" "Aviva Oskow holding her head using her hand as she looks away from the camera" %}
I joined 18F back in 2016 after searching for a way to combine my visual design skills with human-centered design—something that most design agencies, even those which are focused on doing good, didn’t make space for or prioritize at the time. While I had succeeded in using design to help political and social/environmental campaigns and organizations, I wanted a more hands-on role in channeling the needs of the people—facilitating the whole process, instead of only making it look nice at the end. I found that and so much more at 18F, getting to work on projects with impact I couldn’t even imagine at the time.
- Aviva Oskow, Product Designer
-
+{% image_with_class "assets/blog/austin_avatar.jpg" "height-card-lg" "Austin Hernandez (he/him) smiling happily at the camera" %}
I joined 18F because I came to a fork in my long career in the private sector: Should I use my design and research experience to increase profits for shareholders, or should I try to address inequities in access to government services? It wasn’t a difficult choice. Projects I’ve worked on are used by millions of people and decisions we’ve made can drastically change outcomes for the public. Big structural change is slow, but I am here to serve as an advocate for my community and make sure people who are impacted by problems are included in the solutions.
- Austin Hernandez, Product Designer
-
+{% image_with_class "assets/blog/luetger_dave.jpg" "height-card-lg" "Dave Luetger (he/him) looks seriously away from the camera" %}
I started working in government tech in 2016 and quickly became a fan of 18F from a distance. Government tech should (and can) be inclusive and easy to use. In 2020, I made the leap because I wanted to work on projects that affected programs that served the public more directly. I was also drawn to 18F’s warm people, structure, culture of empathy, inclusiveness, and growth.
- Dave Luetger, UX Designer
-
+{% image_with_class "assets/blog/annepetersen.jpg" "height-card-lg" "Anne Petersen (they/them) smiling confidently to the camera" %}
I joined 18F because 18F has an incredible, practical model of change: here, you can design with the public at scale to make their interactions with government easier for everyone, working alongside civil servants throughout the rest of government at all levels. The proportion and impact is immense, the timeline is both finite and generational, and while it can feel like an uphill climb, you can also see the progress you’re helping to make.
@@ -170,77 +170,77 @@ I joined 18F because 18F has an incredible, practical model of change: here, you
[Back to the table of contents](#chapters)
-
+{% image_with_class "assets/blog/18f-logo-l.png" "height-card-lg" "No image available, instead we used the 18F logo" %}
After a start in higher education and a detour into software engineering for the private sector, I wanted to get back to serving people. 18F is a great place to use the skills I had developed to make people’s lives better.
- Neil Martinsen-Burrell, Consulting Engineer
-
+{% image_with_class "assets/blog/chappen_eleni.jpeg" "height-card-lg" "Eleni Chappen (she/her) smiling proudly at the camera" %}
As I progressed in my engineering career, I became less motivated by solving purely technical problems and more motivated by greater missions and values. I wanted to work on problems worth solving, even if they’re harder and need solutions that engineering alone can’t provide
- Eleni Chappen, Consulting Engineer
-
+{% image_with_class "assets/blog/dunkman_andrew.jpg" "height-card-lg" "Andrew Dunkman (he/him) proudly looking at the camera" %}
After spending years working in the tech industry, I was at a crossroads trying to find a way to use the privileges afforded to me to help others. At about that time, I came across a bug in analytics.usa.gov and, noticing it was open source, I fixed the bug and it was patched in production within a few hours. What if all of government technology was like this? Now that was something I wanted to be a part of.
- Andrew Dunkman, Consulting Engineer
-
+{% image_with_class "assets/blog/matt_jadud.jpg" "height-card-lg" "Matt Jadud (he/him) smiling to the camera as he exits from a blue door" %}
I spent two decades as an educator. The work of an educator is a service paid forward to the next generation. It is the work of systemic change, one generation at a time. At 18F, our collaborations with colleagues across the federal government are the much needed systemic change for the people of this generation and the next. I'll get up and give my best self every day for that.
- Matt Jadud, Consulting Engineer
-
+{% image_with_class "assets/blog/carly-headshot.png" "height-card-lg" "Carly Jugler (she/her) smiling at the camera" %}
I always wanted to join the public sector but thought that if I did I would have to trade in my skills in modern software development for meaningful work. When I heard about 18F it sounded like a unicorn: a mission-driven organization that does meaningful work on difficult problems while using and advocating for agile and user-centered development
- Carly Jugler, Consulting Engineer
-
+{% image_with_class "assets/blog/edwin_torres.jpg" "height-card-lg" "Edwin Torres (he/him) proudly smiling at the camera" %}
While working on a Puerto Rico Department of Education project, I came across 18F and USDS. Their mission to create better technology services for the government inspired me and my team to create the new School Report Card for the island. Since then I followed the organization, and at the beginning of 2020 I found out that 18F was looking for engineers. Without thinking twice, I submitted my resume. Just meeting 18F team members during the interview process was enriching for me. I'm still surprised that I can contribute to improving the federal government and be part of this awesome team while living in Puerto Rico.
- Edwin Torres, Consulting Engineer
-
+{% image_with_class "assets/blog/tranovich_james.png" "height-card-lg" "James Tranovich (he/him) looking away from the camera smiling at something in the distance" %}
I worked in the private sector for many years, and quite honestly, I was not planning on working in the federal government. I interviewed with 18F on a whim and I'm so happy I did. I was struck during the interview by 18F's long-standing and clear commitment to cultural values, open source, public service, and its mission to transform digital work for the benefit of everyone in the United States. It has been a genuine joy to work with passionate and driven people and attempt to solve difficult problems in government collectively.
- James Tranovich, Consulting Engineer
-
+{% image_with_class "assets/blog/ryan_ahearn.jpg" "height-card-lg" "Ryan Ahearn (he/him) smiling happily at the camera" %}
I had been working at a series of startups with increasing societal impact, but felt like I could be doing more. The combination of teaching new processes and improving technology that 18F practices is the perfect match for me, and you can’t beat this opportunity to make a difference
- Ryan Ahearn, Consulting Engineer
-
+{% image_with_class "assets/blog/hofschneider_ryan.jpg.jpg" "height-card-lg" "Ryan Hofschneider (he/him) smiling confidently at the camera" %}
I wanted to help build systems that solve sticky issues, at scale, for the common good.
- Ryan Hofschneider, Consulting Engineer
-
+{% image_with_class "assets/blog/alex-soble.jpeg" "height-card-lg" "Alex Soble (he/him) smiling confidently at the camera" %}
Before 18F, I worked in and with local governments. I saw how approaches like human-centered design and working in the open could help us serve our public. I looked up to 18F as a part of government doing terrific work and writing on these topics. At the time that I applied to 18F, I was freelancing, and although I had wonderful clients, my health insurance options weren’t matching my healthcare needs. I applied to 18F as a job that would let me serve the public, while also offering the health insurance I needed. Since joining, I have been lucky enough to work on projects related to healthcare access, as well as transportation and public benefits.
- Alex Soble, Consulting Engineer
-
+{% image_with_class "assets/blog/18f-logo-l.png" "height-card-lg" "No image available, instead we used the 18F logo" %}
Prior to 18F, I was a federal civil servant in another agency, happily building products to (hopefully) make disaster response better for the people we serve. 18F was attractive to me as a software development shop using all the “modern” techniques and tools. 18F has actually been a place full of passionate public servants using a broad range of well-established practices and tools to help other agencies adopt good, successful software development practices, and it’s been a hugely rewarding experience to work here.
@@ -251,49 +251,49 @@ Prior to 18F, I was a federal civil servant in another agency, happily building
[Back to the table of contents](#chapters)
-
+{% image_with_class "assets/blog/colin_murphy_headshot.jpg" "height-card-lg" "Colin Murphy (he/him) confidently looking at the camera" %}
Mine is extremely selfish TBH. Early in my product career, I kept stumbling across 18F articles that clearly articulated definitions and methods for building technology. From then on my excitement continued and my admiration grew. 18F became my north star, knowing this is where I could learn how to be an amazing product manager.
- Colin Murphy, Product Manager
-
+{% image_with_class "assets/blog/theis-emily.png" "height-card-lg" "Emily Theis (she/her) smiling confidently at the camera" %}
My background is in journalism, so I’ve always valued work that is driven by informing and supporting the public. 18F’s agile-based model of partnering with lots of different agencies is also fun because you get to become a mini-expert as you work with new people and problems. The timing was important for me too: I joined in summer 2020, when moving toward public service felt particularly meaningful in a difficult year. I’m so proud to be at 18F!
- Emily Theis, Product Manager
-
+{% image_with_class "assets/blog/norman_allison.jpg" "height-card-lg" "Allison Norman (she/her) in a black and white picture smiling happily at the camera" %}
In the private sector, I worked to solve problems that just didn't feel like real problems (e.g. optimizing products to get another 0.01% of clicks), and it was starting to wear on me. I saw President Obama's keynote interview at SXSW Interactive in 2017, where he emphasized how solvable many real challenges are with technology. Obama encouraged SXSW attendees to consider applying their private sector experience to public service. I felt like he was speaking directly to me! And he was right, since joining 18F, I have been able to focus on working with agency partners to impact how the public engages with government digital products and services. The problems are real, they're worth solving, and it's a privilege to get to do this work every day.
- Allison Norman, Product Manager
-
+{% image_with_class "assets/blog/juneau-vogel_selena.jpg" "height-card-lg" "Selena Juneau-Vogel (she/her) staring confidently at the camera" %}
I’ve worked in service organizations for my whole career but I assumed the government, especially the federal government, was too monolithic and staid for me to grow or contribute. But when a friend pointed me to an 18F job posting, I was drawn in by the exciting language of human-centered design, open source, and product thinking. I’m so grateful to be in this community of diverse, talented, and driven changemakers who widen the cracks in the monolith to let the light in.
- Selena Juneau-Vogel, Product Manager
-
+{% image_with_class "assets/blog/roy_ayushi.jpeg" "height-card-lg" "Ayushi Roy (she/her) smiling confidently at the camera" %}
I’ve been a public servant for most of my career, though not always a technologist. When I was asked to help build out the Innovation Office for the City of Oakland, I learned 80% of what I knew by reading 18F’s guides and playbooks. I was blown away, became a huge fan of 18F and its values, and aspired to one day have the opportunity to serve the organization (and maybe even become a playbook-writer myself!). Perhaps it comes as no surprise then that I chose my birthday as the date on which to take the oath of office and start my first day on this dream job.
- Ayushi Roy, Product Manager
-
+{% image_with_class "assets/blog/patrick_kigongo.jpeg" "height-card-lg" "Patrick Kigongo (he/him) looking confidently at the camera with a bookcase behind him" %}
I’ve spent much of my career bouncing between nonprofits and the private sector. Despite living and working in D.C. for nearly a decade, I never worked in the federal government. I became a fan of 18F shortly after relocating to the west coast and in 2019 I arrived at a professional crossroads, and decided to redirect my energies towards public service. When I saw a job posting for an 18F product manager role in March 2020, I took it as a sign. Each day since I took my oath of office later that summer, I’ve been humbled by the brilliance and dedication of everyone in this organization.
- Patrick Kigongo, Product Manager
-
+{% image_with_class "assets/blog/18f-logo-l.png" "height-card-lg" "No image available, instead we used the 18F logo" %}
Joining 18F was a chance to apply my whole self to things that really matter — to unapologetically frame problems like a designer and solutions like an engineer, to be an individual contributor who occasionally gets lost in the big picture, to tackle challenges that come at me sideways.
@@ -304,14 +304,14 @@ Joining 18F was a chance to apply my whole self to things that really matter —
[Back to the table of contents](#chapters)
-
+{% image_with_class "assets/blog/hannah_kane.jpg" "height-card-lg" "Hannah Kane (she/her) smiling confidently at the camera" %}
I think there are many levers one can pull to make a meaningful contribution to society, but working in government has afforded me access to what feels like one of the most direct levers. It also helps that 18F is working on such exciting projects, and bringing proven human-centered and iterative processes to the work.
- Hannah Kane, Account Manager
-
+{% image_with_class "assets/blog/glenn.grieves.jpg" "height-card-lg" "Glenn Grieves (he/him) smiling happily at the camera" %}
After spending most of my career in the private sector (advertising and tech), it became clear to me that the user’s experience is everything. A customer’s only interaction with a brand may be through a website or an app, and great user experiences are an opportunity to secure customer loyalty and trust. To me, improving the user experience of government is the same idea. We have an opportunity to build trust and deliver for the American people - to solve problems that truly matter. I wanted to contribute.
@@ -322,7 +322,7 @@ After spending most of my career in the private sector (advertising and tech), i
[Back to the table of contents](#chapters)
-
+{% image_with_class "assets/blog/brouilette_alan.jpg" "height-card-lg" "Alan Brouilette (he/him) looking confidently away from the camera" %}
The magnitude of the problem 18F is trying to help solve. This problem won’t be solved in a generation, and I like challenges.
@@ -333,7 +333,7 @@ The magnitude of the problem 18F is trying to help solve. This problem won’t b
[Back to the table of contents](#chapters)
-
+{% image_with_class "assets/blog/miatta-myers.png" "height-card-lg" "Miatta Myers (she/her) smiling happily at the camera" %}
When I joined 18F, I had been in the federal acquisition field for over 10 years and I knew that the government’s traditional way of buying software was not working but I couldn’t figure out why. When I learned about 18F and its tech procurement innovations, I just knew I had to be a part of such a dedicated and passionate team that not only wants to help agencies provide better digital services but also strives to make procurement joyful! I am very proud of the work we do at 18F and our commitment to serve the public.
@@ -341,7 +341,7 @@ When I joined 18F, I had been in the federal acquisition field for over 10 years
-
+{% image_with_class "assets/blog/18f-logo-l.png" "height-card-lg" "No image available, instead we used the 18F logo" %}
I was a contracting officer for about 15 years before joining 18F. I was growing frustrated by the status quo and was interested in the idea of experimenting with new approaches to contracting for IT services. I also wanted to learn more about the digital services I was buying on behalf of my customers, and thought 18F would help me become a better buyer. It’s been a great experience and I love being able to work with other contracting officers that have similar interests in improving the nature of procurement. I’ve found the vast majority of procurement folks we’ve worked with are excited about the prospect of trying new approaches, and it’s led to better outcomes and helped expand the marketplace.
diff --git a/content/posts/2021-06-14-improving_the_way_the_u-s-_tax_court_engages_with_the_public.md b/content/posts/2021-06-14-improving_the_way_the_u-s-_tax_court_engages_with_the_public.md
index 7526f1bdf..f3696c471 100644
--- a/content/posts/2021-06-14-improving_the_way_the_u-s-_tax_court_engages_with_the_public.md
+++ b/content/posts/2021-06-14-improving_the_way_the_u-s-_tax_court_engages_with_the_public.md
@@ -30,7 +30,7 @@ The Court reached out to 18F to help write a solicitation for a new, open-source
18F conducted a three-day workshop with the Court to develop the [solicitation](https://github.com/ustaxcourt/case-management-rfq) that was descriptive of the kind of work to be done but not prescriptive about how to do it, allowing ongoing adjustments based on user research as to what features were developed. The solicitation leveraged a time-and-material (T&M) contract type with a not-to-exceed ceiling to achieve this flexibility. We then helped the Court conduct market research to identify qualified companies on [GSA Schedules](https://www.gsa.gov/buying-selling/purchasing-programs/gsa-schedule) and coached the Court’s evaluation team on [what to look](https://derisking-guide.18f.gov/federal-field-guide/deciding-what-to-buy/#evaluate-contractor-proposals-based-on-industry-best-practices) for in a qualified industry partner.
-![Screenshot of the US Tax Court's DAWSON case-management application"]({{ site.baseurl }}/assets/blog/ustc-header-image.png)
+{% image "assets/blog/ustc-header-image.png" "Screenshot of the US Tax Court's DAWSON case-management application" %}
The Court awarded the contract to an industry partner that brought strong software development and user-centered design skills to the project. All told, from the time the final solicitation was posted to the first commit of code, the process took 70 days.
diff --git a/content/posts/2021-07-27-the_tts_handbook_a_21st-century_approach_to_internal_documentation.md b/content/posts/2021-07-27-the_tts_handbook_a_21st-century_approach_to_internal_documentation.md
index 99d14228a..a065881a9 100644
--- a/content/posts/2021-07-27-the_tts_handbook_a_21st-century_approach_to_internal_documentation.md
+++ b/content/posts/2021-07-27-the_tts_handbook_a_21st-century_approach_to_internal_documentation.md
@@ -18,7 +18,7 @@ Nearly five years after its inception, we realized there haven’t been any blog
In a nutshell, the Handbook is our take on internal government documentation. It is an open, crowd-sourced, accessible, and living resource that aims to provide the information our team needs to do their work.
-![Screen capture of scrolling through the Handbook homepage, then clicking into the “TTS mission, history, and values]({{ site.baseurl }}/assets/blog/image4.gif "Screen capture of scrolling through the Handbook homepage")
+{% image "assets/blog/image4.gif" "Screen capture of scrolling through the Handbook homepage, then clicking into the “TTS mission, history, and values" %}
In this post, we’ll unpack the Handbook’s core values -- and how they’re implemented in practice. We’ll dive into our experience with the Handbook and even highlight some other organizations who’ve adopted it. Finally, we’ll touch on what’s in store for the project going forward. If you’re a federal employee, civic technologist, or member of the public, we hope to leave you with a sense of what 21st-century transparency in your government looks like.
@@ -48,7 +48,7 @@ The actual mechanism to make contributions was overly complicated. Some contribu
**Solution:** To remedy the overly-technical contribution process, we are adding support for [NetlifyCMS](https://www.netlifycms.org/) ([via cloud.gov Pages](https://federalist.18f.gov/documentation/getting-started-with-netlify-cms/)): an open-source content management system that will give our contributors a friendly UI and Git-free publishing workflow.
-![Demoing the contribution workflow in NetlifyCMS]({{ site.baseurl }}/assets/blog/netlify-workflow.gif "NetlifyCMS")
+{% image "assets/blog/netlify-workflow.gif" "Demoing the contribution workflow in NetlifyCMS" %}
### Reviewer ambiguity
@@ -56,7 +56,7 @@ Tethered to unclear ownership is an issue that crops up in the review process: r
**Solution:** To address the reviewer ambiguity, we made use of [GitHub’s “code owners” feature](https://docs.github.com/en/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github/about-code-owners). Our ownership assignments, from a content and code perspective, are maintained in a [CODEOWNERS file](https://github.com/18F/handbook/blob/main/CODEOWNERS). In this file, GitHub teams are assigned as “owners” of certain folders. Later, they are automatically added as reviewers to pull requests affecting their content.
-![By writing a CODOWNERS file, reviewers are automatically added to pull requests]({{ site.baseurl }}/assets/blog/code-owners-file.png "CODOWNERS file")
+{% image "assets/blog/code-owners-file.png" "By writing a CODOWNERS file, reviewers are automatically added to pull requests" %}
### Unclear governance
diff --git a/content/posts/2021-09-16-a_day_in_the_life_-_ingeniero_en_18f.md b/content/posts/2021-09-16-a_day_in_the_life_-_ingeniero_en_18f.md
index d0254ff24..11e997cb9 100644
--- a/content/posts/2021-09-16-a_day_in_the_life_-_ingeniero_en_18f.md
+++ b/content/posts/2021-09-16-a_day_in_the_life_-_ingeniero_en_18f.md
@@ -27,7 +27,7 @@ Sabemos que personas como tú, interesadas en 18F, tienen muchas preguntas y es
## Bienvenidos
-![Edwin (el) posa sonriendo en frente de su escritorio. El tiene piel blanca bronzeada y largo cabello negro. En su escritorio hay 5 monitores, uno se encuentra apagado, tres de ellos tienen la foto de un astronauta en el espacio, y el quinto el logo del GSA. En su escritorio tambien hay una taza de cafe con el logo de 18F, una decoracion de madera con la bandera de Puerto Rico, y un figurin del Mandalorian. A la par de su escritorio hay un estante con tres plantas verdes]({{ site.baseurl }}/assets/blog/edwin_gsa.jpg)
+{% image "assets/blog/edwin_gsa.jpg" "Edwin (el) posa sonriendo en frente de su escritorio. El tiene piel blanca bronzeada y largo cabello negro. En su escritorio hay 5 monitores, uno se encuentra apagado, tres de ellos tienen la foto de un astronauta en el espacio, y el quinto el logo del GSA. En su escritorio tambien hay una taza de cafe con el logo de 18F, una decoracion de madera con la bandera de Puerto Rico, y un figurin del Mandalorian. A la par de su escritorio hay un estante con tres plantas verdes" %}
¡Hola! Mi nombre es Edwin Torres. Soy ingeniero de software en 18F, una de las organizaciones de consultoría en tecnología y diseño más excepcionales del mundo, dado que está formada por empleados gubernamentales que trabajan como consultores para otras agencias del Gobierno. En otras palabras, 18F trabaja con otras agencias para mejorar la experiencia del usuario a la hora de acceder a servicios gubernamentales. 18F ayuda a estos otros grupos a desarrollar y adquirir tecnología.
diff --git a/content/posts/2021-09-28-a_day_in_the_life_of_an_18f_engineer.md b/content/posts/2021-09-28-a_day_in_the_life_of_an_18f_engineer.md
index 9f413d47c..0a75f432a 100644
--- a/content/posts/2021-09-28-a_day_in_the_life_of_an_18f_engineer.md
+++ b/content/posts/2021-09-28-a_day_in_the_life_of_an_18f_engineer.md
@@ -26,7 +26,7 @@ We know that potential bilingual candidates interested in 18F have many question
## Welcome
-![Edwin smiles at the camera crossing his arms. He has tan skin and long black hair. Behind him you can find his desk. There are four monitors on his desk. One is turned off, two have the image of an astronaut in space, and the fourth one has the GSA logo. On his desk there's also a mug with an 18F logo, a wooden ornament with the Puertorican flag, and a figurine of the Mandelorian. Next to his desk there's a shelf with green plants]({{ site.baseurl }}/assets/blog/edwin_gsa.jpg)
+{% image "assets/blog/edwin_gsa.jpg" "Edwin smiles at the camera crossing his arms. He has tan skin and long black hair. Behind him you can find his desk. There are four monitors on his desk. One is turned off, two have the image of an astronaut in space, and the fourth one has the GSA logo. On his desk there's also a mug with an 18F logo, a wooden ornament with the Puertorican flag, and a figurine of the Mandelorian. Next to his desk there's a shelf with green plants" %}
Hi there! My name is Edwin Torres. I am a software engineer at 18F, one of the most exceptional design and technology consulting organizations in the world. It’s made up of government employees who serve as consultants for other government agencies. In other words, 18F works with agencies to improve the user experience of government services by helping them build and buy technology.
diff --git a/content/posts/2021-10-19-navigating-atos.md b/content/posts/2021-10-19-navigating-atos.md
index 6be864bcc..895380d3f 100644
--- a/content/posts/2021-10-19-navigating-atos.md
+++ b/content/posts/2021-10-19-navigating-atos.md
@@ -36,7 +36,7 @@ In order to successfully work with security compliance teams to ship software in
## Architect systems anticipating the ATO process
-
+{% image "assets/blog/navigating-atos/example-boundary-diagram.png" "boundary diagram with lines describing the types of connections between entities such as an API and routers" %}
As you explore the requirements of your system, consider selecting an architectural foundation that allows you to inherit as many of the [NIST 800-53 controls](https://csrc.nist.gov/publications/detail/sp/800-53/rev-5/final) as possible from an existing provider or product. This can dramatically reduce the scope of work required for the ATO, reduce timelines, and improve overall system security.
@@ -88,7 +88,7 @@ You can still make changes and keep building and improving your system after its
## Embrace DevOps, continuous integration, and automated testing, while staying flexible on format
-
+{% image "assets/blog/navigating-atos/zap.png" "ZAP scanning report indicating several findings" %}
DevOps, continuous integration, automated testing, automated security scanning using open-source tools such as OWASP ZAP: all of these modern software development practices show your team’s commitment to rigorous testing of your system. Take the time to walk through the practices your team is employing, and show how these techniques test and verify the security of your system. If your development team is running a full suite of automated tests for correctness, security, and accessibility on every proposed code change, make sure your security compliance team knows this is happening and sees the benefits. You may need to be flexible on the format you use to share information about the testing you are doing. Taking the time to put results into a familiar format like Word, PDF, or an HTML page can go a long way.
diff --git a/content/posts/2021-10-21-the_weekly_ship.md b/content/posts/2021-10-21-the_weekly_ship.md
index ca816709f..0bf8906ef 100644
--- a/content/posts/2021-10-21-the_weekly_ship.md
+++ b/content/posts/2021-10-21-the_weekly_ship.md
@@ -8,7 +8,7 @@ tags:
excerpt: "The weekly ship has been a staple of 18F projects for years. It is a way to engage partners, inform teammates, and reflect on our work."
---
-![Photo of a ship at sunset]({{ site.baseurl }}/assets/blog/ship.jpeg "Photo of a ship at sunset")
+{% image "assets/blog/ship.jpeg" "Photo of a ship at sunset" %}
At 18F and its parent office Technology Transformation Services (TTS), we are committed to [working in the open](https://18f.gsa.gov/open-source-policy/). One way we do that with agency partners is through our "weekly ship" – a weekly memo that captures what we did that week, what’s upcoming, and how much we’ve spent on the project so far. We send weekly ships throughout the duration of a project. The weekly ship is a way we engage with our partners, but it’s also an internal ritual that promotes transparency by giving our co-workers project insight. At a glance, both our partners and anyone in TTS can understand the status of a project, the state of its funding, and where the project is heading.
diff --git a/content/posts/2022-01-21-what-have-you-learned-from-other-18F-designers.md b/content/posts/2022-01-21-what-have-you-learned-from-other-18F-designers.md
index 846e1dd7c..1c9e2d8bb 100644
--- a/content/posts/2022-01-21-what-have-you-learned-from-other-18F-designers.md
+++ b/content/posts/2022-01-21-what-have-you-learned-from-other-18F-designers.md
@@ -12,7 +12,7 @@ tags:
excerpt: "We asked 18F designers what they've learned from fellow designers while working together. Here's what they said."
---
-![Image of team brainstorming]({{ site.baseurl }}/assets/blog/team_brainstorming.png)
+{% image "assets/blog/team_brainstorming.png" "Image of team brainstorming" %}
Special thanks to designer Jia Gu for the images in this post
{: .font-alt-xs }
@@ -91,7 +91,7 @@ I learned from fellow UX designer Melissa Braxton how to foster relationships an
– Mark Trammell, UX designer
-![Image of woman thinking]({{ site.baseurl }}/assets/blog/woman_thinking.png)
+{% image "assets/blog/woman_thinking.png" "Image of woman thinking" %}
## On user research and facilitation
diff --git a/content/posts/2022-01-25-tech-talks.md b/content/posts/2022-01-25-tech-talks.md
index db68d205d..fd2387ecc 100644
--- a/content/posts/2022-01-25-tech-talks.md
+++ b/content/posts/2022-01-25-tech-talks.md
@@ -14,7 +14,7 @@ image_alt: "An older model computer whose screen reads 'Building Trust With Tech
---
-![An older model computer whose screen reads "Building Trust With Tech Talks"]({{ site.baseurl }}/assets/blog/tech-talks/building-trust.png)
+{% image "assets/blog/tech-talks/building-trust.png" "An older model computer whose screen reads “Building Trust With Tech Talks”" %}
Special thanks to Jessica Dussault for this image!
{: .font-alt-xs }
diff --git a/content/posts/2022-05-01-finding-post-award-balance-with-quality-assurance.md b/content/posts/2022-05-01-finding-post-award-balance-with-quality-assurance.md
index 29e56456f..50297c5a7 100644
--- a/content/posts/2022-05-01-finding-post-award-balance-with-quality-assurance.md
+++ b/content/posts/2022-05-01-finding-post-award-balance-with-quality-assurance.md
@@ -27,7 +27,7 @@ But first, let’s talk about QASPs.
## What is a Quality Assurance Surveillance Plan?
-
+{% image "assets/blog/finding-post-award-balance/loc-fdr-study.jpg" "Franklin Roosevelt inspects stamps with a magnifying glass" %}
Franklin Roosevelt may not have inspected vendor code, but if he did we imagine it would have looked something like this. Image source: Library of Congress
A Quality Assurance Surveillance Plan, or QASP, is a document used to evaluate the work a contractor does on behalf of a federal agency. A QASP contains a list of desired outcomes and a method to measure the outcome's success which both parties have agreed to: the federal agency by writing it and the contractor by accepting the contract.
diff --git a/content/posts/2022-07-13-content-design-ada.md b/content/posts/2022-07-13-content-design-ada.md
index 197533fe8..437ef5a44 100644
--- a/content/posts/2022-07-13-content-design-ada.md
+++ b/content/posts/2022-07-13-content-design-ada.md
@@ -45,7 +45,7 @@ With this in mind, we attempted to write clear and actionable content that would
Here are two examples of that direct communication:
-![Screenshot from revised service animals page with clear heading text, Service animals are and Service animals are not, followed by three bulleted lists for each written in plain language including service animals are dogs and any breed and any size of dog, and service animals are not required to be certified or go through a professional training program]({{ site.baseurl }}/assets/blog/content/ada-service-animals-1.png)
+{% image "assets/blog/content/ada-service-animals-1.png" "Screenshot from revised service animals page with clear heading text, Service animals are and Service animals are not, followed by three bulleted lists for each written in plain language including service animals are dogs and any breed and any size of dog, and service animals are not required to be certified or go through a professional training program" %}
## Writing for action _and_ flexibility
Returning to the product vision — the foundation for the ADA.gov content strategy — we wanted to _empower_ users to understand their rights and obligations under the ADA. To do that, we needed to tell users as clearly and directly as possible what the ADA requires. This is hard, because some definitions in the regulations are intentionally broad for purposes of flexibility.
@@ -67,7 +67,7 @@ This example helps illustrate how the law might apply in a specific situation—
### Collapse complexity
We didn’t want to force users to read content that isn't relevant to them, so when we included extra detail or definitions, we used accordions, or other collapsible design patterns.
-![Screenshot from revised service animals page that shows a heading with a plus sign that can be expanded to get more detail. The heading is phrased as a question, What does fundamentally alter mean? The screenshot is animated to show the heading being expanded to display the answer and closed again]({{ site.baseurl }}/assets/blog/content/ada-accordion.gif)
+{% image "assets/blog/content/ada-accordion.gif" "Screenshot from revised service animals page that shows a heading with a plus sign that can be expanded to get more detail. The heading is phrased as a question, What does fundamentally alter mean? The screenshot is animated to show the heading being expanded to display the answer and closed again" %}
This technique was useful for instances where we couldn’t sufficiently explain the ADA without defining a term in the law or regulations. It was also useful for examples and further explanations, such as the difference between service animals and emotional support animals.
diff --git a/content/posts/2022-08-10-18f-tech-sandwich.md b/content/posts/2022-08-10-18f-tech-sandwich.md
index 27d907aaf..4a9c9c8c0 100644
--- a/content/posts/2022-08-10-18f-tech-sandwich.md
+++ b/content/posts/2022-08-10-18f-tech-sandwich.md
@@ -16,15 +16,15 @@ We often talk about 18F Engineering as a technology shop, but that's too broad.
We combine a limited set of technologies to make our applications. To explain this, we'll use the metaphor of a sandwich shop.
-![An array of food vector drawings. For bread, a baguette and slice of white bread; for protein, poultry, t-bone steak, and a cube of tofu; for fillings, mustard, chili, and tomato]({{ site.baseurl }}/assets/blog/eng-sandwich/image2.png)
+{% image "assets/blog/eng-sandwich/image2.png" "An array of food vector drawings. For bread, a baguette and slice of white bread; for protein, poultry, t-bone steak, and a cube of tofu; for fillings, mustard, chili, and tomato" %}
## Bread: cloud-based application hosting
-![ ]({{ site.baseurl }}/assets/blog/eng-sandwich/image4.png)
+{% image "assets/blog/eng-sandwich/image4.png" "" %}
{: .float-left.padding-right-2.padding-bottom-2 }
Bread represents commercial or government cloud hosting options. We use cloud computing to be [agile and resilient](https://18f.gsa.gov/2019/02/07/the-cloud-is-not-a-virtue/) and so that we can integrate security with our development. We host several of our applications on a government cloud provider called [cloud.gov](http://cloud.gov) which [meets many compliance requirements](https://cloud.gov/docs/compliance/ato-process/). We also have experience using our partner agencies' commercial cloud providers.
## Protein: open-source programming languages
-![ ]({{ site.baseurl }}/assets/blog/eng-sandwich/image3.png)
+{% image "assets/blog/eng-sandwich/image3.png" "" %}
{: .float-left.padding-right-2.padding-bottom-2 }
The protein is what makes our sandwich tasty. These are the open-source programming languages with which we have experience. We use well-supported open source languages with active communities, which helps us to ensure security support, develop language-specific practices, and write reusable code. These days, we develop mostly in Python, Ruby, and JavaScript. We also have some experience developing with C# in the .NET Core ecosystem.
@@ -32,7 +32,7 @@ The protein is what makes our sandwich tasty. These are the open-source programm
Our commitment to open source languages and tools allows us to work in the open, and help ensure public input to our work.
## Fillings and condiments: features driven by user needs
-![graphic of a mustard and peppers]({{ site.baseurl }}/assets/blog/eng-sandwich/image5.png)
+{% image "assets/blog/eng-sandwich/image5.png" "graphic of a mustard and peppers" %}
{: .float-left.padding-right-2.padding-bottom-2 }
What really makes a sandwich great are the fillings and condiments that meet individual preference and taste. In our metaphor, they represent application features that are based on the user needs we have discovered through research. The most common features we implement are user interfaces that are specific to our partner agencies' needs. We often integrate authentication, authorization, and user management. We frequently connect to notification services to send email to users. Sometimes we build integrations to transfer data to existing systems.
diff --git a/content/posts/2022-08-18-senior-executives-part4.md b/content/posts/2022-08-18-senior-executives-part4.md
index 42f8e6bea..5398e5e03 100644
--- a/content/posts/2022-08-18-senior-executives-part4.md
+++ b/content/posts/2022-08-18-senior-executives-part4.md
@@ -18,7 +18,7 @@ Senior executives often have to make big decisions early because of the long bud
This diagram demonstrates how a product team and a champions group of senior executives might maintain these direct interactions ([see part 3]({{site.baseurl}}/2022/08/11/senior-executives-pt3/) for a definition of a product team and champions group):
-![Top to Bottom: The Product Team, shown as people icons, find patterns by conducting research with real users. The product team builds solutions by testing and validates the solution with real users. The product team discusses patterns, share demos, and outlines next steps every sprint with Policy SMEs, Champions, and Technology SMEs, shown as people icons below the Product Team. The champions are connected by dotted lines ending in arrows to Policy and Technology SMEs. The SMEs are connected to the Product Team by dotted lines with warning icons indicating their roles as helping to identify policy conflicts or inconsistencies.]({{ site.baseurl }}/assets/blog/content/example1-senior-executives-part4.png)
+{% image "assets/blog/content/example1-senior-executives-part4.png" "Top to Bottom: The Product Team, shown as people icons, find patterns by conducting research with real users. The product team builds solutions by testing and validates the solution with real users. The product team discusses patterns, share demos, and outlines next steps every sprint with Policy SMEs, Champions, and Technology SMEs, shown as people icons below the Product Team. The champions are connected by dotted lines ending in arrows to Policy and Technology SMEs. The SMEs are connected to the Product Team by dotted lines with warning icons indicating their roles as helping to identify policy conflicts or inconsistencies." %}
* **The product team** conducts user research regularly and leverages that information to direct all product decisions.
* **The champions** are updated every sprint (via [weekly ship emails](https://18f.gsa.gov/2021/10/21/the_weekly_ship/) and demos) and advise on the best path forward, given their knowledge of organizational enablers and risks.
diff --git a/content/posts/2022-09-12-creating-a-culture-of-innovation.md b/content/posts/2022-09-12-creating-a-culture-of-innovation.md
index 8a387d4bf..18eee9cc9 100644
--- a/content/posts/2022-09-12-creating-a-culture-of-innovation.md
+++ b/content/posts/2022-09-12-creating-a-culture-of-innovation.md
@@ -80,7 +80,7 @@ Groups we spoke to are working through this challenge by building a brand around
Regardless of what they decided to specialize in, something we heard echoed several times was: "you'll only be able to deliver value if you pick something that lets you focus enough to deliver and be successful."
-
+{% image "assets/blog/inno-labs/portfolio-scope.png" "A rectangular graphic in landscape orientation with a white background. On the left is a cluster of nine small and medium-sized circles in shades of blue, gray, and black. The cluster is above a line of text that says, Overly-broad portfolio. On the right is a cluster with a large dark blue circle and three smaller ones to its right; medium blue, black, and gray. The text below them reads, More narrow scope with a specialized focus. Between the two lines of text, a thin, dark arrow points to the right, indicating that one should aim for a more narrow, focused scope for better success." %}
### Moving from experimentation to delivery without adequate support
diff --git a/content/posts/2022-11-14-improving-inclusion-continuously-how-we-iterated-on-our-bot-to-promote-more-inclusive-and-thoughtful-language.md b/content/posts/2022-11-14-improving-inclusion-continuously-how-we-iterated-on-our-bot-to-promote-more-inclusive-and-thoughtful-language.md
index 42f46133e..ef8df9cad 100644
--- a/content/posts/2022-11-14-improving-inclusion-continuously-how-we-iterated-on-our-bot-to-promote-more-inclusive-and-thoughtful-language.md
+++ b/content/posts/2022-11-14-improving-inclusion-continuously-how-we-iterated-on-our-bot-to-promote-more-inclusive-and-thoughtful-language.md
@@ -26,7 +26,7 @@ chat’s Slackbot](https://18f.gsa.gov/2016/01/12/hacking-inclusion-by-customizi
auto-response: whenever it saw the word “guys,” it would respond and ask if the
person meant something else, such as “friends” or “y’all.”
-![A screenshot from Slack showing the legacy bot response. It is a message with the text "custom response" above it. It is from the user Slackbot and the message says, "Did you mean y'all?" It also includes a link with the text "What's this?"]({{site.baseurl}}/assets/blog/inclusion-bot/legacy-guys-bot.png)
+{% image "assets/blog/inclusion-bot/legacy-guys-bot.png" "A screenshot from Slack showing the legacy bot response. It is a message with the text “custom response” above it. It is from the user Slackbot and the message says, “Did you mean y'all?” It also includes a link with the text “What's this?”" %}
Telling the stories of our work through avenues such as our blog is an important
way we adhere to our core values like working in the open and scaling our impact
@@ -75,12 +75,12 @@ suggesting different language. To help with these concerns, we updated the bot
so that only the person who triggers it will see a response. The Inclusion Bot
also adds an emoji to the original statement, signifying that it has responded:
-![A screenshot taken from Slack. A user named Charlie Demonstrata, displaying pronouns as he/him and displaying their location as DC, says, "Hey guys! Just wanted to let you know this project was being grandfathered into the previous structure." This message has an emoji response of a waving hand. Beneath the message is a response from a user named Inclusion Bot. This message has the text "Only visible to you" above it, and says, "Hello! Our inclusive TTS culture is built one interaction at a time, and inclusive language is the foundation. This bot helps us practice our inclusive values here in TTS. Some of your message could be unintentionally non-inclusive. Here are some alternatives that might work better." It then suggests, "Instead of saying grandfathered, how about included retroactively?" and "Instead of saying guys, how about folks?" There is a button to the right that reads, "Why this suggestion?" At the bottom, there is small text that reads, "You can view the full list of words and phrases this bot watches for." The text is blue, indicating a link.]({{site.baseurl}}/assets/blog/inclusion-bot/bot-response.png)
+{% image "assets/blog/inclusion-bot/bot-response.png" "A screenshot taken from Slack. A user named Charlie Demonstrata, displaying pronouns as he/him and displaying their location as DC, says, “Hey guys! Just wanted to let you know this project was being grandfathered into the previous structure.” This message has an emoji response of a waving hand. Beneath the message is a response from a user named Inclusion Bot. This message has the text “Only visible to you” above it, and says, “Hello! Our inclusive TTS culture is built one interaction at a time, and inclusive language is the foundation. This bot helps us practice our inclusive values here in TTS. Some of your message could be unintentionally non-inclusive. Here are some alternatives that might work better.” It then suggests, “Instead of saying grandfathered, how about included retroactively?” and “Instead of saying guys, how about folks?” There is a button to the right that reads, “Why this suggestion?” At the bottom, there is small text that reads, “You can view the full list of words and phrases this bot watches for.” The text is blue, indicating a link." %}
Additionally, we added a button that users can click to get more information
about why the highlighted words or phrases can be problematic:
-![A screenshot of a Slack popup message. The header is an icon representing the bot Charlie, and the header text says "Inclusion Bot." The first paragraph reads, "'Guys' is commonly used to refer to groups of people, but it is a gendered pronoun. It can make people who do not identify as 'guys' feel excluded even if that's not the intent. Regardless of our cultural background or innocent intent, we recommend alternative language that makes it clear everyone is included in the conversation! Consider a word like 'y'all' or 'folks' instead!" The second paragraph reads, "'Grandfathered' arose from voter restrictions that prevented Black people from voting. We want to avoid slavery and racist oppression references." The third paragraph is small text that reads, "See our blog post for more information about this bot." The words "blog post" are blue, indicating a link.]({{site.baseurl}}/assets/blog/inclusion-bot/bot-info-popup.png)
+{% image "assets/blog/inclusion-bot/bot-info-popup.png" "A screenshot of a Slack popup message. The header is an icon representing the bot Charlie, and the header text says “Inclusion Bot.” The first paragraph reads, “'Guys' is commonly used to refer to groups of people, but it is a gendered pronoun. It can make people who do not identify as 'guys' feel excluded even if that's not the intent. Regardless of our cultural background or innocent intent, we recommend alternative language that makes it clear everyone is included in the conversation! Consider a word like 'y'all' or 'folks' instead!” The second paragraph reads, “'Grandfathered' arose from voter restrictions that prevented Black people from voting. We want to avoid slavery and racist oppression references.” The third paragraph is small text that reads, “See our blog post for more information about this bot.” The words “blog post” are blue, indicating a link." %}
## Why it matters to TTS
diff --git a/content/posts/2023-02-24-18f-checks-in-with-emily-read-and-the-usgs-water-resources-mission-area-projects.md b/content/posts/2023-02-24-18f-checks-in-with-emily-read-and-the-usgs-water-resources-mission-area-projects.md
index 2ad02f895..d46a5e51c 100644
--- a/content/posts/2023-02-24-18f-checks-in-with-emily-read-and-the-usgs-water-resources-mission-area-projects.md
+++ b/content/posts/2023-02-24-18f-checks-in-with-emily-read-and-the-usgs-water-resources-mission-area-projects.md
@@ -18,7 +18,7 @@ excerpt: >
_This is the second in a series of blog posts where 18F checks in with our partners throughout the government. Previously in this series: [18F Checks In With Jerome Lee and the eAPD Project](https://18f.gsa.gov/2022/11/29/18f-checks-in-with-jerome-lee-and-the-eapd-project/)._
-![USGS hydrologic technician Travis Gibson confirms Great Salt Lake water levels at the SaltAire gauge.]({{ site.baseurl }}/assets/blog/usgs-wma-checkin/20210722_150403.jpg)
+{% image "assets/blog/usgs-wma-checkin/20210722_150403.jpg" "USGS hydrologic technician Travis Gibson confirms Great Salt Lake water levels at the SaltAire gauge." %}
USGS hydrologic technician Travis Gibson confirms Great Salt Lake water levels at the SaltAire gauge. Source: [USGS Multimedia Gallery](https://www.usgs.gov/media/images/great-salt-lake-reaches-new-historic-low)
{: .font-alt-xs }
diff --git a/content/posts/2023-04-25-18f-checks-in-with-the-dawson-project-at-the-us-tax-court.md b/content/posts/2023-04-25-18f-checks-in-with-the-dawson-project-at-the-us-tax-court.md
index 9ce72afa5..7a5f71508 100644
--- a/content/posts/2023-04-25-18f-checks-in-with-the-dawson-project-at-the-us-tax-court.md
+++ b/content/posts/2023-04-25-18f-checks-in-with-the-dawson-project-at-the-us-tax-court.md
@@ -21,7 +21,7 @@ excerpt: >
_This is the third in a series of blog posts where 18F checks in with our partners throughout the government. Previously in this series: [18F Checks In With Emily Read and the USGS Water Resources Mission Area Projects](https://18f.gsa.gov/2023/02/24/18f-checks-in-with-emily-read-and-the-usgs-water-resources-mission-area-projects/)._
-![The U.S. Tax Court DAWSON electronic case file system's homepage]({{ site.baseurl }}/assets/blog/ustc-dawson-checkin/dawson-home.png)
+{% image "assets/blog/ustc-dawson-checkin/dawson-home.png" "The U.S. Tax Court DAWSON electronic case file system's homepage" %}
This is the current home page for DAWSON. The Tax Court’s electronic filing and case management system, launched in 2020, is named for the Court’s longest-serving judge, Howard A. Dawson, Jr. This system is entirely web-based and open source.
{: .font-alt-xs }
diff --git a/content/posts/2023-05-08-andrew-hyder-award.md b/content/posts/2023-05-08-andrew-hyder-award.md
index cdf100763..8ce91669d 100644
--- a/content/posts/2023-05-08-andrew-hyder-award.md
+++ b/content/posts/2023-05-08-andrew-hyder-award.md
@@ -14,7 +14,7 @@ TTS annually awards the Andrew Hyder Government Service Improvement Award to one
This award commemorates the life and work of Andrew Hyder, a consulting software engineer at 18F who tragically passed away in 2021. Andrew was a community organizer who brought together activists, technologists, community members, and others to improve the way that governments delivered services to those in need. Examples of his contributions can be found in these blog posts: [A dashboard for privacy offices](https://18f.gsa.gov/2020/12/15/a-dashboard-for-privacy-offices/) and [Forms Resource for Federalist Users](https://18f.gsa.gov/2020/02/18/forms-resource-federalist/).
-![Andrew Hyder speaking at Code for America]({{ site.baseurl }}/assets/blog/andrew-hyder-award-2023/andrew-hyder-photo.png)
+{% image "assets/blog/andrew-hyder-award-2023/andrew-hyder-photo.png" "Andrew Hyder speaking at Code for America" %}
"Feed the people" was Andrew’s well-known refrain, though it went beyond just nutritional benefits and programs like [GetCalFresh](https://www.getcalfresh.org/en/about). He challenged colleagues and partners to think about the true benefits and costs of our work, always seeing the connections from our keyboards to the lived experiences of people across the country.
@@ -22,7 +22,7 @@ It’s easy when you’re working at a high level to forget to pause, adjust, an
As we open the 2023 award nomination period to those in TTS internally, we’d like to recognize the work of 2022 honorees Jessica Dussault (18F) and Will Cahoe (10x).
-![Jess Dussault profile picture]({{ site.baseurl }}/assets/blog/andrew-hyder-award-2023/jess-dussault-hyder-award.png)
+{% image "assets/blog/andrew-hyder-award-2023/jess-dussault-hyder-award.png" "Jess Dussault profile picture" %}
**Jess** is fun-loving, sincere, hard-working, and dedicated, and she brings enthusiasm and energy to everything that she works on. In her time as a consulting software engineer at 18F, Jess has demonstrated a dedication and enthusiasm to improving government public service through her efforts on projects and contributions to TTS culture.
@@ -30,7 +30,7 @@ She worked on improving how the public learns about government services through
Jess shares new approaches to improving government service through her writings on 18F’s blog, the TTS Engineering Newsletter, every day in Slack, and in the numerous meetings, team meetings, and coffees that she partakes in.
-![Will Cahoe profile picture]({{ site.baseurl }}/assets/blog/andrew-hyder-award-2023/will-cahoe-hyder-award-photo.png)
+{% image "assets/blog/andrew-hyder-award-2023/will-cahoe-hyder-award-photo.png" "Will Cahoe profile picture" %}
In all of **Will**’s work, he embodies the enthusiasm, warmth, and dedication that so many of us remember as hallmarks of Andrew's work in TTS. Will began his federal career in the Peace Corps, and joined TTS soon after. From his first day at GSA, he has infused TTS with humor, kindness, appreciation and celebration of differences, and an immovable dedication to public service. Will's creativity and ingenuity surface in everything he does – from problem solving to public speaking. Nothing Will does is dull, and the federal government is a better place because of his inventiveness.
diff --git a/content/posts/2023-09-07-catching-up-with-the-tanf-data-portal-project.md b/content/posts/2023-09-07-catching-up-with-the-tanf-data-portal-project.md
index 64e6a398c..69a40748f 100644
--- a/content/posts/2023-09-07-catching-up-with-the-tanf-data-portal-project.md
+++ b/content/posts/2023-09-07-catching-up-with-the-tanf-data-portal-project.md
@@ -58,7 +58,7 @@ Designing the contract and the system the way we did — for OFA to have control
**Lauren Frohlich**: Yeah, there are some milestones we can definitely put on there.
-![A line chart showing the emotional highs and lows of the TANF product owner over 5 years. The highs include the contract getting awarded and getting the ATO, followed by the first 10 partners using the new system. Emotions are at their lowest at the planned 18F roll off, and integration challenges afterwards. The emotions are consistently high when onboarding partners is in full swing.]({{ site.baseurl }}/assets/blog/tanf-data-portal-catchup/TDP-checkin--emotion-chart.jpg "TANF product owner emotion chart")
+{% image "assets/blog/tanf-data-portal-catchup/TDP-checkin--emotion-chart.jpg" "A line chart showing the emotional highs and lows of the TANF product owner over 5 years. The highs include the contract getting awarded and getting the ATO, followed by the first 10 partners using the new system. Emotions are at their lowest at the planned 18F roll off, and integration challenges afterwards. The emotions are consistently high when onboarding partners is in full swing." %}
**Lauren Frohlich**: Getting to ATO, that was like a 7 out of 10. And, not to be too negative but there were definitely some low points. It started to turn up again after the integration challenges. Some high points were getting focused on feature parity with the old system and launching production.
diff --git a/content/posts/2023-09-21-18f-website-refresh.md b/content/posts/2023-09-21-18f-website-refresh.md
index 88a191575..4ddac19a0 100644
--- a/content/posts/2023-09-21-18f-website-refresh.md
+++ b/content/posts/2023-09-21-18f-website-refresh.md
@@ -37,7 +37,7 @@ Interviews with our leadership team also clarified current organizational priori
## We did just enough design
-![A collage showcasing three of the newly refreshed 18F website pages.]({{ site.baseurl }}/assets/blog/18f-website-refresh/refreshed-screenshot-collage.jpg "Refreshed website screenshot collage")
+{% image "assets/blog/18f-website-refresh/refreshed-screenshot-collage.jpg" "A collage showcasing three of the newly refreshed 18F website pages." %}
As one would expect with a site “refresh,” we kept the amount of design to a minimum.
@@ -59,7 +59,7 @@ Because the previous site also used the U.S. Web Design System (USWDS), translat
## Websites are living products
-![A ribbon cutting ceremony with the new 18F website in the background on a stage at GSA Headquarters.]({{ site.baseurl }}/assets/blog/18f-website-refresh/refreshed-website-ribbon-cutting.jpg "A ribbon-cutting ceremony celebrating the refreshed 18F Website")
+{% image "assets/blog/18f-website-refresh/refreshed-website-ribbon-cutting.jpg" "A ribbon cutting ceremony with the new 18F website in the background on a stage at GSA Headquarters." %}
That’s how we launched a new 18f.gsa.gov in the course of several weeks. It wasn’t a simple process, but it was a steady one thanks to clear goals, disciplined decisions, and good coordination.
diff --git a/content/posts/2024-01-12-andrew-hyder-award.md b/content/posts/2024-01-12-andrew-hyder-award.md
index 1c8b69664..2ceb2e094 100644
--- a/content/posts/2024-01-12-andrew-hyder-award.md
+++ b/content/posts/2024-01-12-andrew-hyder-award.md
@@ -11,7 +11,7 @@ excerpt: |
TTS is proud to present the 2023 Andrew Hyder Government Service Improvement Award to Lalitha Jonnalagadda. This is awarded annually to one or more federal employees who demonstrate both excellence in their work and a commitment to improving the public's experience with government.
-![Lalitha Jonnalagadda]({{ site.baseurl }}/assets/blog/andrew-hyder-2023/jonnalagadda.jpg)
+{% image "assets/blog/andrew-hyder-2023/jonnalagadda.jpg" "Lalitha Jonnalagadda" %}
Lalitha is a product manager at 18F. In her tenure at TTS, she has had the opportunity to collaborate with amazing federal teams through visioning, strategizing, coaching, delivering and launching digital products, most notably the [Department of Justice's civil rights portal](https://civilrights.justice.gov/). At 18F, Lalitha collaborated with and led teams in developing and coaching product management at FEMA, EPA, DOE, HHS' Office of Head Start and DOJ's OIP (for foia.gov).
@@ -25,6 +25,6 @@ Lalitha lives in Virginia with her husband and two boys. She is motivated to sol
This award commemorates the life and work of Andrew Hyder, a consulting software engineer at 18F who passed away in 2021. Andrew was a community organizer who brought together activists, technologists, community members, and others to improve the way that governments delivered services to those in need. Examples of his contributions can be found in these blog posts: [A dashboard for privacy offices](https://18f.gsa.gov/2020/12/15/a-dashboard-for-privacy-offices/) and [Forms Resource for Federalist Users](https://18f.gsa.gov/2020/02/18/forms-resource-federalist/).
-![Andrew Hyder speaking at Code for America]({{ site.baseurl }}/assets/blog/andrew-hyder-2023/hyder.png)
+{% image "assets/blog/andrew-hyder-2023/hyder.png" "Andrew Hyder speaking at Code for America" %}
"Feed the people" was Andrew's well-known refrain, though it went beyond just nutritional benefits and programs like [GetCalFresh](https://www.getcalfresh.org/en/about). He challenged colleagues and partners to think about the true benefits and costs of our work, always seeing the connections from our keyboards to the lived experiences of people across the country.