forked from 18F/18f.gsa.gov
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request 18F#2178 from 18F/gboone-patch-2
changes email url to a mailto
- Loading branch information
Showing
1 changed file
with
3 additions
and
3 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -26,7 +26,7 @@ We’re also going to continue talking to users to find more opportunities to sh | |
|
||
## Designing further for flexibility | ||
|
||
Now that we have a good baseline of website components (for example typography, headers, footers), we’re also going to focus on building more complex components. We’ll be taking on the deeper layers of government sites and applications, such as more complex forms and data applications, to get a better understanding of the public’s pain points in using them. In preparation for this work, we’re looking for agencies that are interested in partnering with us on custom development and research to solve their design and user experience challenges. We’ll then take the work from these partnerships and build it back into the platform and share it with all of government. If you’re an agency that’s interested in partnering with us, please get in touch with us at [[email protected].]([email protected]) | ||
Now that we have a good baseline of website components (for example typography, headers, footers), we’re also going to focus on building more complex components. We’ll be taking on the deeper layers of government sites and applications, such as more complex forms and data applications, to get a better understanding of the public’s pain points in using them. In preparation for this work, we’re looking for agencies that are interested in partnering with us on custom development and research to solve their design and user experience challenges. We’ll then take the work from these partnerships and build it back into the platform and share it with all of government. If you’re an agency that’s interested in partnering with us, please get in touch with us at [[email protected].](mailto:[email protected]) | ||
|
||
## Preparing government for the future, mobile majority | ||
|
||
|
@@ -45,6 +45,6 @@ To do this, we need partners with interesting government challenges to help us b | |
- Building custom components for your agency that might benefit other agencies (such as more complex input forms, maps, data visualizations and data structures, email templates, etc.) | ||
- Have feedback or ideas on how we can improve the Draft Standards | ||
|
||
If you’d like to talk to the team or explore a partnership, please contact us at [[email protected]]([email protected]) | ||
If you’d like to talk to the team or explore a partnership, please contact us at [[email protected]](mailto:[email protected]) | ||
|
||
We’re from the government, and we’re here to help. | ||
We’re from the government, and we’re here to help. |