ec0abe052 Update index.md ed44339cd Update bio.md cef04eb95 Minor edits 4d45dcc8d Submitting Digital.gov to the Hugo Showcase d35126af7 Azure uses storage containers, not buckets; edited accordingly. (#1078) 9c249cc89 fix grammatical error 9728699a3 Release Hugo 0.69.2 cccabed0c Merge branch 'temp692' 3d0a740c4 releaser: Add release notes to /docs for release of 0.69.2 b760aceb1 HTTPS external links in docs 49e4631b0 Release 0.69.1 01f3da870 Merge branch 'temp691' 8280d85aa releaser: Add release notes to /docs for release of 0.69.1 40ea44d24 fix typo (#1088) 725f53643 Rebuild cache 80ee1efd9 Add KeyCDN Showcase f253e906e docs: Fix typo in Hugo's Security Model b3ffd1ad3 Mentioning a range is equivalent to foreach (#1086) 0c396911f Update jsonify function docs 376befc9a Fix typo (#1084) 4bdc9bc72 Mark .Page.UniqueID as deprecated and add .File.UniqueID 30a7b7bf2 Update hosting-on-github.md c5db4ba2b Update postprocess.md 1121f74a5 Update install guide with Scoop extended 8988aa6fa Merge branch 'postprocess' 225d3f9c7 Release Hugo 0.69.0 4caf7a89a releaser: Add release notes to /docs for release of 0.69.0 664b2a0fa Document resources.PostProcess and buildStats 9737b34e9 docs: Regen docs helper 0fab3ba24 Merge commit 'da3c3e5fbd0de65f956618cd2e35401460a3cd02' 96dad83b1 Update hosting-on-aws-amplify.md 57eb27897 Merge commit 'c494c37a4523fbf2db6274dc87e0877fd5bec24b' dcc7afef7 fix typo in getting started git-subtree-dir: docs git-subtree-split: ec0abe052bcfebc65c323df4ff14ad277bb405d8
5.1 KiB
title | date | description | siteURL | siteSource |
---|---|---|---|---|
Digital.gov | 2020-05-01 | Showcase: "Guidance on building better digital services in government." | https://digital.gov/ | https://github.com/gsa/digitalgov.gov |
For over a decade, Digital.gov has provided guidance, training, and community support to the people who are responsible for delivering digital services in the U.S. government. Essentially, it is a place where people can find examples of problems being solved in government, and get links to the tools and resources they need.
Through collaboration in our communities of practice, Digital.gov is a window into the people who work in technology in government and the challenges they face making digital services stronger and more effective. Read more about our site »
Digital.gov is built using the U.S. Web Design System (USWDS) and have followed the design principles in building out our new site:
- Start with real user needs — We used human-centered design methods to inform our product decisions (like qualitative user research), and gathered feedback from real users. We also continually test our assumptions with small experiments.
- Earn trust —We recognize that trust has to be earned every time. We are including all required links and content on our site, clearly identifying as a government site, building with modern best practices, and using https.
- Embrace accessibility — Accessibility affects everybody, and we built it into every decision. We’re continually working to conform to Section 508 requirements, use user experience best practices, and support a wide range of devices.
- Promote continuity — We started from shared solutions like USWDS and Federalist. We designed our site to clearly identify as a government site by including USWDS’s .gov banner, common colors and patterns, and built with modern best practices.
- Listen — We actively collect user feedback and web metrics. We use the Digital Analytics Program (DAP) and analyze the data to discover actionable insights. We make small, incremental changes to continuously improve our website by listening to readers and learning from what we hear.
More on the USWDS maturity model »
Open Tools
We didn’t start from scratch. We built and designed the Digital.gov using many of the open-source tools and services that we develop for government here in the Technology Transformation Services (TTS).
Using services that make it possible to design, build, and iterate quickly are essential to modern web design and development, which is why Federalist and the U.S. Web Design System are such a great combination.
Why Hugo? Well, with around ~3,000
files (and growing) and ~9,000
built pages, we needed a site generator that could handle that volume with lightning fast speed.
Hugo was the clear option. The Federalist team quickly added it to their available site generators, and we were off.
At the moment, it takes around 32 seconds
to build close to ~10,000
pages!
Take a look:
| EN
-------------------+-------
Pages | 7973
Paginator pages | 600
Non-page files | 108
Static files | 851
Processed images | 0
Aliases | 1381
Sitemaps | 1
Cleaned | 0
Built in 32.427 seconds
In addition to Hugo, we are proudly using a number of other tools and services, all built by government are free to use:
- Federalist
- Search.gov — A free, hosted search platform for federal websites.
- Cloud.gov — helps teams build, run, and authorize cloud-ready or legacy government systems quickly and cheaply.
- Federal CrowdSource Mobile Testing Program — Free mobile compatibility testing by feds, for feds.
- Digital Analytics Program (DAP) — A free analytics tool for measuring digital services in the federal government
- Section508.gov and PlainLanguage.gov resources
- API.data.gov — a free API management service for federal agencies
- U.S. Digital Registry — A resource for confirming the official status of government social media accounts, mobile apps, and mobile websites.
Questions or feedback? Submit an issue or send us an email to digitalgov@gsa.gov ❤️