-
Notifications
You must be signed in to change notification settings - Fork 3
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
ffd00a2
commit ea2ada8
Showing
41 changed files
with
1,035 additions
and
68 deletions.
There are no files selected for viewing
27 changes: 27 additions & 0 deletions
27
...dules/custom/default_content_config/content/file/0ec3708e-1d2d-4879-8f4c-04145eb83b3a.yml
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 |
---|---|---|
@@ -0,0 +1,27 @@ | ||
_meta: | ||
version: '1.0' | ||
entity_type: file | ||
uuid: 0ec3708e-1d2d-4879-8f4c-04145eb83b3a | ||
default_langcode: en | ||
default: | ||
uid: | ||
- | ||
target_id: 1 | ||
filename: | ||
- | ||
value: kaufmann-404-page-spike.png | ||
uri: | ||
- | ||
value: 'public://2024-10/kaufmann-404-page-spike.png' | ||
filemime: | ||
- | ||
value: image/png | ||
filesize: | ||
- | ||
value: 161774 | ||
status: | ||
- | ||
value: true | ||
created: | ||
- | ||
value: 1729710809 |
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
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
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
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
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
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
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
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
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
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
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
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
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
Binary file added
BIN
+158 KB
web/modules/custom/default_content_config/content/file/kaufmann-404-page-spike.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
28 changes: 28 additions & 0 deletions
28
...ules/custom/default_content_config/content/media/48556cac-53e4-4f0e-85c9-b44cd9867296.yml
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 |
---|---|---|
@@ -0,0 +1,28 @@ | ||
_meta: | ||
version: '1.0' | ||
entity_type: media | ||
uuid: 48556cac-53e4-4f0e-85c9-b44cd9867296 | ||
bundle: image | ||
default_langcode: en | ||
depends: | ||
0ec3708e-1d2d-4879-8f4c-04145eb83b3a: file | ||
default: | ||
status: | ||
- | ||
value: true | ||
uid: | ||
- | ||
target_id: 1 | ||
name: | ||
- | ||
value: kaufmann-404-page-spike.png | ||
created: | ||
- | ||
value: 1729710809 | ||
field_media_image: | ||
- | ||
entity: 0ec3708e-1d2d-4879-8f4c-04145eb83b3a | ||
alt: 'page spike' | ||
title: '' | ||
width: 844 | ||
height: 670 |
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
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
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 |
---|---|---|
|
@@ -5,8 +5,9 @@ _meta: | |
bundle: news | ||
default_langcode: en | ||
depends: | ||
c2eb37c0-02a5-4a36-90bc-a7039449b61b: media | ||
8c66bd6c-e163-46cd-b915-2575b5686eec: media | ||
e2e80683-d456-446a-acbd-a03ff409bf1d: node | ||
6bd8641f-84c6-4ddb-b8b2-9c076b017198: media | ||
95077128-6d33-4445-a48a-4ad8ebb7d9b3: node | ||
default: | ||
revision_uid: | ||
- | ||
|
@@ -31,32 +32,32 @@ default: | |
value: false | ||
body: | ||
- | ||
value: '<p><em>_Originally published on the [GSA blog](</em><u>https://www.gsa.gov/blog/2019/04/18/gsa-calls-on-federal-emerging-tech-leaders-to-form-rpa-community-of-practice</u><em>)_</em></p><p> </p><p>Emerging technologies are rapidly changing the way government and industry do business. In order to prepare for and fully leverage this technological revolution, GSA is forming a community of practice (CoP) for robotic process automation (RPA). The new RPA CoP will allow federal government leaders to explore opportunities, share ideas, and collaborate on how RPA can be effectively implemented in their respective agencies.</p><p> </p><p>[<strong>**Join the community »**</strong>]({{< ref "/communities/rpa-community.md" >}})</p><p> </p><p>The Executive Sponsors of the RPA CoP are GSA Chief Financial Officer Gerard Badorrek and GSA Technology Transformation Services (TTS) Director Anil Cheriyan. The CoP will be chaired by Ed Burrows of the GSA Office of the Chief Financial Officer (CFO).</p><p> </p><p>With the advancements in emerging technology, it’s important for the federal government to capitalize on technological solutions in order to obtain the benefits of cost-effectively automating manual, repetitive, and rule-based operations. Many agencies are currently piloting RPA or already have bots in production, but so much more can be learned, accomplished, and shared<span> </span>with the collective efforts of industry and government.</p><p> </p><p>In addition, RPA will advance agency missions by helping shift the federal workforce from low-value to high-value work, which supports the President’s Management Agenda, Cross-Agency Priority Goal 6. Other benefits include:</p><p> </p><p>- Re-engineering and improving processes as they are automated;</p><p>- Increasing the efficiency of existing operations;</p><p>- Completing more work with less resources (e.g., more frequent and timely processing, improved data quality through full reconciliation);</p><p>- Reducing costs over time by creating capacity to maintain quality of service and absorb new work requirements without the need for additional hiring;</p><p>- Reducing processing errors and labor costs related to rework, delays, and customer dissatisfaction; and,</p><p>- Reducing process cycle times and thereby improving service to internal customers, agency partners, and U.S. citizens.</p><p> </p><p>By creating a RPA CoP, the federal government can reduce duplication and streamline efforts to implement RPA across government to help advance agency missions today, and into the future. The GSA Office of the CFO will leverage the existing TTS CoP management capabilities and expertise to lead the RPA CoP.<span> </span>The CoP will mobilize federal RPA leaders to share information, define technical options, and outline best practices for implementation in order to accelerate operational achievements and the benefits of RPA.</p><p> </p><p>GSA looks forward to helping agency partners take important next steps to successfully implement RPA programs and strategically position the federal workforce to engage in higher value work to deliver on their mission.</p><p> </p><p>To learn more about how to get involved with the RPA CoP please contact [[email protected]](<u>mailto:[email protected]</u>).</p><p> </p><p> </p>' | ||
value: '<p>Lorem ipsum odor amet, consectetuer adipiscing elit. Dapibus facilisis tellus eleifend cras lectus diam efficitur. Porttitor aenean habitasse magna inceptos commodo litora. Magna fermentum sit phasellus taciti neque venenatis feugiat proin! Himenaeos nam leo hendrerit netus litora luctus porttitor? Congue <strong>habitasse</strong> faucibus habitasse nascetur sit. Dolor hac sagittis ligula vulputate; elit quisque mi tempor. Posuere penatibus vehicula orci suspendisse tortor netus nostra leo laoreet.</p><p>Cursus etiam metus sagittis ultricies, aliquet eget. Nostra euismod feugiat fames suspendisse hendrerit dapibus phasellus felis. Tempor tellus lacus convallis varius hac turpis. Pulvinar augue fusce accumsan suscipit molestie interdum augue porta. Consectetur maximus pulvinar ex curae nostra tellus nisi eu. Convallis mattis ex ullamcorper nisl neque mi torquent. Eros inceptos dis pretium lectus sem mus a. Faucibus proin luctus ultrices; vestibulum tincidunt rutrum.</p>' | ||
format: html | ||
summary: '' | ||
field_authors: | ||
- | ||
target_id: 15 | ||
entity: e2e80683-d456-446a-acbd-a03ff409bf1d | ||
field_deck: | ||
- | ||
value: 'The new community will explore opportunities, share ideas, and collaborate on how RPA can be effectively implemented in federal agencies' | ||
value: 'nulla iaculis ligula fames proin in <b>erat</b>' | ||
format: html | ||
field_featured_image: | ||
- | ||
entity: c2eb37c0-02a5-4a36-90bc-a7039449b61b | ||
entity: 6bd8641f-84c6-4ddb-b8b2-9c076b017198 | ||
field_kicker: | ||
- | ||
value: 'New Community' | ||
value: 'nulla iaculis ligula fames proin in <b>erat</b>' | ||
field_page_weight: | ||
- | ||
value: 1 | ||
field_primary_image: | ||
- | ||
entity: 8c66bd6c-e163-46cd-b915-2575b5686eec | ||
entity: 6bd8641f-84c6-4ddb-b8b2-9c076b017198 | ||
field_summary: | ||
- | ||
value: 'The new community will explore opportunities, share ideas, and collaborate on how RPA can be effectively implemented in federal agencies' | ||
value: 'nulla iaculis ligula fames proin in <b>erat</b>' | ||
format: html | ||
field_topics: | ||
- | ||
target_id: 13 | ||
entity: 95077128-6d33-4445-a48a-4ad8ebb7d9b3 |
41 changes: 41 additions & 0 deletions
41
...dules/custom/default_content_config/content/node/3c8c1a7b-5b5b-4196-b435-1fa57ff0230b.yml
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 |
---|---|---|
@@ -0,0 +1,41 @@ | ||
_meta: | ||
version: '1.0' | ||
entity_type: node | ||
uuid: 3c8c1a7b-5b5b-4196-b435-1fa57ff0230b | ||
bundle: resources | ||
default_langcode: en | ||
default: | ||
revision_uid: | ||
- | ||
target_id: 1 | ||
status: | ||
- | ||
value: true | ||
uid: | ||
- | ||
target_id: 1 | ||
title: | ||
- | ||
value: 'An introduction to accessibility' | ||
created: | ||
- | ||
value: 1729705485 | ||
promote: | ||
- | ||
value: false | ||
sticky: | ||
- | ||
value: false | ||
body: | ||
- | ||
value: '<p><strong>## What is accessibility?</strong></p><p> </p><p>In the federal government, accessibility means that agencies must give disabled employees and members of the public access to information comparable to the access available to others.</p><p> </p><p>Familiarize yourself with [Section508,gov](<u>https://www.section508.gov/</u>), and read this deeper dive on [understanding accessibility in government](<u>https://digital.gov/resources/an-advanced-approach-to-accessibility/</u>) to gain a solid foundation on accessibility in the federal space.</p><p> </p><p>Accessibility must be considered throughout design, development, content creation, and maintenance of digital assets. It’s much easier to build accessibility in from the start, than to remediate something after it’s already built. Some of the most common accessibility issues we see on federal websites include:</p><p> </p><p>- <strong>**Missing ALT text**</strong> - Always add descriptive ALT (alternative) text to images, so screen reader software can convey the meaning of an image, even if someone can’t see it.</p><p>- <strong>**Lack of structure**</strong> - When creating content, use document styles to organize content and properly tag headings, which will make it easier for screen reader software to navigate through a document or web page.</p><p>- <strong>**Insufficient color contrast**</strong> - Follow the [U.S. Web Design System (USWDS) guidance on color](<u>https://designsystem.digital.gov/utilities/color/</u>) to ensure sufficient contrast between text and background colors.</p><p>- <strong>**Content quality**</strong> - Write concisely and clearly using [plain language](<u>https://digital.gov/resources/an-introduction-to-plain-language</u>), and put the most important information at the top of the page.</p><p> </p><p>Automated testing can find some accessibility issues, but only manual testing will catch everything, so use your agency’s standard testing tool and follow the [Section 508 ICT Testing Baseline](<u>https://ictbaseline.access-board.gov/</u>) to test all code and content before publication. Using this testing baseline ensures you address access to information and communication technology (ICT) under Section 508 of the Rehabilitation Act and Section 255 of the Communications Act.</p><p> </p><p><strong>## Why is accessibility important?</strong></p><p> </p><p>To meet our mission and serve the public, we must provide accessible resources, both physical and digital. Section508.gov offers many [practical reasons for digital accessibility](<u>https://www.section508.gov/manage/benefits-of-accessibility/</u>).</p><p> </p><p>Accessibility is not only the right thing to do, it’s also the law. Under [Section 508 of the Rehabilitation Act of 1973](<u>https://www.section508.gov/manage/laws-and-policies/</u>), as amended in (29 U.S.C § 794d), federal agencies must build websites and digital services that conform to the [Revised 508 Standards](<u>https://www.access-board.gov/guidelines-and-standards/communications-and-it/about-the-ict-refresh/final-rule/text-of-the-standards-and-guidelines</u>).</p><p> </p><p>Following accessibility guidelines often also leads to improvements in [usability](<u>https://digital.gov/topics/usability/</u>) as well. This means your websites and digital services will work better, not only for those with disabilities, but for everyone. Promote accessibility at your agency by:</p><p> </p><p>- Designing accessible experiences</p><p>- Following accessibility standards</p><p>- Testing against the [Section 508 ICT Testing Baseline](<u>https://ictbaseline.access-board.gov/</u>)</p><p>- Conducting inclusive [research](<u>https://digital.gov/topics/research/</u>) and welcoming feedback</p><p>- Learning more about accessibility by watching [Digital.gov videos](<u>https://www.youtube.com/playlist?list=PLd9b-GuOJ3nFHykZgRBZ7_bzwfZ526rxm</u>) and [attending training](<u>https://www.section508.gov/training/</u>)</p><p> </p><p><strong>## What can I do next?</strong></p><p> </p><p>Federal agencies are required to provide an accessibility statement. GSA’s Government-wide IT Accessibility Program also encourages all digital product owners to include information about an organization’s commitment towards providing equal access to information.</p><p> </p><p>Visit Section508.gov to learn how to [develop a website accessibility statement](<u>https://www.section508.gov/manage/laws-and-policies/website-accessibility-statement/</u>), including why you should publish a statement, what to include, and where to publish it.</p><p> </p><p> </p>' | ||
format: html | ||
summary: '' | ||
field_deck: | ||
- | ||
value: 'Understand how to approach accessibility for all' | ||
format: html | ||
field_summary: | ||
- | ||
value: 'An overview of how to design and deliver accessible digital products and services in the federal government' | ||
format: html |
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
Oops, something went wrong.