xdgov / mlbias Goto Github PK

POCs for Use Case Content

• Zach use case
• Christain use case
• Tiffany use case

Content

• How bias was found
• What measures were taken to remediate

Choose a word for the navigation / URL slug that encompasses what this page is so that it can be referenced in calls to action and the website's navigation.

Per a conversation with @s-hosseini and @katemccallkiley1, I'd like to advocate for an alternative flow that may actually help to simplify the Resources UX.

Essentially the Resources page could serve as a master list of Resources by default. This list becomes optionally filtered by answers to the questionnaire, which is not listed here by default but linked to in a CTA card at the top of the page. Resources are then filtered based on responses to the questionnaire.

Fundamentally, the sharing features, profile self assessment, and listing of resources appears similar but this approach could simplify the flow considerably and open the door to future filter and sorting features. I'll share a mock here before EOD.

@lukad03 to review images taken from prototype background, and cut and pasted at the top of GIthub markdown pages and readme, and suggest alternatives (low-priority)

Current design doesn't highlight that the options are clickable. Propose converting the design to use more traditional (but stylized) HTML elements for improved user friendliness.

@s-hosseini add header tags to every page

Add template(s) for contributing issues and pull requests.

Get approval from ADRM to launch.

Send website to CNMP for content review. Anthony should be POC for this. Contingent on pre-launch checklist being mostly complete.

Wondering how we might develop a process for tagging resources while also supporting Markdown files. Jekyll comes to mind with regards to support for assigning attributes. Is this something we should handle at the Markdown level or outside of it, i.e. each Resource is listed as an object with a link to the content that is in a Markdown file. Example:

{
name: "Resource Name",
tags: "models", "build",
content: ".../build/resource-name.md"
}

Homepage

• Determine if there's a way to make the banner look less rigid / dated
• Image feels inappropriate for the work. Should be swapped for something else - perhaps more abstract or more discernible
• xD logomark should be removed. Make a new one?
• Be consistent with product naming here and in banner
• Convert "Featured Resources" heading to serif font
• Use plain language for card links with arrows, similar to buttons (i.e. "Learn More >" or individualized action text)
• Button hover results in uneven arrow
• Card arrows appear off center
• Add header with 'this is an alpha' language

Footer

• Consider adding U.S. Census Bureau logo to footer
• Add Privacy and Accessibility links to footer
• Consider adding "10x funded project" to footer

Quiz

• Feels abrupt when you land here. Could benefit from primer text
• Typography feels inconsistent with other areas of the site (bigger).
• Button active state should change. Highlight purple border and text with no background instead?
• Checkmarks in progress bar use colors and line-weight inconsistent with other areas of the site.
• Last "Next" button should indicate this is the last step, i.e. "See Results" or something to that effect
• Questions should be in serif font

Resources Index

• Quiz CTA tag should have a color other than white

General Feedback

• Find ways to make design less stale, more visual, without photo elements

Case Study Content

• Autocoding
• Imbalances in reporting
• Bias in computer vision for user authentication

Build Content

• Thing One
• Thing Two
• Thing Three

Journey Content

• Thing One
• Thing Two
• Thing Three

Website Views

• Case Study View
• Resources View
• Journey View
• Homepage View
• Quiz View
• Add Agency Logos - Issue #6

Marketing

• Draft comms plan
• Brief stakeholders on comms plan
• Send comms one pager to stakeholders for launch day

Website Infrasctructure

• Meet with Federalist Team
• Content Approval - Issue #19
• Secure subdomain from TCO - Issue #2
• Point subdomain to Federalist

Pending approval from CNMP for content.

• Determine POC for securing subdomain
• Determine if subdomain can be secured prior to launch
• Work with relevant parties to secure subdomain
• Ensure subdomain is properly connected to Federalist

Determine where to add Agency logos (DoC?, Census)

Create a space on the site to contextualize agency contributions, ownership, etc.

@s-hosseini add page on open and free Courses to the repo

Add email address to website to field inquiries for expertise, new use cases, etc.

GitHub Maintenance

• Clean up issues
• Add templates for issues and contributing - Issue #4
• Determine deployment flow w/ ADCOM

@s-hosseini to add file hierarchy/naming convention to contribute file to help those hoping to contribute to understand our file and naming logic