Merge branch 'main' into bc-inclusive-language

config.yml

@@ -131,10 +131,6 @@ menu:
       Identifier: "guides"
       URL: "/guides/"
       Weight: 4
-    - Name: "Tools"
-      Identifier: "tools"
-      URL: "/services/directory/"
-      Weight: 5
     - Name: "Job board"
       Identifier: "job-board"
       URL: "/job-board/"

content/about/contribute.md

@@ -2,8 +2,8 @@
 slug: contribute
 date: 2019-07-10 4:00:00 -0500
 title: Contribute to Digital.gov
-deck: "Have a case study to share? Did your team recently launch something new? Here is what we're looking for."
-summary: "Have a case study to share? Did your team recently launch something new? Here is what we're looking for."
+deck: "Have a story to share? Here is what we’re looking for."
+summary: "Have a story to share? Here is what we’re looking for."
 aliases:
   - /join-digitalgov/
   - /about/join/
@@ -13,59 +13,63 @@ aliases:
 ---
 Digital.gov provides guidance on building better digital services in government. Do you have a case study or success story to share? Did your team recently accomplish something noteworthy?
 
-We’re always on the lookout for contributions from our community members. Keep reading for more information on the requirements and how to contribute.
+We’re always on the lookout for ideas from our [community members](https://digital.gov/communities/).
 
-{{< box color="light-blue" >}}
-**Contribution requirements**
+## How to contribute content and events
 
-**Who:** We welcome insights and expertise from folks across all levels of experience. You must belong to at least one Digital.gov community and be a federal employee or contractor with a .gov or .mil email. Federal employees must have approval from their supervisors for all work submitted to Digital.gov. Federal contractors must have approval from their federal product manager, COR, or both. We cannot accept promotional content or pitches from the public.
+Agency stories are an important tool to empower and support colleagues who are working to improve digital content. Digital.gov gathers ideas and expertise from across the federal government and shares that information with thousands of community members, readers, and event attendees. 
 
-**What:** You can contribute to content, events, or both. And if you’re not ready to take that big of a leap, there are plenty of other ways to contribute.
+### 1. Check if you are eligible to contribute.
 
-**When:** We accept contributions on a rolling basis.
+We welcome ideas and expertise from folks across all levels of experience. You must belong to at least one Digital.gov community and be a federal employee or contractor with an official government email. In most cases, this is a .gov or .mil account. Federal employees must have approval from their supervisors for all work submitted to Digital.gov. Federal contractors must have approval from their federal product manager, Contracting Officer’s Representative, or both. We cannot accept promotional content or pitches from the public.
 
-**Why:** We will share your story with tens of thousands of community members, readers, and event attendees. You and your team deserve the recognition!
+### 2. Make sure your contribution aligns with our users’ needs.
 
-**How:** Email [email protected] to submit your ideas.
-{{< /box >}}
+Not sure what to share? Digital.gov focuses on creating content with direct and actionable connections to digital services. We are looking for ideas that will help generalists, technologists, and teams in the federal government create world-class digital experiences. You can find examples of recent case studies and stories in our [blogs](https://digital.gov/news/) and on our [resource](https://digital.gov/resources/) pages. 
 
-## How to contribute content and events
+If you’re interested in pitching an event, check out our [video archive of past events](https://youtube.com/@DigitalGov). You can also explore our [guidelines for Digital.gov event presenters](https://digital.gov/resources/guidelines-for-digital-gov-event-presenters/).
 
-### Web content
+### 3. Write and share your pitch. 
 
-Agency stories are an important tool to empower and support colleagues who are working “in the trenches” to improve digital content.
+Write a 3-5 sentence summary of your idea and the content type you have in mind, like a blog or an event. Email this pitch to [[email protected]](mailto:[email protected]).
 
-Email [[email protected]](mailto:[email protected]) to submit your ideas for web content. We will review your ideas and provide feedback, prioritizing the ideas that best align with our mission and audience. We will also share an easy-to-follow content template with you. You’ll have a few weeks to write the content and submit it to us. Then, our editorial team will copy edit the content and publish it on Digital.gov and related channels.
+If you’re submitting an event, you can also use our [event submission form](https://feedback.gsa.gov/jfe/form/SV_1MS3YC4dieV8WQm).
 
-* [Resources](https://digital.gov/resources/): Submit a 300- to 500-word guidance document, checklist, toolkit, style guide, or other similar resource to help agencies improve their digital content.
+### 4. Digital.gov’s editorial team reviews the pitch. 
 
-* [Blog posts](https://digital.gov/news/): Submit a newsworthy 500- to 750-word article to share a case study, success story, or challenge you faced while working to make federal digital services better for the public.
+We accept and review pitches on a rolling basis. Our team will look at your idea to determine the right format or event type, relevance to our audience, and match to our mission and goals.
 
-Want to request a content update, report a bug, or suggest a feature? Use the green "New Issue" button on [our GitHub Issues page](https://github.com/GSA/digitalgov.gov/issues). When filling out the issue, apply any relevant labels (in the right column), and be sure to:
+### 5. Work with our content strategists and editors to produce the content or event. 
 
-1. include the URL of the page
-2. describe the issue or request
+If your pitch is accepted, we’ll work with you to produce the content. This can include interviewing relevant stakeholders, editing for style and voice, and making sure it is reviewed by subject matter experts. We aim to publish written content within 6 to 8 weeks from the time work begins. Most events are held 8 to 12 weeks after they are proposed.
 
 {{< box color="light-gray" >}}
 **Did you know?** Digital.gov follows the [Associated Press (AP) Stylebook](https://www.apstylebook.com/) and [general plain language guidance](https://www.plainlanguage.gov/). When we make edits, it’s to ensure the content reaches and engages our audience. View our full [Digital.gov Style Guide](https://digital.gov/style-guide/).
 {{< /box >}}
 
-### Informational events
+## Submit requests in GitHub
 
-[Digital.gov events](https://digital.gov/events/) highlight the work federal employees are doing across government to improve digital services and provides a range of free events — from huddles to webinars to summits — for people and teams across the federal government.
+Do you want to request a content update, report a bug, or suggest a feature? Use the green "New Issue" button on [our GitHub Issues page](https://github.com/GSA/digitalgov.gov/issues). When filling out the issue, apply any relevant labels (in the right column), and be sure to:
 
-Email [[email protected]](mailto:[email protected]) to volunteer to present or moderate at an event. You can also submit ideas for event topics in the [Digital.gov event submission form](https://feedback.gsa.gov/jfe/form/SV_1MS3YC4dieV8WQm). Speakers must be federal employees or federal contractors presenting along with their federal counterparts. Read our [Guidelines for Digital.gov event presenters](https://digital.gov/resources/guidelines-for-digital-gov-event-presenters/) to know what to expect.
+* include the URL of the page
+* describe the issue or request
 
-* **Webinars:** Webinars generally consist of a 15- to 20-minute presentation followed by a moderated Q&A session. Most webinars are open to the public.
+## Other ways to contribute
 
-* **Huddles:** Huddles provide Digital.gov community members a place to discuss specific topics, share best practices, and spark ideas. Community huddles generally consist of a 5- to 10-minute presentation followed by a moderated, open mic discussion among panelists and community members.
+While we welcome event and content ideas from community members across all levels of experience, we know that can feel like a big leap, especially for folks who are new to the federal government or Digital.gov. So, we offer other ways to contribute.
 
-## Other ways to contribute
+### Community mailing lists
 
-While we welcome event and content contributions from community members across all levels of experience, we know that can feel like a big leap, especially for folks who are new to the federal government or Digital.gov. So, we offer other ways to contribute.
+Join our [Digital.gov Communities of Practice](https://digital.gov/communities/) to share your thoughts and ideas on the community mailing lists. All community members can post messages on the mailing lists. And be sure to join several communities. Each community has its own culture, and you don’t have to be an expert to join and learn something new.
 
-**Open Opportunities:** We occasionally post short, recurring tasks on the Open Opportunities platform. Each task takes about 8 hours. [Browse all Digital.gov tasks](https://openopps.usajobs.gov/search?state=open&state=in%20progress&term=digital.gov&page=1) to find one that is a good fit for you.
+### Feedback
 
-**Community mailing lists:** Share your thoughts and ideas on the community LISTSERV. Tell us about your agency and team and some of your noteworthy projects. Share best practices and resources. Ask questions about new research, industry trends, and other topics. All community members can post messages on the LISTSERV. And be sure to [join several Digital.gov communities of practice](https://digital.gov/communities/). Each community has its own culture, and you’ll learn something new by joining more than one community.
+We want to hear from you! We use feedback from community members and the public to continually improve Digital.gov. Complete our post-event, website, and community surveys, or write to us at [[email protected]](mailto:[email protected]) to share what’s on your mind.
+
+### Open Opportunities
+
+We occasionally post short, recurring tasks on the Open Opportunities platform. Each task takes about 8 hours. [Browse all Digital.gov tasks](https://openopps.usajobs.gov/search?state=open&state=in%20progress&term=digital.gov&page=1) to find one that is a good fit for you.
+
+---
 
-**Feedback:** We want to hear from you. We use feedback from community members and the public to continually improve Digital.gov. Complete our post-event, website, and community surveys, or write to us at [[email protected]](mailto:[email protected]) to share what’s on your mind.
+**Disclaimer**: All references to specific brands, products, and/or companies are used only for illustrative purposes and do not imply endorsement by the U.S. federal government or any federal government agency.

content/authors/behati-hart/_index.md

@@ -0,0 +1,16 @@
+---
+display_name: Behati Hart
+first_name: Behati
+last_name: Hart
+# e.g. U.S. General Services Administration
+agency_full_name: U.S. General Services Administration
+# Agency Acronym [e.g., GSA]
+agency: GSA
+# [e.g. 'jeremyzilar'] — A GitHub account will allow you to edit pages on Digital.gov.
+# Also, the image used in your GitHub account can be used to populate your digital.gov profile photo.
+# Learn more about getting a Github account at [URL]
+github: beharti
+# See [URL] for a full list of profile photo options
+profile_photo: github
+slug: behati-hart
+---

content/authors/mitchell-henke/_index.md

@@ -0,0 +1,14 @@
+---
+display_name: Mitchell Henke
+first_name: Mitchell
+last_name: Henke
+# e.g. U.S. General Services Administration
+agency_full_name: U.S. General Services Administration
+# Agency Acronym [e.g., GSA]
+agency: GSA
+# [e.g. 'jeremyzilar'] — A GitHub account will allow you to edit pages on Digital.gov.
+# Also, the image used in your GitHub account can be used to populate your digital.gov profile photo.
+# Learn more about getting a Github account at [URL]
+github: mitchellhenke
+slug: mitchell-henke
+---

content/authors/nick-ng/_index.md

@@ -0,0 +1,14 @@
+---
+display_name: Nick Ng
+first_name: Nick
+last_name: Ng
+# e.g. U.S. General Services Administration
+agency_full_name: U.S. General Services Administration
+# Agency Acronym [e.g., GSA]
+agency: GSA
+# [e.g. 'jeremyzilar'] — A GitHub account will allow you to edit pages on Digital.gov.
+# Also, the image used in your GitHub account can be used to populate your digital.gov profile photo.
+# Learn more about getting a Github account at [URL]
+github: nickttng
+slug: nick-ng
+---

content/communities/communicators.md

@@ -1,29 +1,38 @@
 ---
-# See all topics at https://digital.gov/topics
-topics:
-  - content-strategy
-  - plain-language
-  - social-media
-  - communication
 
-dg_acronym: FCN
-dg_logo: communities-communicators.svg
-date: 2021-02-24 18:49:00 -0500
 title: Join the Communicators
 summary: "Improve written and verbal communication to make government more effective."
-
 deck: Share and learn with communications and public affairs practitioners.
 
+dg_shortname: Communicators
+dg_acronym: FCN
+dg_logo: communities-communicators.svg
+dg_highlight: true
+date: 2021-02-24 18:49:00 -0500
+
 # See all authors at https://digital.gov/authors
 authors:
   - deanna-mccray-james
   - josie-anderson
 
-dg_shortname: Communicators
-slug: communicators
-kicker: Communities of practice
+# See all topics at https://digital.gov/topics
+topics:
+  - content-strategy
+  - plain-language
+  - social-media
+  - communication
+
+event_cop: communicators
+
+community_list:
+  - platform: listserv
+    type: government
+    subscribe_email: "[email protected]"
+    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,554
+    join_cop_button: "Communicators community members"
 
-primary_image:
 # Controls how this page appears across the site
 # 0 -- hidden
 # 1 -- visible
@@ -43,9 +52,7 @@ community_list:
       are eligible to join.
     members: 2,501
     join_cop_button: Communicators community members
-dg_highlight: true
-event_cop:
-  - communicators
+
 ---
 
 Government professionals from all levels come together in this community to improve written and verbal communication to make government communication more effective.

content/communities/contact-center.md

@@ -15,8 +15,7 @@ topics:
   - contact-centers
   - customer-experience
 
-event_cop:
-  - contact-center
+event_cop: contact-center
 
 community_list:
   - platform: listserv

content/communities/multilingual.md

@@ -18,8 +18,7 @@ authors:
   - lgodfrey
   - fedora-braverman
 
-event_cop:
-  - multilingual
+event_cop: multilingual
 
 # see all topics at https://digital.gov/topics
 topics:

content/communities/plain-language-community-of-practice.md

@@ -27,8 +27,7 @@ topics:
   - plain-language
   - communication
 
-event_cop:
-  - plain-language
+event_cop: plain-language
 
 # Weight: controls how this page appears across the site
 # 0 -- hidden

content/communities/social-media.md

@@ -18,8 +18,7 @@ authors:
 topics:
   - social-media
 
-event_cop:
-  - social-media
+event_cop: social-media
 
 # Page weight: controls how this page appears across the site
 # 0 -- hidden

content/communities/user-experience.md

@@ -17,8 +17,7 @@ aliases:
 topics:
   - user-experience
 
-event_cop:
-  - user-experience
+event_cop: user-experience
 
 # Weight: controls how this page appears across the site
 # 0 -- hidden

content/communities/web-analytics-and-optimization.md

@@ -24,8 +24,7 @@ aliases:
 authors:
   - tlowden
 
-event_cop:
-  - web-analytics
+event_cop: web-analytics
 
 # Controls how this page appears across the site
 # 0 -- hidden

content/communities/web-managers-forum.md

@@ -46,8 +46,7 @@ authors:
   - beth-martin
   - ruxi-giura
 
-event_cop:
-  - web-managers
+event_cop: web-managers
 
 # Page weight: controls how this page appears across the site
 # 0 -- hidden