OpenFreeEnergy / OpenFreeEnergy/openfreeenergy.github.io

CSS Issues

Open
#23 0 comments 0 reactions 2 assignees View on GitHub

@atravitz is already working on this.

Since Mar 24, 2025.

Dominant language
HTML
Stars
2
Forks
3
Avg merge
6h 59m
Merged PRs (30d)
2

Description

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.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.