diff --git a/.circleci/config.yml b/.circleci/config.yml index f7eb03a804..06f1395370 100644 --- a/.circleci/config.yml +++ b/.circleci/config.yml @@ -1,8 +1,8 @@ version: 2.1 orbs: - hugo: circleci/hugo@0.5.2 - node: circleci/node@5.1.0 + hugo: circleci/hugo@1.3.1 + node: circleci/node@5.2.0 defaults: &defaults executor: @@ -32,7 +32,7 @@ jobs: root: . html-proofer: executor: - name: hugo/cibuilds + name: hugo/default steps: - attach_workspace: at: . diff --git a/.hugo-version b/.hugo-version index 36545ad338..6c92f6a46c 100644 --- a/.hugo-version +++ b/.hugo-version @@ -1 +1 @@ -0.92.0 +0.123.3 diff --git a/.nvmrc b/.nvmrc index 3c032078a4..2dbbe00e67 100644 --- a/.nvmrc +++ b/.nvmrc @@ -1 +1 @@ -18 +20.11.1 diff --git a/content/about/style-guide.md b/content/about/style-guide.md index d9319a3597..24b70fac1f 100644 --- a/content/about/style-guide.md +++ b/content/about/style-guide.md @@ -245,27 +245,27 @@ The overarching name of the site is Digital.gov. You may see references to "Digi ## Logos {{< accordion title="Expand for digital.gov logo images" icon="edit" >}} -{{< asset-img path="/img/digitalgov-logo.png" alt="" width="220" >}} -{{< asset-img path="/img/digitalgov-logo.svg" alt="" width="220" >}} -{{< asset-img path="/img/digitalgov-logo-small.png" alt="" width="100" >}} -{{< asset-img path="/img/digitalgov-logo-small.svg" alt="" width="100" >}} -{{< asset-img path="/img/digitalgov-logo-white.png" alt="" width="220" bg="dark" >}} -{{< asset-img path="/img/digitalgov-logo-white.svg" alt="" width="220" bg="dark" >}} -{{< asset-img path="/img/digitalgov-logo-small-white.png" alt="" width="100" bg="dark" >}} -{{< asset-img path="/img/digitalgov-logo-small-white.svg" alt="" width="100" bg="dark" >}} -{{< asset-img path="/img/digit-small-black.png" alt="" width="32" >}} -{{< asset-img path="/img/digit-small-black.svg" alt="" width="32" >}} -{{< asset-img path="/img/digit-small-white.png" alt="" width="32" bg="dark" >}} -{{< asset-img path="/img/digit-small-white.svg" alt="" width="32" bg="dark" >}} -{{< asset-img path="/img/digit-150.png" alt="" width="150" >}} -{{< asset-img path="/img/digit-100.png" alt="" width="100" >}} -{{< asset-img path="/img/digit-50.png" alt="" width="50" >}} -{{< asset-img path="/img/digit-25.png" alt="" width="25" >}} -{{< asset-img path="/img/digit-16.png" alt="" width="16" >}} -{{< asset-img path="/img/digit-light.png" alt="" width="100" bg="dark" >}} -{{< asset-img path="/img/digit-dark.png" alt="" width="100" >}} -{{< asset-img path="/img/digit-hi.png" alt="" width="100" >}} -{{< asset-img path="/img/digit-usa.png" alt="" width="100" >}} +{{< asset-img path="img/digitalgov-logo.png" alt="" width="220" >}} +{{< asset-img path="img/digitalgov-logo.svg" alt="" width="220" >}} +{{< asset-img path="img/digitalgov-logo-small.png" alt="" width="100" >}} +{{< asset-img path="img/digitalgov-logo-small.svg" alt="" width="100" >}} +{{< asset-img path="img/digitalgov-logo-white.png" alt="" width="220" bg="dark" >}} +{{< asset-img path="img/digitalgov-logo-white.svg" alt="" width="220" bg="dark" >}} +{{< asset-img path="img/digitalgov-logo-small-white.png" alt="" width="100" bg="dark" >}} +{{< asset-img path="img/digitalgov-logo-small-white.svg" alt="" width="100" bg="dark" >}} +{{< asset-img path="img/digit-small-black.png" alt="" width="32" >}} +{{< asset-img path="img/digit-small-black.svg" alt="" width="32" >}} +{{< asset-img path="img/digit-small-white.png" alt="" width="32" bg="dark" >}} +{{< asset-img path="img/digit-small-white.svg" alt="" width="32" bg="dark" >}} +{{< asset-img path="img/digit-150.png" alt="" width="150" >}} +{{< asset-img path="img/digit-100.png" alt="" width="100" >}} +{{< asset-img path="img/digit-50.png" alt="" width="50" >}} +{{< asset-img path="img/digit-25.png" alt="" width="25" >}} +{{< asset-img path="img/digit-16.png" alt="" width="16" >}} +{{< asset-img path="img/digit-light.png" alt="" width="100" bg="dark" >}} +{{< asset-img path="img/digit-dark.png" alt="" width="100" >}} +{{< asset-img path="img/digit-hi.png" alt="" width="100" >}} +{{< asset-img path="img/digit-usa.png" alt="" width="100" >}} {{< /accordion >}} ### Branded names and initialisms or acronyms for related services and programs: diff --git a/content/communities/communicators.md b/content/communities/communicators.md index befbdec2b9..2b882cb572 100644 --- a/content/communities/communicators.md +++ b/content/communities/communicators.md @@ -29,7 +29,7 @@ community_list: subscribe_email: "fcn-request@listserv.gsa.gov" subscribe_email_subject: "Join the Communicators Community" terms: "Government employees and contractors with an official .gov or .mil email are eligible to join." - members: 2,342 + members: 2,373 join_cop_button: "Communicators community members" # Controls how this page appears across the site diff --git a/content/communities/multilingual.md b/content/communities/multilingual.md index 687f799d6f..a59049cafd 100644 --- a/content/communities/multilingual.md +++ b/content/communities/multilingual.md @@ -42,7 +42,7 @@ community_list: subscribe_email: "fmwc-request@listserv.gsa.gov" subscribe_email_subject: "Join the Multilingual Community" terms: "Government employees and contractors with an official .gov or .mil email are eligible to join." - members: 700 + members: 702 join_cop_button: "Multilingual community members" kicker: "Join the Multilingual Community" diff --git a/content/communities/plain-language-community-of-practice.md b/content/communities/plain-language-community-of-practice.md index 9e9b7b3c4f..6faf6ce40b 100644 --- a/content/communities/plain-language-community-of-practice.md +++ b/content/communities/plain-language-community-of-practice.md @@ -45,7 +45,7 @@ community_list: subscribe_email: "pl-cop-main-request@listserv.gsa.gov" subscribe_email_subject: "Join the Plain Language Community" terms: "Government employees and contractors with an official .gov or .mil email are eligible to join." - members: 2,135 + members: 2,149 join_cop_button: "Plain Language community members" kicker: "Join the Plain Language Community" diff --git a/content/communities/social-media.md b/content/communities/social-media.md index 38ea15e137..8f2a560e3a 100644 --- a/content/communities/social-media.md +++ b/content/communities/social-media.md @@ -36,7 +36,7 @@ community_list: subscribe_email: "sm-cop-request@listserv.gsa.gov" subscribe_email_subject: "Join the Social Media Community" terms: "Government employees and contractors with an official .gov or .mil email are eligible to join." - members: 1,432 + members: 1,462 join_cop_button: "Social Media community members" kicker: "Join the Social Media Community" diff --git a/content/communities/user-experience.md b/content/communities/user-experience.md index 443ac65f9e..bb24725075 100644 --- a/content/communities/user-experience.md +++ b/content/communities/user-experience.md @@ -35,7 +35,7 @@ community_list: subscribe_email: "ux-cop-request@listserv.gsa.gov" subscribe_email_subject: "Join the User Experience Community" terms: "Government employees and contractors with an official .gov or .mil email are eligible to join." - members: 2,142 + members: 2,163 join_cop_button: "User Experience community members" # see all authors at https://digital.gov/authors diff --git a/content/communities/web-analytics-and-optimization.md b/content/communities/web-analytics-and-optimization.md index 2f8dd016a5..49ab2544dd 100644 --- a/content/communities/web-analytics-and-optimization.md +++ b/content/communities/web-analytics-and-optimization.md @@ -42,7 +42,7 @@ community_list: subscribe_email: "analyze-optimize-request@listserv.gsa.gov" subscribe_email_subject: "Join the Web Analytics Community" terms: "Government employees and contractors with an official .gov or .mil email are eligible to join." - members: 955 + members: 981 join_cop_button: "Web Analytic community members" kicker: "Join the Web Analytics Community" diff --git a/content/communities/web-managers-forum.md b/content/communities/web-managers-forum.md index 970f28b5b4..2197fafefd 100644 --- a/content/communities/web-managers-forum.md +++ b/content/communities/web-managers-forum.md @@ -46,7 +46,7 @@ community_list: subscribe_email: "content-managers-l-request@listserv.gsa.gov" subscribe_email_subject: "Join the Web Managers Community" terms: "Government employees and contractors with an official .gov or .mil email are eligible to join." - members: 2,059 + members: 2,084 join_cop_button: "Web Manager community members" primary_image: "white-on-gsa-blue-digital-gov-card-community" diff --git a/content/events/2024/02/2024-02-27-spring-2024-community-summit.md b/content/events/2024/02/2024-02-27-spring-2024-community-summit.md deleted file mode 100644 index 1f80cf25a1..0000000000 --- a/content/events/2024/02/2024-02-27-spring-2024-community-summit.md +++ /dev/null @@ -1,62 +0,0 @@ ---- -title: Spring 2024 Community Summit -deck: Delivering a digital-first public experience -kicker: Annual Gathering -summary: Digital service experts across the federal government will share case studies and best practices on delivering a digital-first public experience. - -event_organizer: Digital.gov -cop_events: "" - -registration_url: https://gsa.zoomgov.com/webinar/register/WN_fS46iSeTSG6ww_VNpzUPeQ - -slug: spring-2024-community-summit - -# See all topics at https://digital.gov/topics -topics: - - design - - user-centered-design - - analytics - - user-experience - - accessibility - - multilingual - - best-practices - - communication - - content-strategy - - plain-language - - customer-experience - - product-and-project-management - - research - - trust - - social-media - - usability - - search-engine-optimization - -date: 2024-03-13 10:00:00 -0500 -end_date: 2024-03-13 16:00:00 -0500 - -# zoom, youtube_live, adobe_connect, google -event_platform: zoom - ---- - -On March 13, 2024, the Digital.gov Spring Community Summit will bring together web and digital service practitioners to talk about the many facets of delivering a digital-first public experience. - -Join us for a day of inspiration and collaboration as leading voices across government agencies share stories of innovation and excellence in every phase of the digital project journey. Topics include: - -* Recruiting the right talent -* Uncovering impactful solutions -* Crafting quality content -* Navigating seamless acquisitions -* Closing out projects with impact - -This is your chance to: - -* Uncover approaches to building accessibility into every step of the process. -* Gain practical insights from case studies and real-world experiences. -* Witness the forefront of thought leadership during panel discussions. - -**This event is best suited for:** Anyone and everyone invested in advancing federal digital services. - -The summit is virtual. There will be a short break after each session, and a 1-hour break at 12 pm ET. Reserve your virtual seat today! - -Agenda to follow. diff --git a/content/events/2024/03/2024-02-27-spring-2024-community-summit.md b/content/events/2024/03/2024-02-27-spring-2024-community-summit.md new file mode 100644 index 0000000000..cf2026e500 --- /dev/null +++ b/content/events/2024/03/2024-02-27-spring-2024-community-summit.md @@ -0,0 +1,225 @@ +--- +title: Spring 2024 Community Summit +deck: Delivering a digital-first public experience +kicker: Annual Gathering +summary: Digital service experts across the federal government will share case studies and best practices on delivering a digital-first public experience. + +event_organizer: Digital.gov +cop_events: "" + +registration_url: https://gsa.zoomgov.com/webinar/register/WN_fS46iSeTSG6ww_VNpzUPeQ + +slug: spring-2024-community-summit + +# See all topics at https://digital.gov/topics +topics: + - digital-service-delivery + - acquisition + - design + - user-centered-design + - analytics + - user-experience + - accessibility + - multilingual + - best-practices + - communication + - content-strategy + - plain-language + - customer-experience + - product-and-project-management + - research + - trust + - social-media + - usability + - search-engine-optimization + +date: 2024-03-13 10:00:00 -0500 +end_date: 2024-03-13 16:00:00 -0500 + +# zoom, youtube_live, adobe_connect, google +event_platform: zoom + +primary_image: "spring-2024-community-title-card" + +--- + +On March 13, 2024, the Digital.gov Spring Community Summit will bring together web and digital service practitioners to talk about the many facets of delivering a digital-first public experience. Federal Chief Information Officer, [Clare Martorana](https://www.cio.gov/about/members-and-leadership/martorana-clare/), will deliver the opening keynote. + +Join us for a day of inspiration and collaboration as leading voices across 16 U.S. federal government agencies share stories of innovation and excellence in every phase of the digital project journey. Topics include: + +* Recruiting the right talent +* Uncovering impactful solutions +* Crafting quality content +* Navigating seamless acquisitions +* Figuring out what to do after launch + +This is your chance to: + +* Uncover approaches to building accessibility into every step of the process. +* Gain practical insights from case studies and real-world experiences. +* Witness the forefront of thought leadership during panel discussions. + +**This event is best suited for:** Anyone and everyone invested in advancing federal digital services. + +The summit is virtual. There will be a short break after each session, and a 1-hour break at 12 pm ET. Reserve your virtual seat today! + +The event agenda below includes the speakers, agencies, and descriptions for all sessions. + +## Agenda + +### 10:00 am - 10:10 am, ET + +{{< img-right src="250-eop-omb-executive-office-president-office-management-budget" >}} + +Opening keynote with [Clare Martorana](https://www.cio.gov/about/members-and-leadership/martorana-clare/), Federal Chief Information Officer, OMB + +--- + +### 10:10 am - 11:00 am, ET + +**Session 1, Standing up a digital team** + +Hear from a panel of experts on making the case for building a digital team with strategies for success. You’ll learn what digital teams look like across the federal government, the skill sets successful digital teams possess, innovative hiring strategies, and much more. + +**Speakers** + +* **Jacquelyn Dolezal Morales** — Digital Communications Specialist, IAF +* **Lindsay Goldstein** — Digital Services Specialist, Office of Natural Resources Revenue, DOI +* **Robert Jolly** — Product Manager, 10x, GSA +* **Vicki McFadden** — Product Manager, Service Delivery Team, GSA +* **Gregory Your** — Director of Website Management, USAID + + + + + + + + + + + +
Seal of the Inter-American Foundation, IAF.The logo for the Department of the Interior's Office of Natural Resources Revenue is in shades of blues, greens, and white.The square 10x logo has the number 10 in white and the lowercase x in purple, on a dark background.The GSA logo in white, at the bottom of a blue square.Seal for the United States Agency for International Development, USAID.
+ +--- + +### 11:10 am - 12:00 pm, ET + +**Session 2, Uncovering impactful solutions through user research and technical discovery** + +In this session, a panel of experts will share insights, methods, and strategies for leveraging user research to drive innovation in digital service delivery. You’ll learn the different types of user-centered research and design techniques, ways to identify technical and security risks, and best practices for inclusive and ethical research. + +**Speakers** + +* **Kristen Lohman** — Design Strategist, Service Delivery Team, GSA +* **Beth A. Martin** — Digital Services Expert (UX Designer), OPM +* **Mark Meyer** — Software Developer, Digital Service Team, GSA +* **Christopher Patten** — Human-Centered Designer, DHS +* **Martha Wilkes** — Lead Accessibility Strategist, VA + + + + + + + + +
The GSA logo in white, at the bottom of a blue square.Seal of the Office of Personnel Management, OPM.Seal of the Department of Homeland Security, DHS.Seal of the Department of Veterans Affairs, VA.
+ +--- + +### 12:00 pm - 1:00 pm, ET + +Break + +--- + +### 1:00 pm - 1:50 pm, ET + +**Session 3, Crafting quality content** + +Join us for an engaging panel discussion on content strategy development, content creation and curation, and the role of content governance in digital service. You’ll gain insights on managing the content lifecycle, a public-first approach to creating content, and streamlining processes for effective content management. + +**Speakers** + +* **Joe Galbo** — Social Media Specialist, CPSC +* **Sally Harris** — Managing Director, Digital Media and Creative Services, ED +* **Ryan Johnson** — Content Strategist, Service Delivery Team, GSA +* **Rosamund Lannin** — Content Strategist, Service Delivery Team, GSA + + + + + + + +
Seal of the Consumer Product Safety Commission, CPSC.Seal of the U.S. Department of Education.The GSA logo in white, at the bottom of a blue square.
+ +--- + +### 2:00 pm - 2:50 pm, ET + +**Session 4, Navigating seamless acquisitions** + +In this panel discussion, you’ll learn the key factors that contribute to the successful acquisition of services in web and digital experience delivery. You’ll hear from a panel of experts on strategies behind building vs. acquiring services, user-centered procurement, and understanding the unique needs of projects. + +**Speakers** + +* **Anthony Burley** — IT Management, CSOSA +* **Laura Larrimore** — Senior Digital Strategist, DOS +* **Andrew Nielson** — Director of the Government-wide IT Accessibility Program, GSA +* **Ashley Owens** — Senior Digital Acquisition Strategist, Service Delivery Team, GSA +* **Justen Proctor** — Senior Contracting Officer, GSA + + + + + + + +
Seal of the Court Services and Offender Supervision Agency of the District of Columbia, CSOSA.Seal of the Department of State.The GSA logo in white, at the bottom of a blue square.
+ +--- + +### 3:00 pm - 3:50 pm, ET + +**Session 5, We’ve launched, now what?** + +Don’t miss the opportunity to hear from a panel of experts on experiences in successful project close-outs. While it tends to be overlooked, the close-out phase of a project is critical to ensuring long-term success of operations and maintenance in digital services. You’ll learn best practices in conducting post-delivery assessments, data and metrics measurement, documenting lessons learned, and seamless product and service transition. + +**Speakers** + +* **Tori Garten** — Chief of New Media and Web Policy Branch, National Institute of Allergy and Infectious Diseases, NIH +* **Michael Horton** — Accessible Design & Development Advisor, GSA +* **Gloria Huang** — Digital Engagement and Analytics Branch Chief, FEMA +* **Jessica Marine** — Product Manager, Service Delivery Team & Digital Experience (DX) lead, GSA + + + + + + + +
Seal for the Department of Health and Human Services, HHS.The GSA logo in white, at the bottom of a blue square.Logo of the Federal Emergency Management Agency, FEMA.
+ +--- + +### 3:50 pm - 4:00 pm, ET + +{{< img-right src="gsa-blue-logo-sq" >}} + +Closing remarks with Ann Lewis, Director of Technology Transformation Services (TTS), GSA + +--- + +## Resources + +* [Digital service delivery](https://digital.gov/topics/digital-service-delivery/) +* [Requirements for delivering a digital-first public experience](https://digital.gov/resources/delivering-digital-first-public-experience/) +* [Timeless top 10 best practices for great government websites](https://digital.gov/2024/02/09/timeless-top-10-best-practices-for-great-government-websites/) +* [Sunrise to sunset: Building a customer-centric digital ecosystem](https://digital.gov/2022/10/14/sunrise-to-sunset-building-a-customer-centric-digital-ecosystem/) +* [Taking a design-led approach to digital modernization](https://digital.gov/2022/10/07/taking-a-design-led-approach-to-digital-modernization/) + +- - - + +Collaborate and share resources with other communities across government who are focused on building better digital experience in government. [Join a Digital.gov Community of Practice](https://digital.gov/communities/). diff --git a/content/events/2024/03/2024-03-21-uswds-monthly-call-march-2024.md b/content/events/2024/03/2024-03-21-uswds-monthly-call-march-2024.md new file mode 100644 index 0000000000..f0ee4cfc96 --- /dev/null +++ b/content/events/2024/03/2024-03-21-uswds-monthly-call-march-2024.md @@ -0,0 +1,56 @@ +--- +title: USWDS Monthly Call - March 2024 +deck: How to build with U.S. Web Design System tools +kicker: USWDS +summary: Join the U.S. Web Design System team for a lesson on customizing and extending the design system. +host: U.S. Web Design System +event_organizer: Digital.gov +cop_events: "" +registration_url: https://gsa.zoomgov.com/meeting/register/vJIsdu6pqzwuH6ocAtOZ2fI_hHryn0lQ9es +date: 2024-03-21 14:00:00 -0500 +end_date: 2024-03-21 15:00:00 -0500 +# See all topics at https://digital.gov/topics +topics: + - design + - software-engineering + - user-centered-design +slug: uswds-monthly-call-march-2024 +# zoom, youtube_live, adobe_connect, google +event_platform: zoom +primary_image: 2024-uswds-monthly-call-march-title-card + +--- + +Join the U.S. Web Design System team for a lesson on customizing and extending USWDS. You’ll learn how to build new components that look and feel consistent with existing components. + +You’ll learn to: + +* Work with design system settings +* Apply tokens consistently with Sass functions and mixins +* Avoid style conflicts when overriding defaults +* Use tools for ensuring proper color contrast in every context + +**This event is best suited for:** Developers who have basic to advanced familiarity with the design system. + +## Speakers + +* **Dan Williams** **-** Product Lead, USWDS +* **James Mejia** **-** Developer, USWDS Contractor +* **Charlie Mahoney** **-** Developer, USWDS Contractor + +## Join our Communities of Practice + +* [USWDS](https://designsystem.digital.gov/about/community/) +* [Section 508 IT Accessibility](https://www.section508.gov/manage/join-the-508-community/) + +*This event is part of a monthly series that takes place on the third Thursday of each month. Don’t forget to set a placeholder on your personal calendar for our future events this year.* + +## About the USWDS + +[The U.S. Web Design System](https://designsystem.digital.gov/) is a toolkit of principles, guidance, and code to help government teams design and build accessible, mobile-friendly websites backed by user research and modern best practices. + +* [The U.S. Web Design System](https://designsystem.digital.gov/) +* [Contribute on GitHub](https://github.com/uswds/uswds/issues) +* [Email Us](mailto:uswds@gsa.gov) +* [Join our community](https://digital.gov/communities/uswds/) +* [Follow @uswds on Twitter](https://twitter.com/uswds) diff --git a/content/news/2015/02/2015-02-06-getting-to-yes-working-with-vendors-to-secure-terms-of-service-and-federal-friendly-pricing.md b/content/news/2015/02/2015-02-06-getting-to-yes-working-with-vendors-to-secure-terms-of-service-and-federal-friendly-pricing.md index 28bded73b2..993c70a6be 100644 --- a/content/news/2015/02/2015-02-06-getting-to-yes-working-with-vendors-to-secure-terms-of-service-and-federal-friendly-pricing.md +++ b/content/news/2015/02/2015-02-06-getting-to-yes-working-with-vendors-to-secure-terms-of-service-and-federal-friendly-pricing.md @@ -1,7 +1,7 @@ --- slug: getting-to-yes-working-with-vendors-to-secure-terms-of-service-and-federal-friendly-pricing date: 2015-02-06 9:00:32 -0400 -title: 'Getting to Yes: Working with Vendors to Secure Terms of Service and Federal Friendly Pricing' +title: 'Getting to Yes: Working with Vendors to Secure Terms of Service and Federal-Friendly Pricing' summary: The federal government is one of the largest consumers of products and services in the United States. Yet, many agencies face tight budgets and firm guidelines that restrict the parameters under which agencies can use a product or service to complete projects. authors: - clair-koroma @@ -10,27 +10,34 @@ topics: - user-experience - social-media - terms-of-service + --- {{< legacy-img src="2015/02/600-x-400-Successful-handshake-Zurijeta-iStock-Thinkstock-176413004.jpg" alt="Successful handshake" caption="Zurijeta, iStock, Thinkstock" >}} The federal government is one of the largest consumers of products and services in the United States. Yet, many agencies face tight budgets and firm guidelines that restrict the parameters under which agencies can use a product or service to complete projects. This presents an interesting opportunity and dilemma for agencies who want to procure new digital tools to complete their projects. -## Dilemmas {{< legacy-img src="2015/02/250-x-200-legal-clause-symbol-Paragraph-as-Law-Loophole-plrang-iStock-Thinkstock-137436398.jpg" alt="The symbol for legal clauses" caption="plrang, iStock, Thinkstock" >}} +## Dilemmas + +{{< legacy-img-right src="2015/02/250-x-200-legal-clause-symbol-Paragraph-as-Law-Loophole-plrang-iStock-Thinkstock-137436398.jpg" alt="The symbol for legal clauses" caption="plrang, iStock, Thinkstock" >}} - * There are strict guidelines that govern the contracts and legal agreements into which the federal government can enter in order to use a tool or service. For digital products that legal agreement is often in the form of a Terms of Service (TOS) agreement that is crafted by the vendor. Often those terms are not compatible with federal laws and regulations because they dictate how and where legal disputes will be handled. Two of the most problematic clauses are the **Indemnification clauses** that obligate funds if there is a legal dispute and **any clause identifying a specific governing state** or court system in which disputes will be settled. These are problematic because a federal government agency cannot promise to pay funds that have not been appropriated by congress nor can it agree to settle any dispute in a state court. All disputes with the federal government must be settled in federal courts. - * Affordability is a big consideration when procuring a tool. There are many free tools to choose from, but sometimes the right tool for the task comes with a cost. Not only are there increased requirements for procurement for those with higher costs, but there are often longer timelines for acquiring those tools. Additionally, because of shrinking budgets, tools can be unattainable for federal agencies who cannot afford prices that cater to the demands of private industry. +* There are strict guidelines that govern the contracts and legal agreements into which the federal government can enter in order to use a tool or service. For digital products that legal agreement is often in the form of a Terms of Service (TOS) agreement that is crafted by the vendor. Often those terms are not compatible with federal laws and regulations because they dictate how and where legal disputes will be handled. Two of the most problematic clauses are the **Indemnification clauses** that obligate funds if there is a legal dispute and **any clause identifying a specific governing state** or court system in which disputes will be settled. These are problematic because a federal government agency cannot promise to pay funds that have not been appropriated by congress nor can it agree to settle any dispute in a state court. All disputes with the federal government must be settled in federal courts. +* Affordability is a big consideration when procuring a tool. There are many free tools to choose from, but sometimes the right tool for the task comes with a cost. Not only are there increased requirements for procurement for those with higher costs, but there are often longer timelines for acquiring those tools. Additionally, because of shrinking budgets, tools can be unattainable for federal agencies who cannot afford prices that cater to the demands of private industry. -## The Opportunity {{< legacy-img src="2015/01/250-x-158-Business-people-collaborate-puzzle-Jrcasas-iStock-Thinkstock-460134765.jpg" alt="Business people collaborate puzzle" caption="Jrcasas, iStock, Thinkstock" >}} +## The Opportunity + +{{< legacy-img-right src="2015/01/250-x-158-Business-people-collaborate-puzzle-Jrcasas-iStock-Thinkstock-460134765.jpg" alt="Business people collaborate puzzle" caption="Jrcasas, iStock, Thinkstock" >}} The collective power of federal agencies can be very attractive to vendors, both in terms of buying power and heightened visibility in the market. Therefore with a little work on the part of the agency, vendors may be willing to create acceptable TOS agreements and federal-friendly tiers of pricing to meet the unique needs of federal agencies seeking to use their digital tools. Seize the opportunity and work with your legal team and/or contracting officer to reach out to a vendor who has a tool of interest to your agency. Start the conversation by pointing out that, developing a federal TOS and pricing is:: - * **Good for Business:** _Adapting the terms of service and federal-friendly pricing for their product opens up a whole new market segment._ Assure the vendor that this does not need to be a heavy lift for them. Use the resources from the webinar: [Getting to Yes video recording](https://www.youtube.com/watch?v=wc13slb9by4&feature=youtube_gdata) and [Getting to Yes slides](https://s3.amazonaws.com/digitalgov/_legacy-img/2015/02/DHHS-TOS-FINAL.pdf) (PDF, 814 KB, 16 slides, February 2015). Also use [GSA’s model TOS](https://s3.amazonaws.com/digitalgov/_legacy-img/2014/01/model-amendment-to-tos-for-g.doc) (Word document, 55 KB, 5 pages, October 2011), DigitalGov’s information on [Federal-Compatible Terms of Service Agreements]({{< ref "/resources/federal-compatible-terms-of-service-agreements.md" >}} "Federal-Compatible Terms of Service Agreements"), [HHS’ Guide to Negotiating a TOS](http://www.hhs.gov/web/services/negotiate-tos.html) and the help of your agency TOS contact to give the vendor as much information as needed to make the changes you want at a low cost to them. Additionally, give the vendor ideas about the types of pricing tiers that they can use based on other vendors who have them in place for federal government _(For example, Goanimate recently worked with HHS to create a federal-friendly [TOS](http://goanimate.com/termsofuse_government) and [pricing scale](http://goanimate.com/business/videoplans/federal))._ - * **Good for Public Service:** _Adapting the terms of service and federal-friendly pricing for your product delivers impact for public good._ By making the product accessible for use by federal government agencies, the vendor is by default supporting the agency’s mission to provide vital information to the American public. This allows the agency to engage and inspire people to take specific action that contributes to the greater good of society. - * **Good for Taxpayers and Government Agencies:** _Adapting the terms of service and federal-friendly pricing for your product allows government agencies to do more with less._ By default agencies can be more fiscally responsible with the funds that they have. Being able to procure digital tools at a lower pricing tier enables agencies to keep up with new technology and modes of communicating with the public, as well as, be responsible with the money of taxpayers. +* **Good for Business:** _Adapting the terms of service and federal-friendly pricing for their product opens up a whole new market segment._
Assure the vendor that this does not need to be a heavy lift for them. Use the resources from the webinar: [Getting to Yes video recording](https://www.youtube.com/watch?v=wc13slb9by4&feature=youtube_gdata) and [Getting to Yes slides](https://s3.amazonaws.com/digitalgov/_legacy-img/2015/02/DHHS-TOS-FINAL.pdf) (PDF, 814 KB, 16 slides, February 2015). Also use [GSA’s model TOS](https://s3.amazonaws.com/digitalgov/_legacy-img/2014/01/model-amendment-to-tos-for-g.doc) (Word document, 55 KB, 5 pages, October 2011), DigitalGov’s information on [Federal-Compatible Terms of Service Agreements]({{< ref "/resources/federal-compatible-terms-of-service-agreements.md" >}} "Federal-Compatible Terms of Service Agreements"), [HHS’ Guide to Negotiating a TOS](http://www.hhs.gov/web/services/negotiate-tos.html) and the help of your agency TOS contact to give the vendor as much information as needed to make the changes you want at a low cost to them. Additionally, give the vendor ideas about the types of pricing tiers that they can use based on other vendors who have them in place for federal government _(For example, Goanimate recently worked with HHS to create a federal-friendly [TOS](http://goanimate.com/termsofuse_government) and [pricing scale](http://goanimate.com/business/videoplans/federal))._ +* **Good for Public Service:** _Adapting the terms of service and federal-friendly pricing for your product delivers impact for public good._
By making the product accessible for use by federal government agencies, the vendor is by default supporting the agency’s mission to provide vital information to the American public. This allows the agency to engage and inspire people to take specific action that contributes to the greater good of society. +* **Good for Taxpayers and Government Agencies:** _Adapting the terms of service and federal-friendly pricing for your product allows government agencies to do more with less._
By default agencies can be more fiscally responsible with the funds that they have. Being able to procure digital tools at a lower pricing tier enables agencies to keep up with new technology and modes of communicating with the public, as well as, be responsible with the money of taxpayers. ## What to Do After the Vendor Says “Yes” -{{< legacy-img src="2015/02/250-x-186-Businessman-shouting-into-megaphone-Jrcasas-iStock-Thinkstock-158772399.jpg" alt="250-x-186-Businessman-shouting-into-megaphone-Jrcasas-iStock-Thinkstock-158772399" >}}Once you have successfully negotiated a federal-friendly TOS and pricing scale, **tell everyone**. First call your TOS contact at your agency and tell them the good news. Then ensure that they or you contact GSA ([Betsy Steele](mailto:socialmediaapps@gsa.gov)) to let them know about the new TOS and fed-pricing so that they can share your win with the entire federal government community. +{{< legacy-img-right src="2015/02/250-x-186-Businessman-shouting-into-megaphone-Jrcasas-iStock-Thinkstock-158772399.jpg" alt="250-x-186-Businessman-shouting-into-megaphone-Jrcasas-iStock-Thinkstock-158772399" caption="Jrcasas, iStock, Thinkstock" >}} + +Once you have successfully negotiated a federal-friendly TOS and pricing scale, **tell everyone**. First call your TOS contact at your agency and tell them the good news. Then ensure that they or you contact GSA ([Betsy Steele](mailto:socialmediaapps@gsa.gov)) to let them know about the new TOS and fed-pricing so that they can share your win with the entire federal government community. Getting to yes does not have to be difficult. The process may take months, however, the rewards of yes, make the effort worth the endeavor. So if you have a digital tool that you want to use and there is no TOS or fed-pricing in place by the vendor, send an email, then pick up the phone to call the vendor and start working to Get to Yes. diff --git a/content/news/2015/05/2015-05-08-customer-experience-and-user-experience-professionals-a-match-made-in-heaven.md b/content/news/2015/05/2015-05-08-customer-experience-and-user-experience-professionals-a-match-made-in-heaven.md index 2c5d4369f6..0a8634661a 100644 --- a/content/news/2015/05/2015-05-08-customer-experience-and-user-experience-professionals-a-match-made-in-heaven.md +++ b/content/news/2015/05/2015-05-08-customer-experience-and-user-experience-professionals-a-match-made-in-heaven.md @@ -2,31 +2,40 @@ slug: customer-experience-and-user-experience-professionals-a-match-made-in-heaven date: 2015-05-08 9:50:44 -0400 title: 'Customer Experience and User Experience Professionals – A Match Made in Heaven!' -summary: 'Recently, Forrester Research analyst Leah Buley wrote a blog post and report that reminded me of our “what’s the diff?” article on customer experience vs. user experience. In them, she describes the difference between customer experience professionals (CX) and user experience professionals (UX). A Forrester survey found that about 40% of the time, CX and UX are' +summary: 'Recently, Forrester Research analyst Leah Buley wrote a blog post and report that reminded me of our “what’s the diff?” article on customer experience vs. user experience. In them, she describes the difference between customer experience professionals (CX) and user experience professionals (UX).' authors: - ktrebon topics: - product-and-project-management - customer-experience - user-experience + --- -{{< legacy-img src="2015/05/600-x-400-0-two-yellow-puzzle-pieces-TongRo-Images-TongRo-Images-Thinkstock-871735781.jpg" alt="Two yellow puzzle pieces on a wooden table." caption="" >}} +{{< legacy-img-right src="2015/05/600-x-400-0-two-yellow-puzzle-pieces-TongRo-Images-TongRo-Images-Thinkstock-871735781.jpg" alt="Two yellow puzzle pieces on a wooden table." caption="TongRo Images, Thinkstock" >}} Recently, [Forrester Research analyst Leah Buley](https://www.forrester.com/leah-buley "Link to Forrester research and bio Leah Buley ") wrote a [blog post](http://blogs.forrester.com/leah_buley/15-04-24-whats_in_a_name_between_cx_and_ux_a_lot "Link to Leah Buley Forrester Blog Post") and report that reminded me of [our “what’s the diff?” article on customer experience vs. user experience]({{< ref "2014-07-07-user-experience-ux-vs-customer-experience-cx-whats-the-dif.md" >}} "DigitalGov article on customer experience vs. user experience"). In them, she describes the difference between [customer experience]({{< ref "2015-04-08-monthly-theme-how-federal-contact-centers-deliver-great-customer-service.md" >}} "Digital Gov material on customer experience") professionals (CX) and [user experience]({{< ref "/topics/user-experience" >}} "Digital Gov material on user experience ") professionals (UX). A Forrester survey found that about 40% of the time, CX and UX are formalized functions in a corporation. That’s good news, but they are only a joint operation about 10% of the time. Corporations like Discover and Kohl’s follow this model. For the ones that don’t, CX is often housed in the marketing department, while UX is in the technology or product division. -But are CX and UX professionals like lovers destined to remain apart? Or can there be a happy ending to this movie? Here are Forrester’s findings on the subject:_Similarities:_ +But are CX and UX professionals like lovers destined to remain apart? Or can there be a happy ending to this movie? Here are Forrester’s findings on the subject: + +## Similarities - * CX and UX professionals both have key roles in strategy, customer understanding and governance/guidelines/policies._Differences_ + * CX and UX professionals both have key roles in strategy, customer understanding and governance, guidelines, and policies. + +## Differences * CX professionals drive measurement and culture. They often have a MBA, and a background in program management, operations management or quantitative analysis. - * UX pros drive design, so their background is often in that, or human computer interaction. They use processes such as user research, [ideation]({{< ref "2013-11-14-ideation-challenges.md" >}} "Digital Gov material on ideation "), iterative design, prototyping and end user validation. They know design trends, standards and best practices, and are adept in working with software development teams._How Can They Work Better Together?_ + * UX pros drive design, so their background is often in that, or human computer interaction. They use processes such as user research, [ideation]({{< ref "2013-11-14-ideation-challenges.md" >}} "Digital Gov material on ideation "), iterative design, prototyping and end user validation. They know design trends, standards and best practices, and are adept in working with software development teams. + +## How Can They Work Better Together? + +{{< img src="business-people-collaborate-puzzle-jrcasas-istock-thinkstock-460134765" >}} - * {{< legacy-img src="2015/05/250-x-165-Business-people-collaborate-puzzle-Jrcasas-iStock-Thinkstock-460134765.jpg" alt="Two business people collaborate with puzzle pieces" caption="" >}}Stop talking about CX vs. UX, and focus instead on **the work that needs to be done**. + * Stop talking about CX vs. UX, and focus instead on **the work that needs to be done**. * Create a regular way for CX and UX to come together and align efforts. Start simple, with invitations to meetings or conference calls. Bigger efforts to consider later include a Customer Experience Council, and/or connecting CX and UX budgets. * File artifacts electronically in one place, such as data and research about customers. CX and UX professionals are both interested in customer feedback forms, web analytics, tweets, blog comments and email delivery stats. * Focus on more than digital. For example, CX professionals looking to improve [interactive voice response]({{< ref "2015-04-30-digitalgovs-inaugural-podcast-how-ivr-supports-contact-centers.md" >}} "DigitalGov’s Inaugural Podcast: How IVR Supports Contact Centers") (IVR) at their [contact center]({{< ref "/communities/government-contact-center-council.md" >}} "Digital Gov material on the contact center community") can collaborate with UX professionals on problem framing, iterative design and testing, and measurement against the baseline. -Has your agency blended your CX and UX teams? How did it work out? What were the obstacles, if any, and how did you overcome them? \ No newline at end of file +Has your agency blended your CX and UX teams? How did it work out? What were the obstacles, if any, and how did you overcome them? diff --git a/content/news/2024/03/2024-03-06-customer-experience-beyond-surveys.md b/content/news/2024/03/2024-03-06-customer-experience-beyond-surveys.md new file mode 100644 index 0000000000..3b3d8ef7f3 --- /dev/null +++ b/content/news/2024/03/2024-03-06-customer-experience-beyond-surveys.md @@ -0,0 +1,24 @@ +--- +# Originally published at the following URL +source_url: https://18f.gsa.gov/2024/03/05/customer-experience-beyond-surveys/ +source: 18f +date: 2024-03-05 09:00:00 -0500 +title: "Customer experience: beyond surveys" +deck: Want to measure customer experience? Surveys aren’t the only way! Consider + these guiding questions to help your team select an approach based on what you + want to learn. +summary: Want to measure customer experience? Surveys aren’t the only way! + Consider these guiding questions to help your team select an approach based on + what you want to learn. +# See all topics at https://digital.gov/topics +topics: + - customer-experience + - user-centered-design + - human-centered-design + - analytics +slug: customer-experience-beyond-surveys +# Controls how this page appears across the site +# 0 -- hidden +# 1 -- visible +weight: 1 +--- diff --git a/content/resources/21st-century-integrated-digital-experience-act.md b/content/resources/21st-century-integrated-digital-experience-act.md index 625c45436d..6d68710451 100644 --- a/content/resources/21st-century-integrated-digital-experience-act.md +++ b/content/resources/21st-century-integrated-digital-experience-act.md @@ -380,7 +380,7 @@ In the footer of each agency’s website, or the entry point for a digital servi Agencies should consult USWDS and Digital.gov for more specific recommendations on how to best display required links and other relevant information on websites and digital services.69 -View the full policy guidance as a web page +View the full policy guidance as a web page {{< /accordion >}} @@ -441,7 +441,7 @@ The use of signatures may not be appropriate for every scenario involving a publ * **Maintain a digital equivalent method:** To the greatest extent practicable, agencies should not require a handwritten signature (i.e., wet signature) or other in-person identity proofing requirements as a requirement for completing a public-facing form or service without providing the public with a comparable digital equivalent method for submitting information or transacting with an agency. To the greatest extent practicable, agencies should ensure that any public-facing form or service can be provided and completed by the user over different channels, preferably over at least one traditional service channel (e.g., in person) and one digital service channel (e.g., web application) and ideally in the channel that is most convenient to the user. * **Use identity verification when greater assurance of identity is needed:** Agencies should use appropriate identity verification processes for online transactions, commensurate with the agency’s risk assessment, when there is a need for assurance of the identity of the user or the authenticity and integrity of the transaction. Signatures alone do not provide identity assurance and should not be used by themselves for identity verification, identity proofing, or non-repudiation purposes when identity assurance is required. -View the full policy guidance as a web page +View the full policy guidance as a web page {{< /accordion >}} @@ -472,7 +472,7 @@ OMB recommends that agencies prioritize developing digital options for existing 2. Forms directly supporting the delivery of a service or benefit to the public that, if provided digitally, would address user needs, reduce public burden, or improve public impact, as determined based on user research or business analysis. 3. Assistance provided through customer call center support that could be designed as self-service digital tasks for customers to reach resolution on their own. -View the full policy guidance as a web page +View the full policy guidance as a web page {{< /accordion >}} @@ -523,7 +523,7 @@ Within `180 days` of issuance (due March 20, 2024) - **Instructions**: Coordinate with your agency digital experience delivery lead (identified in [action 1 above](https://digital.gov/resources/delivering-digital-first-public-experience/#action-1-identify-digital-experience-delivery-lead)) to submit the agency response. Additional review and submission instructions are available via the online tool, [Agency Action Item #3: Identify and Assess Top Facing Sites (requires a Max.gov account)](https://collectvnext.max.gov/site/174/home-page). This inventory provides a pre-populated list of all public-facing federal websites, and it can be accessed by any federal employee with a Max.gov account. For websites that participate in the [Digital Analytics Program](https://digital.gov/guides/dap/) (DAP), website traffic data is pre-populated. -Note that agencies must complete [action 2 above](https://digital.gov/resources/delivering-digital-first-public-experience/#action-2-identify-public-facing-websites) before action 3. +Note that agencies must complete [action 2 above](https://digital.gov/resources/delivering-digital-first-public-experience/#action-2-identify-public-facing-websites) before action 3. ### Action 4. Assess common questions and top content for deduplication and SEO @@ -557,7 +557,7 @@ Within `180 days` of the launch of the Federal Services Index (date to be determ 5. **Assess top tasks for self-service optimization:** {{< highlight >}}Within 180 days{{< /highlight >}}, agencies that provide services to the public shall review the highest volume public-facing services and identify the tasks required to access each service as well as the channels available to complete each task (e.g., online, phone, mail, in person). Agencies shall provide to OMB a list of opportunities for no less than 5 top tasks that can be newly designed or further optimized as self-service digital options. 6. **Inventory public-facing services:** {{< highlight >}}Within 180 days{{< /highlight >}} of the release of the Federal Services Index, each agency shall develop and submit a preliminary inventory to the Federal Services Index 86 of all public-facing services. For each service that cannot be made available in a digital format, the agency must provide the information specified by section 4(d) of the 21st Century IDEA. 87 Within one year of the release of the Federal Services Index, agencies shall finalize the inventory and make it publicly available online. -View the full policy guidance as a web page +View the full policy guidance as a web page {{< /accordion >}} diff --git a/content/resources/an-introduction-to-search.md b/content/resources/an-introduction-to-search.md index c2080933c6..2a4ea373a7 100644 --- a/content/resources/an-introduction-to-search.md +++ b/content/resources/an-introduction-to-search.md @@ -60,7 +60,7 @@ The Federal Government’s public web presence is an open book that may be crawl - **Indicate timeliness of content:** Agencies should indicate when content on static,30 public-facing websites was created or last updated by including temporal information in line with content or by using “Last Modified” in the HTTP header, in metadata tags, or in XML sitemaps. Time-and-date stamps provide transparency to the user and help the public better understand the freshness of content. When developing a timestamp strategy, agencies should prioritize adding timestamps to content that is time-sensitive, frequently changed, or top-trafficked. - **Permit automated web scraping:** Generally, agencies shall permit web scraping and archival services to operate unimpeded without challenge-response restrictions (e.g., without presenting CAPTCHAs). Blocking or throttling of even potentially abusive crawlers is only appropriate in exceptional circumstances, such as an active denial-of-service attack, and, even then, is appropriate only on a temporary basis. If an agency detects significant public interest in scraping information from web pages, the agency should strongly consider making that information available as machine-readable data that can be accessed in bulk and optimized for automated access (such as through an API). -View the full policy guidance as a web page +View the full policy guidance as a web page {{< /accordion >}} diff --git a/content/resources/eight-principles-mobile-friendliness.md b/content/resources/eight-principles-mobile-friendliness.md index 0a54f53908..14999ec319 100644 --- a/content/resources/eight-principles-mobile-friendliness.md +++ b/content/resources/eight-principles-mobile-friendliness.md @@ -3,7 +3,7 @@ # Learn how to edit our pages at https://workflow.digital.gov slug: eight-principles-mobile-friendliness -date: 2019-12-19 14:000:00 -0500 +date: 2019-12-19 14:00:00 -0500 title: "Eight Principles of Mobile-Friendliness" deck: "Following these principles will help you make your site more usable and user-friendly." summary: "Following these principles will help you make your site more usable and user-friendly." diff --git a/content/resources/guide-robotic-process-automation.md b/content/resources/guide-robotic-process-automation.md index 8bf6409e99..42f1b003c9 100644 --- a/content/resources/guide-robotic-process-automation.md +++ b/content/resources/guide-robotic-process-automation.md @@ -3,7 +3,7 @@ # Learn how to edit our pages at https://workflow.digital.gov slug: guide-to-robotic-process-automation -date: 2020-11-03 14:000:00 -0500 +date: 2020-11-03 14:00:00 -0500 title: "Guide to Robotic Process Automation" deck: "Automate repetitive business processes without writing code" summary: "Configure bots to execute repetitive tasks to save users from performing mundane tasks repeatedly for the same process." diff --git a/content/resources/how-test-websites-for-accessibility.md b/content/resources/how-test-websites-for-accessibility.md index 43577d04b9..4c0ed50005 100644 --- a/content/resources/how-test-websites-for-accessibility.md +++ b/content/resources/how-test-websites-for-accessibility.md @@ -4,7 +4,7 @@ # slug (url path) — changing this requires a redirect slug: how-test-websites-for-accessibility -date: 2020-07-15 14:000:00 -0500 +date: 2020-07-15 14:00:00 -0500 title: "How to Test Websites for Accessibility" deck: "Use both manual and automated testing methods to create accessible websites." summary: "Use both manual and automated testing methods to create accessible websites." diff --git a/content/resources/service-delivery-project-reflection.md b/content/resources/service-delivery-project-reflection.md new file mode 100644 index 0000000000..93b1c63645 --- /dev/null +++ b/content/resources/service-delivery-project-reflection.md @@ -0,0 +1,87 @@ +--- +slug: service-delivery-project-reflection +date: 2024-03-13 12:00:00 -0500 +title: "Service Delivery Project Reflection" +summary: "Use this template, shared at the 2024 Spring Community Summit, to improve your own service delivery." + +# Controls how this page appears across the site +# 0 -- hidden +# 1 -- visible +# 2 -- highlighted +weight: 0 + +topics: + - digital-service-delivery + +authors: + - ammie-farraj-feijoo +--- + +## [project name] | Project reflection + +Start date - End date | [Team members] + +## Background + +[Background, link to project proposal] + +During this time, the Service Delivery team has: +- Description of activity [link as appropriate] +- Description of activity [link as appropriate] + +## Project goals: + +- [Copy from project proposal] + +## Project Prompts + +Let’s spend 5 minutes (more or less) responding to each of the prompts. Feel free to mark other people’s responses up with additional feedback: + +- “+” to signal you agree +- “$” to spend time discussing/unpacking as a group +- “?” if you don’t understand the feedback + +## Did we achieve our goals? How do we know? + +1-2 sentences max. + +- +- + +## Did the outcomes change? When and why? + +1-2 sentences max. + +- +- + +## A few of our biggest achievements: + +- +- + +## A few of the biggest challenges we faced: +- +- + +## What we’d do differently if we could go back in time to the start of this project knowing what we know now: + +- +- + +## 6 months from now, here’s what we should look for to assess our impact: + +If we were to check in on the project 6 months from now, what would tell us whether or not our work had a lasting impact on the partner agency? + +- Good sign: +- Good sign: +- Good sign: +- Bad sign: +- Bad sign: +- Bad sign: + +## Learn more about the project: + +- Slack channel: +- Project drive: +- Github repo: diff --git a/content/resources/service-delivery-transition-plan.md b/content/resources/service-delivery-transition-plan.md new file mode 100644 index 0000000000..47856b12ec --- /dev/null +++ b/content/resources/service-delivery-transition-plan.md @@ -0,0 +1,94 @@ +--- +slug: service-delivery-transition-plan +date: 2024-03-13 12:00:00 -0500 +title: "Service Delivery Transition Plan" +summary: "Use this template, shared at the 2024 Spring Community Summit, to improve your own service delivery." + +# Controls how this page appears across the site +# 0 -- hidden +# 1 -- visible +# 2 -- highlighted +weight: 0 + +topics: + - digital-service-delivery + +authors: + - ammie-farraj-feijoo +--- + + +## Project name + +## Transition Plan + +[partner] + GSA Service Delivery team + +Date +Background + +Over the last [X] months, the GSA Service Delivery team has partnered with [partner] for [purpose from project proposal/link to project proposal]. +[work done to date and outcome]. + +## The goals + +[copy from project proposal] + +## Transition plan + +Below are some scenarios and acceptance criteria that the [partner] and Service Delivery team can use to define success and signal when it’s time for the Service Delivery team to roll off the project. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Priority/SequenceScenarioAcceptance CriteriaStatus
diff --git a/content/resources/tips-for-starting-your-customer-experience.md b/content/resources/tips-for-starting-your-customer-experience.md index b79dba588c..092c9fa983 100644 --- a/content/resources/tips-for-starting-your-customer-experience.md +++ b/content/resources/tips-for-starting-your-customer-experience.md @@ -3,7 +3,6 @@ # Learn how to edit our pages at https://workflow.digital.gov slug: tips-for-starting-your-customer-experience -date: 2020-01-07 24:00:00 -0500 time: 24:00:00 title: "Tips for Starting Your Customer Experience Journey" deck: "Low-cost, low-lift actions that any federal employee can take to improve customer experience." diff --git a/content/resources/uswds-maturity-model.md b/content/resources/uswds-maturity-model.md index 2ed586a237..dac013133e 100644 --- a/content/resources/uswds-maturity-model.md +++ b/content/resources/uswds-maturity-model.md @@ -10,7 +10,6 @@ source: uswds # slug (url path) — changing this requires a redirect slug: uswds-maturity-model -date: 2020-01-16 24:000:00 -0500 title: "USWDS Maturity Model" deck: "How to adopt the design system incrementally and design and build better digital experiences." summary: "How to adopt the design system incrementally and design and build better digital experiences." diff --git a/data/images/150-fema-dhs-logo.yml b/data/images/150-fema-dhs-logo.yml new file mode 100644 index 0000000000..5322d31957 --- /dev/null +++ b/data/images/150-fema-dhs-logo.yml @@ -0,0 +1,12 @@ + + # https://s3.amazonaws.com/digitalgov/150-fema-dhs-logo.png + # Image shortcode: {{< img src=150-fema-dhs-logo >}}' + date : 2024-03-12 00:45:17 -0400 + uid : 150-fema-dhs-logo + width : 150 + height : 150 + format : png + credit : + caption : "" + alt : "The logo for the Federal Emergency Management Agency, combines the U.S. Department of Homeland Security seal on top, and the acronym, FEMA, in bold blue text, below it." + diff --git a/data/images/150-niaid-nih-logo.yml b/data/images/150-niaid-nih-logo.yml new file mode 100644 index 0000000000..dd02376bc4 --- /dev/null +++ b/data/images/150-niaid-nih-logo.yml @@ -0,0 +1,12 @@ + + # https://s3.amazonaws.com/digitalgov/150-niaid-nih-logo.jpg + # Image shortcode: {{< img src=150-niaid-nih-logo >}}' + date : 2024-03-12 02:38:42 -0400 + uid : 150-niaid-nih-logo + width : 150 + height : 150 + format : jpg + credit : + caption : "" + alt : "The logo for the National Institute of Allergy and Infectious Diseases had the gray and blue National Institutes of Health logo, and the NIAID acronym below it in gray captital letters." + diff --git a/data/images/150-nih-niaid-logo.yml b/data/images/150-nih-niaid-logo.yml new file mode 100644 index 0000000000..82c4652103 --- /dev/null +++ b/data/images/150-nih-niaid-logo.yml @@ -0,0 +1,12 @@ + + # https://s3.amazonaws.com/digitalgov/150-nih-niaid-logo.png + # Image shortcode: {{< img src=150-nih-niaid-logo >}}' + date : 2024-03-12 19:24:42 -0400 + uid : 150-nih-niaid-logo + width : 150 + height : 150 + format : png + credit : + caption : "" + alt : "The logo for the National Institute of Allergy and Infectious Diseases had the gray and blue National Institutes of Health logo, and the NIAID acronym below it in gray captital letters." + diff --git a/data/images/2024-uswds-monthly-call-march-title-card.yml b/data/images/2024-uswds-monthly-call-march-title-card.yml new file mode 100644 index 0000000000..d02da9c972 --- /dev/null +++ b/data/images/2024-uswds-monthly-call-march-title-card.yml @@ -0,0 +1,12 @@ + + # https://s3.amazonaws.com/digitalgov/2024-uswds-monthly-call-march-title-card.png + # Image shortcode: {{< img src=2024-uswds-monthly-call-march-title-card >}}' + date : 2024-03-14 20:04:43 -0400 + uid : 2024-uswds-monthly-call-march-title-card + width : 2390 + height : 1244 + format : png + credit : + caption : + alt : Title card image of USWDS logo, a multi-colored pentagon shape consisting of five triangles, centered on a black background. In blue text, the first line says, U.S. Web Design System (USWDS). Below in white text, the second line has the event name, USWDS monthly call March 2024. Below in blue text is date followed by the date of the event in white, March 21, 2024. The next line in blue text is Time followed by the time of the event in white, 2:00 pm ET. + diff --git a/data/images/250-10x-logo-2023.yml b/data/images/250-10x-logo-2023.yml new file mode 100644 index 0000000000..2f4f81f03c --- /dev/null +++ b/data/images/250-10x-logo-2023.yml @@ -0,0 +1,12 @@ + + # https://s3.amazonaws.com/digitalgov/250-10x-logo-2023.png + # Image shortcode: {{< img src=250-10x-logo-2023 >}}' + date : 2024-03-12 22:09:07 -0400 + uid : 250-10x-logo-2023 + width : 250 + height : 250 + format : png + credit : + caption : "" + alt : "The square 10x logo has the number 10 in white and the lowercase x in purple, on a dark background." + diff --git a/data/images/250-court-services-and-offender-supervision-agency-dc-csosa.yml b/data/images/250-court-services-and-offender-supervision-agency-dc-csosa.yml new file mode 100644 index 0000000000..78b2d7444b --- /dev/null +++ b/data/images/250-court-services-and-offender-supervision-agency-dc-csosa.yml @@ -0,0 +1,12 @@ + + # https://s3.amazonaws.com/digitalgov/250-court-services-and-offender-supervision-agency-dc-csosa.png + # Image shortcode: {{< img src=250-court-services-and-offender-supervision-agency-dc-csosa >}}' + date : 2024-03-06 20:45:09 -0400 + uid : 250-court-services-and-offender-supervision-agency-dc-csosa + width : 250 + height : 250 + format : png + credit : + caption : "" + alt : "Seal of the Court Services and Offender Supervision Agency of the District of Columbia, CSOSA." + diff --git a/data/images/250-cpsc-consumer-product-safety-commission.yml b/data/images/250-cpsc-consumer-product-safety-commission.yml new file mode 100644 index 0000000000..d68989604d --- /dev/null +++ b/data/images/250-cpsc-consumer-product-safety-commission.yml @@ -0,0 +1,12 @@ + + # https://s3.amazonaws.com/digitalgov/250-cpsc-consumer-product-safety-commission.png + # Image shortcode: {{< img src=250-cpsc-consumer-product-safety-commission >}}' + date : 2024-03-06 20:38:40 -0400 + uid : 250-cpsc-consumer-product-safety-commission + width : 250 + height : 250 + format : png + credit : + caption : "" + alt : "Seal of the Consumer Product Safety Commission, CPSC." + diff --git a/data/images/250-dhs-svg-seal.yml b/data/images/250-dhs-svg-seal.yml new file mode 100644 index 0000000000..cf506ff04d --- /dev/null +++ b/data/images/250-dhs-svg-seal.yml @@ -0,0 +1,12 @@ + + # https://s3.amazonaws.com/digitalgov/250-dhs-svg-seal.png + # Image shortcode: {{< img src=250-dhs-svg-seal >}}' + date : 2024-03-06 20:41:47 -0400 + uid : 250-dhs-svg-seal + width : 250 + height : 250 + format : png + credit : + caption : "" + alt : "Seal of the Department of Homeland Security, DHS." + diff --git a/data/images/250-doi-svg-seal.yml b/data/images/250-doi-svg-seal.yml new file mode 100644 index 0000000000..1eb12391e8 --- /dev/null +++ b/data/images/250-doi-svg-seal.yml @@ -0,0 +1,12 @@ + + # https://s3.amazonaws.com/digitalgov/250-doi-svg-seal.png + # Image shortcode: {{< img src=250-doi-svg-seal >}}' + date : 2024-03-06 20:39:39 -0400 + uid : 250-doi-svg-seal + width : 250 + height : 250 + format : png + credit : + caption : "" + alt : "Seal of the Department of the Interior, DoI." + diff --git a/data/images/250-education-svg-seal.yml b/data/images/250-education-svg-seal.yml new file mode 100644 index 0000000000..5a453d98c8 --- /dev/null +++ b/data/images/250-education-svg-seal.yml @@ -0,0 +1,12 @@ + + # https://s3.amazonaws.com/digitalgov/250-education-svg-seal.png + # Image shortcode: {{< img src=250-education-svg-seal >}}' + date : 2024-03-06 20:44:21 -0400 + uid : 250-education-svg-seal + width : 250 + height : 250 + format : png + credit : + caption : "" + alt : "Seal of the U.S. Department of Education." + diff --git a/data/images/250-eop-omb-executive-office-president-office-management-budget.yml b/data/images/250-eop-omb-executive-office-president-office-management-budget.yml new file mode 100644 index 0000000000..cd300a9c08 --- /dev/null +++ b/data/images/250-eop-omb-executive-office-president-office-management-budget.yml @@ -0,0 +1,12 @@ + + # https://s3.amazonaws.com/digitalgov/250-eop-omb-executive-office-president-office-management-budget.png + # Image shortcode: {{< img src=250-eop-omb-executive-office-president-office-management-budget >}}' + date : 2024-03-07 02:48:59 -0400 + uid : 250-eop-omb-executive-office-president-office-management-budget + width : 250 + height : 250 + format : png + credit : + caption : "" + alt : "Seal of the Executive Office of the President, Office of Management and Budget, OMB." + diff --git a/data/images/250-fema-federal-emergency-management-agency-seal.yml b/data/images/250-fema-federal-emergency-management-agency-seal.yml new file mode 100644 index 0000000000..1a32acc0c2 --- /dev/null +++ b/data/images/250-fema-federal-emergency-management-agency-seal.yml @@ -0,0 +1,12 @@ + + # https://s3.amazonaws.com/digitalgov/250-fema-federal-emergency-management-agency-seal.png + # Image shortcode: {{< img src=250-fema-federal-emergency-management-agency-seal >}}' + date : 2024-03-07 01:38:45 -0400 + uid : 250-fema-federal-emergency-management-agency-seal + width : 250 + height : 250 + format : png + credit : + caption : "" + alt : "Seal of the Federal Emergency Management Agency, FEMA." + diff --git a/data/images/250-hhs-svg-seal.yml b/data/images/250-hhs-svg-seal.yml new file mode 100644 index 0000000000..9a06ef02e4 --- /dev/null +++ b/data/images/250-hhs-svg-seal.yml @@ -0,0 +1,12 @@ + + # https://s3.amazonaws.com/digitalgov/250-hhs-svg-seal.png + # Image shortcode: {{< img src=250-hhs-svg-seal >}}' + date : 2024-03-07 15:33:36 -0400 + uid : 250-hhs-svg-seal + width : 250 + height : 250 + format : png + credit : + caption : "" + alt : "Seal for the Department of Health and Human Services, HHS." + diff --git a/data/images/250-inter-american-foundation-iaf-seal.yml b/data/images/250-inter-american-foundation-iaf-seal.yml new file mode 100644 index 0000000000..3fde450258 --- /dev/null +++ b/data/images/250-inter-american-foundation-iaf-seal.yml @@ -0,0 +1,12 @@ + + # https://s3.amazonaws.com/digitalgov/250-inter-american-foundation-iaf-seal.png + # Image shortcode: {{< img src=250-inter-american-foundation-iaf-seal >}}' + date : 2024-03-07 15:33:01 -0400 + uid : 250-inter-american-foundation-iaf-seal + width : 250 + height : 250 + format : png + credit : + caption : "" + alt : "Seal of the Inter-American Foundation, IAF." + diff --git a/data/images/250-opm-svg-seal.yml b/data/images/250-opm-svg-seal.yml new file mode 100644 index 0000000000..b02b9e6ccb --- /dev/null +++ b/data/images/250-opm-svg-seal.yml @@ -0,0 +1,12 @@ + + # https://s3.amazonaws.com/digitalgov/250-opm-svg-seal.png + # Image shortcode: {{< img src=250-opm-svg-seal >}}' + date : 2024-03-06 20:40:41 -0400 + uid : 250-opm-svg-seal + width : 250 + height : 250 + format : png + credit : + caption : "" + alt : "Seal of the Office of Personnel Management, OPM." + diff --git a/data/images/250-sq-gsa-blue-logo.yml b/data/images/250-sq-gsa-blue-logo.yml new file mode 100644 index 0000000000..3b407cb644 --- /dev/null +++ b/data/images/250-sq-gsa-blue-logo.yml @@ -0,0 +1,12 @@ + + # https://s3.amazonaws.com/digitalgov/250-sq-gsa-blue-logo.png + # Image shortcode: {{< img src=250-sq-gsa-blue-logo >}}' + date : 2024-03-07 15:34:36 -0400 + uid : 250-sq-gsa-blue-logo + width : 250 + height : 250 + format : png + credit : + caption : "" + alt : "The GSA logo in white, at the bottom of a medium blue square." + diff --git a/data/images/250-state-dept-seal.yml b/data/images/250-state-dept-seal.yml new file mode 100644 index 0000000000..6d8870caae --- /dev/null +++ b/data/images/250-state-dept-seal.yml @@ -0,0 +1,12 @@ + + # https://s3.amazonaws.com/digitalgov/250-state-dept-seal.png + # Image shortcode: {{< img src=250-state-dept-seal >}}' + date : 2024-03-06 20:39:13 -0400 + uid : 250-state-dept-seal + width : 250 + height : 250 + format : png + credit : + caption : "" + alt : "Seal of the Department of State." + diff --git a/data/images/250-usaid-united-states-agency-for-international-development-seal.yml b/data/images/250-usaid-united-states-agency-for-international-development-seal.yml new file mode 100644 index 0000000000..de4af3ad56 --- /dev/null +++ b/data/images/250-usaid-united-states-agency-for-international-development-seal.yml @@ -0,0 +1,12 @@ + + # https://s3.amazonaws.com/digitalgov/250-usaid-united-states-agency-for-international-development-seal.png + # Image shortcode: {{< img src=250-usaid-united-states-agency-for-international-development-seal >}}' + date : 2024-03-06 21:01:46 -0400 + uid : 250-usaid-united-states-agency-for-international-development-seal + width : 250 + height : 250 + format : png + credit : + caption : "" + alt : "Seal for the United States Agency for International Development, USAID." + diff --git a/data/images/250-va-veterans-affairs-svg-seal.yml b/data/images/250-va-veterans-affairs-svg-seal.yml new file mode 100644 index 0000000000..fb07ec1f19 --- /dev/null +++ b/data/images/250-va-veterans-affairs-svg-seal.yml @@ -0,0 +1,12 @@ + + # https://s3.amazonaws.com/digitalgov/250-va-veterans-affairs-svg-seal.png + # Image shortcode: {{< img src=250-va-veterans-affairs-svg-seal >}}' + date : 2024-03-06 20:43:46 -0400 + uid : 250-va-veterans-affairs-svg-seal + width : 250 + height : 250 + format : png + credit : + caption : "" + alt : "Seal of the Department of Veterans Affairs, VA." + diff --git a/data/images/business-people-collaborate-puzzle-jrcasas-istock-thinkstock-460134765.yml b/data/images/business-people-collaborate-puzzle-jrcasas-istock-thinkstock-460134765.yml new file mode 100644 index 0000000000..e8c90453cf --- /dev/null +++ b/data/images/business-people-collaborate-puzzle-jrcasas-istock-thinkstock-460134765.yml @@ -0,0 +1,12 @@ + + # https://s3.amazonaws.com/digitalgov/business-people-collaborate-puzzle-jrcasas-istock-thinkstock-460134765.jpg + # Image shortcode: {{< img src=business-people-collaborate-puzzle-jrcasas-istock-thinkstock-460134765 >}}' + date : 2024-03-13 15:53:34 -0400 + uid : business-people-collaborate-puzzle-jrcasas-istock-thinkstock-460134765 + width : 600 + height : 379 + format : jpg + credit : + caption : "jrcasas, iStock, Thinkstock" + alt : "Illustration of two excited business people collaborate with puzzle pieces." + diff --git a/data/images/gsa-blue-logo-sq.yml b/data/images/gsa-blue-logo-sq.yml index 86edfc2ed6..b2afb1f37e 100644 --- a/data/images/gsa-blue-logo-sq.yml +++ b/data/images/gsa-blue-logo-sq.yml @@ -7,6 +7,6 @@ height : 1024 format : png credit : - caption : - alt : - \ No newline at end of file + caption : "" + alt : "The GSA logo in white, at the bottom of a blue square." + diff --git a/data/images/nih-niaid-logo.yml b/data/images/nih-niaid-logo.yml new file mode 100644 index 0000000000..f080f161b3 --- /dev/null +++ b/data/images/nih-niaid-logo.yml @@ -0,0 +1,12 @@ + + # https://s3.amazonaws.com/digitalgov/nih-niaid-logo.jpg + # Image shortcode: {{< img src=nih-niaid-logo >}}' + date : 2024-03-12 14:23:15 -0400 + uid : nih-niaid-logo + width : 285 + height : 268 + format : jpg + credit : + caption : "" + alt : "The logo for the National Institute of Allergy and Infectious Diseases had the gray and blue National Institutes of Health logo, and the NIAID acronym below it in gray captital letters." + diff --git a/data/images/spring-2024-community-title-card.yml b/data/images/spring-2024-community-title-card.yml new file mode 100644 index 0000000000..1f0d10ce11 --- /dev/null +++ b/data/images/spring-2024-community-title-card.yml @@ -0,0 +1,12 @@ + + # https://s3.amazonaws.com/digitalgov/spring-2024-community-title-card.png + # Image shortcode: {{< img src=spring-2024-community-title-card >}}' + date : 2024-03-01 21:16:03 -0400 + uid : spring-2024-community-title-card + width : 1200 + height : 630 + format : png + credit : + caption : + alt : "Title card graphic for the event has a white background, and on the right, a flat vector illustration in shades of blue of four people at a conference room table. On the left are three sections of text in dark blue. The first line has the blue Digital.gov logo, three blue ribbons joined together in an hexagon to resemble a capital letter D, and says, Digital.gov Communities of Practice. The next section is the title of the event, Spring 2024 Community Summit: Delivering a digital-first public experience. The last section gives the Date: March 13, 2024, and Time: 10:00 am - 4:00 pm, Eastern." + diff --git a/data/usa_identifier.yml b/data/usa_identifier.yml index db1a9cfac1..79b2070733 100644 --- a/data/usa_identifier.yml +++ b/data/usa_identifier.yml @@ -7,7 +7,7 @@ identifier_data: parent_agency: name: U.S. General Services Administration acronym: GSA - logo: /img/gsa-logo-w100.png + logo: img/gsa-logo-w100.png url: https://www.gsa.gov required_links: label: Important links diff --git a/themes/digital.gov/layouts/_default/baseof.html b/themes/digital.gov/layouts/_default/baseof.html index 7b430a0697..bd64d9d7c5 100644 --- a/themes/digital.gov/layouts/_default/baseof.html +++ b/themes/digital.gov/layouts/_default/baseof.html @@ -58,7 +58,7 @@ glossaryPath = "{{ $glossaryPath | absURL }}"; {{- end -}} // Needed to pass relURL to JS - const glossaryIcon = "{{ "/uswds/img/sprite.svg#expand_more" | relURL }}" + const glossaryIcon = "{{ "uswds/img/sprite.svg#expand_more" | relURL }}" diff --git a/themes/digital.gov/layouts/_default/taxonomy.html b/themes/digital.gov/layouts/_default/taxonomy.html index edef156c82..a57a26ad9e 100644 --- a/themes/digital.gov/layouts/_default/taxonomy.html +++ b/themes/digital.gov/layouts/_default/taxonomy.html @@ -13,7 +13,7 @@

Topics

Categories / - See all » + See all »

diff --git a/themes/digital.gov/layouts/communities/list.html b/themes/digital.gov/layouts/communities/list.html index f4270c910d..c1c95c6512 100644 --- a/themes/digital.gov/layouts/communities/list.html +++ b/themes/digital.gov/layouts/communities/list.html @@ -14,7 +14,7 @@

Other Communities of Practice

These communities are not managed by Digital.gov, but are listed here
because they overlap with - our mission. + our mission.
diff --git a/themes/digital.gov/layouts/home.html b/themes/digital.gov/layouts/home.html index fe32164f6d..93d055b996 100644 --- a/themes/digital.gov/layouts/home.html +++ b/themes/digital.gov/layouts/home.html @@ -66,7 +66,7 @@

See all 21st Century IDEA resources */}} {{- if $source -}} {{- if $source.Params.logo -}} - {{- $src := (printf "/logos/%s%s" $source.Params.logo "-logo.png") -}} + {{- $src := (printf "logos/%s%s" $source.Params.logo "-logo.png") -}} {{- $source.Params.name }} logo {{- end -}} diff --git a/themes/digital.gov/layouts/partials/core/featured-collection.html b/themes/digital.gov/layouts/partials/core/featured-collection.html index 492906de5d..52bf90f62e 100644 --- a/themes/digital.gov/layouts/partials/core/featured-collection.html +++ b/themes/digital.gov/layouts/partials/core/featured-collection.html @@ -26,7 +26,7 @@

{{- .heading -}}

{{- if $source.Params.logo -}} {{/* get the path for the icon — e.g. 18f-icon.png */}} - {{- $src := (printf "/logos/%s%s" $source.Params.logo "-icon.png") -}} + {{- $src := (printf "logos/%s%s" $source.Params.logo "-icon.png") -}} {{/* Pass these vars into the collection template (see bottom of collection.html partial) */}} @@ -53,7 +53,7 @@

{{- .heading -}}

{{/* Pass these vars into the collection template (see bottom of collection.html partial) */}} - {{- template "collection-list-item" dict "item" . "href" (print .Permalink "?dg") "src" (print "/img/digit-50.png") -}} + {{- template "collection-list-item" dict "item" . "href" (print .Permalink) "src" (print "img/digit-50.png") -}} {{- end -}} {{- end -}} diff --git a/themes/digital.gov/layouts/partials/core/footer.html b/themes/digital.gov/layouts/partials/core/footer.html index 843f731769..f33eb0d792 100644 --- a/themes/digital.gov/layouts/partials/core/footer.html +++ b/themes/digital.gov/layouts/partials/core/footer.html @@ -145,7 +145,7 @@

Social

RSS diff --git a/themes/digital.gov/layouts/partials/core/get_related.html b/themes/digital.gov/layouts/partials/core/get_related.html index aae8feb86a..f181c0c119 100644 --- a/themes/digital.gov/layouts/partials/core/get_related.html +++ b/themes/digital.gov/layouts/partials/core/get_related.html @@ -41,7 +41,7 @@

Join a Community

See all {{ $communityCount }} communities diff --git a/themes/digital.gov/layouts/partials/core/glossary.html b/themes/digital.gov/layouts/partials/core/glossary.html index 1563f4cfe8..056466e9f1 100644 --- a/themes/digital.gov/layouts/partials/core/glossary.html +++ b/themes/digital.gov/layouts/partials/core/glossary.html @@ -16,7 +16,7 @@ aria-hidden="true" focusable="true" > - + {{/* Used as a hook in `summary-box.js`. */}} diff --git a/themes/digital.gov/layouts/partials/core/guides/guide-menu-bar.html b/themes/digital.gov/layouts/partials/core/guides/guide-menu-bar.html index ea0bbcba0f..9f33125536 100644 --- a/themes/digital.gov/layouts/partials/core/guides/guide-menu-bar.html +++ b/themes/digital.gov/layouts/partials/core/guides/guide-menu-bar.html @@ -8,14 +8,14 @@