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

getting-started.md code blocks are white-on-white #1715

Closed
andrewdavidwong opened this Issue Feb 2, 2016 · 8 comments

Comments

Projects
None yet
3 participants
@andrewdavidwong
Member

andrewdavidwong commented Feb 2, 2016

Here's a screenshot:
1

(I highlighted the first four lines of the first code block to show that there's actually text there.)

CC @bnvk

@andrewdavidwong andrewdavidwong added this to the Documentation/website milestone Feb 2, 2016

marmarek added a commit to QubesOS/qubesos.github.io that referenced this issue Feb 3, 2016

Revert "Change highlighter to rouge to suppress page build warning"
This reverts commit 76ca7a3.

While according to the github documentation, it shouldn't matter,
apparently it does and renders code sections white on white.

QubesOS/qubes-issues#1715
@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Feb 3, 2016

Member

I've reverted change suggested by github docs, but it didn't fixed anything. @bnvk any idea? Maybe some github pages change? I don't remember having github page build warning before, so maybe it have something to do here. The warning:

Subject: [QubesOS/qubesos.github.io] Page build warning

The page build completed successfully, but returned the following warning:

You are attempting to use the 'pygments' highlighter, which is currently unsupported on GitHub
Pages. Your site will use 'rouge' for highlighting instead. To suppress this warning, change the
'highlighter' value to 'rouge' in your '_config.yml'. For more information, see
https://help.github.com/articles/page-build-failed-config-file-error/#fixing-highlighting-errors
.

GitHub Pages was recently upgraded to Jekyll 3.0. It may help to confirm you're using the
correct dependencies:

  https://github.com/blog/2100-github-pages-now-faster-and-simpler-with-jekyll-3-0

For information on troubleshooting Jekyll see:

  https://help.github.com/articles/using-jekyll-with-pages#troubleshooting

If you have any questions you can contact us by replying to this email.
Member

marmarek commented Feb 3, 2016

I've reverted change suggested by github docs, but it didn't fixed anything. @bnvk any idea? Maybe some github pages change? I don't remember having github page build warning before, so maybe it have something to do here. The warning:

Subject: [QubesOS/qubesos.github.io] Page build warning

The page build completed successfully, but returned the following warning:

You are attempting to use the 'pygments' highlighter, which is currently unsupported on GitHub
Pages. Your site will use 'rouge' for highlighting instead. To suppress this warning, change the
'highlighter' value to 'rouge' in your '_config.yml'. For more information, see
https://help.github.com/articles/page-build-failed-config-file-error/#fixing-highlighting-errors
.

GitHub Pages was recently upgraded to Jekyll 3.0. It may help to confirm you're using the
correct dependencies:

  https://github.com/blog/2100-github-pages-now-faster-and-simpler-with-jekyll-3-0

For information on troubleshooting Jekyll see:

  https://help.github.com/articles/using-jekyll-with-pages#troubleshooting

If you have any questions you can contact us by replying to this email.

marmarek added a commit to QubesOS/qubesos.github.io that referenced this issue Feb 3, 2016

Revert "Revert "Change highlighter to rouge to suppress page build wa…
…rning""

This reverts commit 0bd1b02.
That was correct commit. The whole issue is caused by github pages
update (to jekyll 3.0).

QubesOS/qubes-issues#1715
@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Feb 3, 2016

Member

And reverted the revert... Github pages really force rouge highlighting, and indeed this (together with jekyll update?) breaks code blocks. It is described in blog post linked in the warning message.

Member

marmarek commented Feb 3, 2016

And reverted the revert... Github pages really force rouge highlighting, and indeed this (together with jekyll update?) breaks code blocks. It is described in blog post linked in the warning message.

@bnvk

This comment has been minimized.

Show comment
Hide comment
@bnvk

bnvk Feb 3, 2016

Yah, definitely caused the change to rouge instead of pygments seems to be something with how the differing highlighters generate the CSS. Anywho I just submitted a pull request to fix this!

bnvk commented Feb 3, 2016

Yah, definitely caused the change to rouge instead of pygments seems to be something with how the differing highlighters generate the CSS. Anywho I just submitted a pull request to fix this!

@andrewdavidwong

This comment has been minimized.

Show comment
Hide comment
@andrewdavidwong

andrewdavidwong Feb 3, 2016

Member

Oops, looks like you and I were working on this at the same time, @bnvk. I hope you don't mind. I adjusted the font size, padding, and colors of code appearance overall.

Member

andrewdavidwong commented Feb 3, 2016

Oops, looks like you and I were working on this at the same time, @bnvk. I hope you don't mind. I adjusted the font size, padding, and colors of code appearance overall.

@andrewdavidwong

This comment has been minimized.

Show comment
Hide comment
@andrewdavidwong

andrewdavidwong Feb 3, 2016

Member

Do you think it's ok? We can revert my commit and use yours instead, if you want.

Member

andrewdavidwong commented Feb 3, 2016

Do you think it's ok? We can revert my commit and use yours instead, if you want.

@bnvk

This comment has been minimized.

Show comment
Hide comment
@bnvk

bnvk Feb 3, 2016

@axon-qubes ah, damn it, wasted time! I don't know. Joanna and others had asked explicitly for a dark background, but meh, whatever. This is closer to what Github does, except it looks a little off (to my eye) as the font-size, but that can be adjusted later!

bnvk commented Feb 3, 2016

@axon-qubes ah, damn it, wasted time! I don't know. Joanna and others had asked explicitly for a dark background, but meh, whatever. This is closer to what Github does, except it looks a little off (to my eye) as the font-size, but that can be adjusted later!

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Feb 3, 2016

Member

FWIW I like the current colors, previous version white-on-almost-black was too much contrast, especially in inline text.

Member

marmarek commented Feb 3, 2016

FWIW I like the current colors, previous version white-on-almost-black was too much contrast, especially in inline text.

@andrewdavidwong

This comment has been minimized.

Show comment
Hide comment
@andrewdavidwong

andrewdavidwong Feb 5, 2016

Member

Ok, sounds like this issue is resolved for now. Feel free to re-open if necessary.

Member

andrewdavidwong commented Feb 5, 2016

Ok, sounds like this issue is resolved for now. Feel free to re-open if necessary.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment