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

Styling adjustments to footer text #1364

Merged
merged 1 commit into from
Jul 3, 2021
Merged

Styling adjustments to footer text #1364

merged 1 commit into from
Jul 3, 2021

Conversation

trvrb
Copy link
Member

@trvrb trvrb commented Jun 30, 2021

Description of proposed changes

This is a simple update to the CSS styling of the page footer specified in footer.js. This is motivated by display of long Markdown description in open builds. Here is resulting display prior to this update:

before

And here is the resulting display after this update:

after

I don't think the main paragraph text was ever meant to be slightly bold. It has font-weight: 300 specified under FooterStyles. However, because it wasn't specified under p the main paragraph text was getting set as font-weight: 400.

I borrowed the font sizing in the section headers from bedford.io, where I preferred to give more of a dynamic range compared to default CSS. In this case, I thought the ##### to be much too large without providing the styling.

Testing

Tested locally.

@trvrb trvrb requested a review from jameshadfield June 30, 2021 01:57
@jameshadfield jameshadfield temporarily deployed to auspice-footer-styling-suhrwve June 30, 2021 01:57 Inactive
@trvrb
Copy link
Member Author

trvrb commented Jul 1, 2021

Nextstrain.org deployment looks like it worked as expected: https://nextstrain-s-auspice-pr-6i41bz.herokuapp.com/ncov/global?dmin=2021-05-17&r=division

@trvrb trvrb merged commit 00a8e81 into master Jul 3, 2021
@trvrb trvrb deleted the footer-styling branch July 3, 2021 17:53
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

Successfully merging this pull request may close these issues.

2 participants