-
Notifications
You must be signed in to change notification settings - Fork 744
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
Certificate issues with bytedeco.org #1469
Comments
I think I was able to fix that. Can you check it now? |
HTTPS is looking spiffy, now it's just the little Fork me on GitHub image that's not loading for some reason. |
Looks good to me too. There's a "fork me" ribbon that's missing https://github.blog/2008-12-19-github-ribbons/ shows the new HTML for that. |
Done! |
Maybe put the ribbon on the right so it doesn't cover up "Bytedeco" in the top toolbar on small screens? |
It's better that it covers the news button?? |
For any narrow screen width you always cover Bytedeco on the left, but for many narrow screen widths you don't cover anything on the right due to the way the line wrapping works. (It's your site, you do as you please ;) |
I'd rather leave it like that just in case, this is just a small display issue. In any case, the whole thing is neglected and should be redesigned with Bootstrap and what not... |
It seems like Chrome is starting to force / default to https, which makes bytedeco.org look like this:
Looks like you're using github pages, maybe this can help: https://docs.github.com/en/pages/getting-started-with-github-pages/securing-your-github-pages-site-with-https ?
The text was updated successfully, but these errors were encountered: