We need to improve the custom font token documentation, as it is currently only in the setting file itself. This leaves little room for good examples and writing. We've promised better docs for this since 2.0 and still haven't delivered.

https://designsystem.digital.gov/design-tokens/typesetting/font-family/

<img width="722" alt="Screen Shot 2020-02-07 at 11 20 14 AM" src="https://user-image

An increasing number of GSA APIs are normalizing around the user of this opensource API template.

It'd be very easy to stand up an new instance for the CKAN API and use it for

Feature

We would like to have better documentation on how to create good open source software documentation as guidance for Department organizations wishing to open source things. This should include things like relevant sections of a "contributing" doc (not just a link to an example), how to write and review PRs, good commit messages, how to write a good GH issue, etc.

Page(s) Affecte

For consideration:

Headings (hx) should be used to wrap the accordion triggering button. This would align with the recommendations of the ARIA 1.1 Practices Guide. The heading level as the first element in the <section>s will also align to the recommendations for the <section> element in the HTML 5.1 W3C Recommendation.

Accordion (Sections With Show/Hide Functionality)
https://www.w3.or

A user on support was advise to update their prototype gradually, version by version (eg, 6 > 7 > 8 > 9 > latest). However, we don't explain how to do this, or where to get those earlier releases from.

For instance, if View Multiple Documents is checked, they move to the 3rd column:

Which is notionally

<table><tbody>
  <tr>
    <td>Date Filed</td>
    <th>#</th>
    <td><small><a href="#" onclick="uncheckAll(doc

Describe the bug
Core is using a version of react-aria-modal which has an open issue to fix using componentWillMount method. This is currently deprecated.

Track the progress of that component here: davidtheclark/react-aria-modal#93 to know when to update appropriately.

The major.minor.patch concept is clear, but what does the part after the dash indicate?

I believe it's one of these:

• major.minor.patch-commit
• major.minor.patch-buildnumber

It's to me what convention @tomschenkjr was using. I see some big numbers which would seem like commits, but I know that the CRAN submission process can be challenging and it could be actual builds.

Either wa

What

Feedback from the cross-government working group following publication of 'Help users to understand the impact of an emergency on your service' to add single quotation marks when we reference page names.

Although feedback is for the emergency banner pattern this would also apply to all content on th

See https://gist.github.com/thisisdano/7c6f117da94a3b89f7d4ecabe77a8c92 for some draft instructions on using Sass and Gulp to include only the USWDS core design language (tokens, mixins, and functions) into a project.

– Search results: it should be ordered by relevance and descending vitality
– Software page: it should be ordered randomly
– Home page: it should be ordered randomly
– Public entity page: it should be ordered alphabetically

Description

In preparation of reviving the engineering onboarding session, refine goals of and needs of engineering onboarding and revamp the materials for the Caseflow Technical System Overview.

• Previous deck: https://docs.google.com/presentation/d/1D7yYubzwYPc2ctBQJmUJbQM9_wqWSh4PRu_bL-POtb8/edit#slide=id.p
• Previous recording from Aug 2019: https://zoom.us/rec/share/6shpcLf--0pIRJWQ2

Having a verbose toggle inside your local settings will help us with debugging and makes issues inside continues integration remotes easier to debug as well.

Need to clarify that the Text File Output may need to be modified to eliminate "File", "DatasetID", "ControlFile", and "File_to_Geocode" fields that can get added when using "Add All" in Pentaho/Kettle.

Need to revise this page.

This is a great project and looks and works well! It would be helpful if the Esc key could be used to collapse an expanded main menu item when on the full width (desktop) version of the site. It currently works for the mobile version of the menu but not full width.

Example:
<img width="330" alt="Screen Shot 2019-06-11 at 11 04 06 AM" src="https://user-images.githubusercontent.com/1154685/59295

What seems to be the problem (1 sentence)

Folks should be entering their Linkedin username only on author pages. Not the whole URL. Need to scan the site and check for author pages that include "http" in the Linkedin value.

example: https://digital.gov/authors/bridget-fields/

Ensure new starter can create new component by following the step by step guide. Consult GG for clarification if necessary.

Ensure the content does not duplicate content maintained by an authoritative source:

• Conducting regular audits to identify and remove redundant or outdated content
• Linking to authoritative sites instead of recreating similar content
• Notifying visitors when a link takes them to sites that may not operate under the same laws, regulations, and policies as federal websites