Skip to content

Update to wegov #4

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
devinbalkind wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Update to wegov #4

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
56 changes: 11 additions & 45 deletions content/about/contribute.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
---
slug: contribute
date: 2019-07-10 4:00:00 -0500
title: Contribute to Digital.gov
title: Contribute to WeGov.nyc
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."
aliases:
Expand All @@ -12,65 +12,31 @@ aliases:

---

While our primary mission is helping agencies implement new technologies or innovations to increase public experience, Digital.gov has several channels to reach both federal and non-federal stakeholders. We send out a newsletter to a broad range of people in government, host informational blog posts, resources, and videos on our site, as well as offer various learning opportunities.
While our primary mission is helping New Yorkers implement new technologies or innovations to improve the city, WeGov.NYC has several channels to reach both stakeholders. We send out a newsletter to a broad range of people, host informational blog posts, resources, and videos on our site, as well as offer various learning opportunities.

We regularly accept content for this site from various federal agencies and are open to other suggestions. [Learn more about what our readers need »](#what-our-readers-need)
We accept content from people working on civic and public interest technology projects including people working as an inidivudal, with for-profits, nonprofits, and government agencies. [Learn more about what our readers need »](#what-our-readers-need)

- **News, Updates, and Blog Posts** — Examples of other agencies’ success are some of the most powerful tools toward convincing colleagues to follow modern practices. We are looking for posts that show what your team is working on, what challenges you’re facing, or how you’re working to make digital better for the public.
- **Case Studies** — We are looking for examples of what agencies are doing, case studies, or collections of validated federal-wide news that has an impact on digital in one spot.
- **Informational Events** — Digital.gov provides a range of free events for people and teams across the federal government.
- **Resources, Tools, and Services** — To help agencies confidently take steps toward working smarter, we try to collect a list of available implementation playbooks, guidance documents, checklists, toolkits, style guides, and other similar content organized by specific topic areas.
- **News, Updates, and Blog Posts** — Examples of success are some of the most powerful tools toward convincing people to follow modern practices. We are looking for posts that show what you are working on, what challenges you’re facing, or how you’re working to make digital better for the public.
- **Case Studies** — We are looking for examples of how people, projects and agencies are using digital technologies to improve the city..
- **Informational Events** — WeGov.NYC produces a calendar of events for people working to improve the city.
- **Resources, Tools, and Services** — To help people confidently take steps toward working smarter, we try to collect a list of available implementation playbooks, guidance documents, checklists, toolkits, style guides, and other similar content organized by specific topic areas.

<!-- {{< hs-form-contribute >}} -->

## Submission Considerations

Just a few quick notes to consider before submitting your contribution request:

- **Your Organization** — We cannot accept promotional content or pitches from vendors. If content is about programs at your agency, you must have it reviewed and approved by your agency’s communications team before submitting.
- **Format** — We can post content in various formats, including presentations, video, and written prose. We also link to content posted by other agencies. As is required for any online content, please make sure that your submission and any related files are accessible and mobile-friendly.
- **Your Organization** — Please identify what organization you work with. We accept contributions form all types of organizations but we will not post promotional content for vendors of proprietary technologies.
- **Format** — We can post content in various formats, including presentations, video, and written prose. We also link to content posted by other individuals and organizations. As is required for any online content, please make sure that your submission and any related files are accessible and mobile-friendly.
- **Length** — We generally like to keep people’s attention so we just ask that you consider your reader or audience.
- **Style and Editing** — Digital.gov follows the Associated Press (AP) Style Guide and general Plain Language guidance. When we make edits, it’s usually to ensure that your content reaches and engages our audience. View our full [Digital.gov Style Guide]({{< ref "style-guide.md" >}}).
- **Style and Editing** — WeGov.NYC tries to follow the Associated Press (AP) Style Guide and general Plain Language guidance. When we make edits, it’s usually to ensure that your content reaches and engages our audience. View our full [Digital.gov Style Guide]({{< ref "style-guide.md" >}}).
- **Visuals/Media** — Photos, screenshots, charts, and other visuals help engage the reader and keep them interested in your content. If you have visuals that we can include, please try to identify the highest resolution of the file possible (i.e., usually anything 150 dpi or greater works best) and we can work with you to adjust the image to an appropriate format and file size. Alternative text also must be provided for accessibility tools like screen readers.
- **Timing** — We generally try to post content within two weeks of your submission. Events are most successful when we post them four weeks out from the event date. So we ask that you take this into account before submitting an event. Videos from events are usually posted within a week after an event once closed captioning and other supporting information is available.

## What Our Readers Need

<div class="deck">Through our user research, we have found that there are three things product managers in government need to be successful in their work.</div>

### Tools and Resources

This information is crucial to modernizing services and much of it is government-specific, dealing with the various rules, regulations and policies.

Access to the right tools and resources will help them confidently take steps toward working smarter, iterating more frequently and delivering better, more effective services to the public.

**Some examples**

- [A resource page that explains how to do something]({{< ref "how-to-prevent-security-certificates-from-expiring-during-shutdown.md" >}})
- [A template for a much needed, common document]({{< ref "digital-governance-policies.md" >}})
- [A link to a helpful guide that your agency relies upon](https://accessibility.18f.gov/)

### Examples of problems being solved in government

Examples of other agencies’ success are some of the most powerful tools toward convincing colleagues to follow modern practices.

They want more information that is specific to government — examples of what agencies are doing; case studies; collections of validated federal-wide news that has an impact on digital in one spot.

**Some examples**

- [A link to a blog post](https://revenuedata.doi.gov/blog/journey-mapping/)
- [A blog post from an agency]({{< ref "2019-06-13-building-trust-with-users-through-open-communication-feedback.md" >}})
- [An explainer in a blog post]({{< ref "2014-07-07-user-experience-ux-vs-customer-experience-cx-whats-the-dif.md" >}})
- [An explainer over video]({{< ref "2019-04-24-dap-learning-series-using-advanced-analysis-tool.md" >}})

## Start Collaborating

**Here are some ways to start collaborating**

- Get in touch with us by emailing [digitalgov@gsa.gov](mailto:digitalgov@gsa.gov)
- [Join a community of practice]({{< ref "/communities/_index.md" >}})
- Get in touch with us by emailing [info@wegov.nyc](mailto:info@wegov.nyc)
- [Subscribe to our newsletter]({{< ref "/about/subscribe.md" >}})

This guidance stems from qualitative user research we conducted with over nearly two dozen federal members of our audience — content managers, designers, developers, innovation leaders — who are involved with all aspects of agencies’ digital services.

As we found in listening to them, they are working against incredible odds, and yet continuously exhibit a desire to be resourceful, perseverant, and resilient. We should all be proud to call them civil servants. :heart: