-
Notifications
You must be signed in to change notification settings - Fork 545
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
The layout of https://olm.operatorframework.io/docs/ is broken #1919
Comments
@camilamacedo86 can you provide the OS/browser you are seeing this in? |
@matthewcarleton I'm seeing this on fedora 33/chrome I've heard similar feedback from users on mac os/chrome too. |
It can also be reproduced by zooming in on the page. |
Hi folks, I use chrome in a mac. WDYT about we push the layout config from https://github.com/operator-framework/operator-sdk/tree/master/website to the olm-docs? I think it would solve this problem and others as ensure that all have the same appearance. |
I'm all for both the sites looking the same. We might wanna be a little careful in adding whatever's there in https://github.com/operator-framework/operator-sdk/tree/master/website though since some of the decisions made for the sdk doc site were different than the olm site. The one to concern ourselves with here is that sdk decided not to expand the menu on the left nav panel, whereas olm decided to expand it, which is why we see the scroll bar. And it's the scroll bar that's causing the problem here as far as I can tell. |
/close |
@anik120: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Bug Report
What did you do?
Check https://olm.operatorframework.io/docs/
What did you expect to see?
The lateral menu
What did you see instead? Under which circumstances?
Environment
Possible Solution
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: