-
Notifications
You must be signed in to change notification settings - Fork 9
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
heading oddity #42
Comments
@rbbeeston Yes, we need to eliminate (or move) styles from website-v2 For this specific use case, here are the lines we're using to target the library readmes. Thankfully there's not a lot, so this would be a great place to start: https://github.com/boostorg/website-v2/blob/develop/frontend/styles.css#L99-L156 |
Either one of you is fine, it's a small item, however we may want to try to either merge and/or remove that CSS completely from any boostlook styling, as it's only going to conflict. I don't want that to slow down Chrissy from what she's doing, as this is more of a maintenance task than a styling one. So if you have the bandwidth to look at it, then go ahead, otherwise it can go to her. |
Roger that, I'm on it! |
Noticed this in the "Any" library h1 header on stage. Seems like
#LibraryReadMe h1 a
was throwing it off with thefloat:right
, can you take a look?It should be at the top and left justified.
The text was updated successfully, but these errors were encountered: