Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make the Editor appear more like GSA websites. #327

Open
3 tasks
danid123 opened this issue Feb 9, 2022 · 5 comments
Open
3 tasks

Make the Editor appear more like GSA websites. #327

danid123 opened this issue Feb 9, 2022 · 5 comments
Assignees
Labels
editor tool Related to the editor tool specifically user interface Any OpenACR UI

Comments

@danid123
Copy link

danid123 commented Feb 9, 2022

Styling changes:

  • Change fonts
    font-family: Public Sans Web, -apple-system, BlinkMacSystemFont, Segoe UI, Roboto, Helvetica, Arial, sans-serif, Apple Color Emoji, Segoe UI Emoji, Segoe UI Symbol;

  • Change font sizes to match GSA styles

  • Change nav bar styling to show a blue bar under the current page
    Note: for this one I'm not sure if we should keep the dark blue/light blue colors we have for our website that matches GSA websites or switch to the white with green bar colors that Section508 uses. I think the GSA colors have greater contrast. @mgifford what do you think?

@danid123 danid123 added the editor tool Related to the editor tool specifically label Feb 9, 2022
@danid123 danid123 added the user interface Any OpenACR UI label Feb 9, 2022
@danid123
Copy link
Author

danid123 commented Feb 9, 2022

mock to compare and contrast
Editor-valid-report-dark
Editor-valid-report-light

@mgifford
Copy link
Collaborator

mgifford commented Feb 9, 2022

I think that's way cleaner.. Looks great to me.

I think we can go with what Section508.gov uses. Just needs to have sufficient contrast.

@dmundra
Copy link
Collaborator

dmundra commented Feb 9, 2022

Hi @danid123 I have two tickets in the backlog to replace W3C WAI stylesheet (#225) and add USWDS stylesheet (#226). I think we can close those tickets and bring requirements to this ticket.

That being said this will also need priority because I estimate it will be a good amount of work to replace the stylesheets and we might not able to do it in this option.

What do you think? We could do smaller incremental changes but it is probably best to do one big change.

@danid123
Copy link
Author

danid123 commented Feb 9, 2022

@dmundra that sounds like a good plan. One big change is probably also easier for testing.

@dmundra dmundra added this to the Option 2 - Sprint 3 milestone Feb 10, 2022
@dmundra
Copy link
Collaborator

dmundra commented Feb 10, 2022

@dmundra dmundra removed this from the Option 2 - Sprint 3 milestone Feb 15, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
editor tool Related to the editor tool specifically user interface Any OpenACR UI
Projects
None yet
Development

No branches or pull requests

3 participants