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

CSS Issues #23

Open
1 of 10 tasks
dwhswenson opened this issue Apr 8, 2022 · 0 comments
Open
1 of 10 tasks

CSS Issues #23

dwhswenson opened this issue Apr 8, 2022 · 0 comments

Comments

@dwhswenson
Copy link
Member

dwhswenson commented Apr 8, 2022

I'm using this issue to collect a few things that where we should eventually tweak the CSS to look better. This isn't high priority stuff, but if someone feels like taking a break from real coding to play with CSS for an hour or so, you can probably get some of these fixed.

Slightly important issues:

  • Hover transition on Read More links (News page): Until hover, the buttons use our color scheme. On hover, the transition reverts it to the old base theme color (solved in #24)
  • Links (in other-blue) are insufficiently distinct from the text. I tried increasing line weight; it seemed like overkill. Maybe a dashed underline would do it?

Very minor issues:

  • index page, OMSF banner: link is an unofficial color (but we might have to select something from outside the official set)
  • footer: links are unofficial color
  • Team page: GitHub icons aren't styled to match the link color
  • Team page: Names aren't styled according to our color scheme. Our names should be in badass-blue (obviously!)
  • Team page: blurb should probably have some spacing before it starts
  • News page Blog post h3 titles in li use the wrong font (this is a bug in the original theme)
  • Tags for news items: not using official colors. At least background should be either sandy Sergio or Sergio's cousin
  • Tags for news items: Forcing first-letter upper is wrong. These should be all-lower (this is a theme layout issue).

None of these should be considered blockers. They're just relatively low-hanging fruit that we can deal with whenever we have time.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant