kylehalleman / covid19inwi Goto Github PK

Hey yall, could you update the link to WeCountCOVID19.com, directly? We just published our new website, so please send people there.

Perhaps the following?

WeCountCOVID19.com is a grassroots survey of anyone who is possibly sick with coronavirus. If you're sick, please visit the website to take the anonymous 5-minute survey to help understand what and where the symptoms of COVID-19 are. The website also provides data analysis reports of the survey results that are available for anyone to view. This is a joint effort from members of Code for Milwaukee and UW-Milwaukee's School of Public Health.

As the list of links grows, frequent visitors should have a way to see what is new.

https://www.covid19inwi.com/contribute.html does not seem to work (for me)

I also echo #15 : would be great to "create more welcoming/inviting language to have people contribute on Github"

For anyone to catch up on the purpose and dialogues that has gone on thusfar in this work

https://digitalpublicworks.com/projects/49268a4d-1067-4a84-8f97-c15a2ff91dc7

Issue is meant to remain open

Richie Burke, host of Gogedders, is cool with us embedding the audio of this episode on the assitance page. I'm thinking it can go above "How to help" here

https://medium.com/@greggish/introducing-the-principles-of-equitable-disaster-response-89f0e2b44de9

This will be an omnibus ticket to collect thoughts and feedback shared during the Code for Milwaukee session.

The site currently uses a very minimalist theme based off of a small CSS project I made. I chose this because it has strong legibility, minimal footprint, and by using element selectors promotes accessibility (the color palette for both the light and dark themes also passes WCAG 2.1). It also includes a dark mode based on a user's OS settings.

Some updates to the site might be needed to further our goals for the site. I would only ask any updates stay inline with the following design goals.

Design goals

• Accessible: color palette should pass WCAG 2.1 AA and semantic HTML should be used for any interface patterns.
• Responsive: should pass WCAG 2.1 1.4.10 (Reflow).
• Performant: unless a good case is made, I do not see the need in adding web fonts, JavaScript, or excessively large images.

This design was shared with me by volunteer Erin Paasch. I'd like to start implementing it.

A few things to note/consider:

• Given the constraints of translating from Markdown to HTML, the link text can be the larger blue font, and the description text would be anything not a link in the same bullet point.
• Not sure if we'll be able to make the entire rectangle the link in this case
• Not sure how to handle nested lists in this scenario.
• I feel the table of contents is still useful, would need to figure a way to keep it in here.

Going to start implementing this on a branch and maybe some of these issues will resolve themselves as I work on it 🙂.

Rec: make the "Covid-19 in Wisconsin" header clickable back to the homepage

Specific page recs:
Milwaukee Responds to Covid-19 -
1.) the monotony of the layout of the words on this page makes it very overwhelming to look at and understand
Rec: have drop downs for each section so you click on the heading and then all of the bullets show up
2.) if you click on almost any of the other top links it creates a 404 error and the only way to get out is to remove /old/ from the url

General information and data - broken link

How to get help & How to help - more manageable but still monotonous and overwhelming

How to contribute to this resource - create more welcoming/inviting language to have people contribute on Github

Questions to consider:

• can there be some pictures/icons/something to make the UI a little better?
• is this ada compliant?
• could you add a search bar to make all of the content more manageable/findable?

1. Someone manage social media for the project and highlighted a project or 2 twice a day

2. Light UI/UX work to improve flow of site.