-
Notifications
You must be signed in to change notification settings - Fork 44
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
hero and navbar improvements #129
base: main
Are you sure you want to change the base?
Conversation
you need to squash these 2 commits into one since the whitespace and DCO checking happens on each commit in the pull request. Let me know if you need help, but that should get you a clean CI run so we can review. |
I squashed the commits but the previous failed commit is still showing. |
ok, i reset the branch, did a new commit . but after that it's telling me to pull and when i pull, it is merging branches and in that merge that previous failed check commits are present. So it's quite a situation here. |
Signed-off-by: Priyanshu Singh <[email protected]>
Looks like a nice refresh to some of the UI elements on the main page; anyone else @containerd/committers have an opinion? |
I agree it is a nice refresh, a few questions/comments
|
|
Signed-off-by: Priyanshu Singh <[email protected]>
I have made the changes I mentioned above. |
Signed-off-by: Priyanshu Singh <[email protected]>
Any suggestion or changes ? |
Need rebase to remove merge commit. Also either remove the npm packages lock or if necessary move under the node.js comment |
Signed-off-by: Priyanshu Singh <[email protected]>
removed the package-lock file. Also can you do the rebase while merging the PR. Trying to do that locally can become quite messy. |
Signed-off-by: Priyanshu Singh <[email protected]>
Signed-off-by: Priyanshu Singh <[email protected]>
Signed-off-by: Priyanshu Singh <[email protected]>
Signed-off-by: Priyanshu Singh <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Interesting redesign, but it breaks for narrow views and the contrast for the docs pages isn't right. I'll submit screenshots shortly.
A few questions:
- In terms of branding, is this change in line with any branding color scheme?
- Has this redesign been requested and/or approved, if necessary, by the governing committee?
IMHO, this PR changes too many things at the same time. I'd suggest breaking it down into smaller changes submitted through separate PRs.
Here are a few screenshots illustrating design issues that appear for narrow views:
/cc @nate-double-u |
/cc @thisisobate for insight into design issues |
Hii chalin, i was waiting for the final confirmation for the design and had made changes initially for the laptop size only, that's why the site has some issues at smaller screen size. |
I completely agree with everything you said @chalin I suggest we revert the logo to be horizontally positioned. I kinda like the new background image; makes it look fresh. My only concern is that it replaces the brand color. Btw, great work @reveurguy; you got this! |
Signed-off-by: Priyanshu Singh <[email protected]>
Signed-off-by: Priyanshu Singh <[email protected]>
I have made the changes @chalin mentioned for small screen devices. |
Thanks @reveurguy, I'll let @thisisobate have a look at the updates when he has the time. |
@amye and/or @caniszczyk: any comments about the change in colors proposed by this PR, and whether that's an issue in terms of containerd branding, given the current color palette of containerd logos. /cc @nate-double-u |
Signed-off-by: Priyanshu Singh <[email protected]>
Any update on this? @chalin |
Hii, any update on this PR? Do let me know if any changes are required. |
Thanks for your patience. Again, I'll let @thisisobate follow up on this (he's currently out -- or soon will be -- for the holidays if I'm not mistaken). |
@chalin LGTM! Thanks for your patience! @reveurguy |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the updates @reveurguy, and the review @thisisobate.
Good progress
Generally, I like the updates @reveurguy, but making a UI skin change can be challenging to get right. I very much appreciate your efforts, but there is more work to be done. Hopefully you're still up to the challenge!
See below for two other UI issues I've identified. More importantly though, there are two major design problems, as I describe next.
Two major design problems
- This website was built using bulma. In this PR you've added the import of Bootstrap and it's Popper helper (see inline comment in
navbar.html
). We don't want that. CSS frameworks are resource heavy, and add a significant overhead for maintainers (even if you're only importing the JS resources). Use only either bulma or Bootstrap, not both. I'd love to see this project upgraded to use Bootstrap, but that should be done (if at all) after these UI skin changes land. - You've hardcoded styles through use of the
style
attribute. Styles should be added via classes defined by the CSS framework, or custom classes defined in the SASS style file.
Also see inline comments for other issues.
Remaining UI issues under mobile
Under mobile, the hamburger's color contrast isn't enough as you can see here (in the red circle), and in the next image:
The contrast between the logo (in gray) and the top-nav background (in dark gray), could be improved too.
Also, the drop-down menu from the hamburger needs font color fixes too:
Thanks!
check-links: clean production-build install-link-checker run-link-checker | ||
check-links: clean production-build install-link-checker run-link-checker |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think that nothing was changed here other than whitespace. Please undo the whitespace change.
Docs | ||
</span> | ||
|
||
<hr class="hr has-background-grey"> | ||
<hr class="hr "> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nit: remove unnecessary space in class string, here and the other instances below.
<script src="https://code.jquery.com/jquery-3.5.1.slim.min.js" integrity="sha384-DfXdz2htPH0lsSSs5nCTpuj/zy4C+OGpamoFVy38MVBnE+IbbVYUew+OrCXaRkfj" crossorigin="anonymous"></script> | ||
<script src="https://cdn.jsdelivr.net/npm/[email protected]/dist/umd/popper.min.js" integrity="sha384-Q6E9RHvbIyZFJoft+2mJbHaEWldlvI9IOYy5n3zV9zzTtmI3UksdQRVvoxMfooAo" crossorigin="anonymous"></script> | ||
<script src="https://stackpath.bootstrapcdn.com/bootstrap/4.5.0/js/bootstrap.min.js" integrity="sha384-OgVRvuATP1z7JjHLkuOU7Xw704+h835Lr+6QL9UvYjZE3Ipu6Tp75j7Bh/kR0JKI" crossorigin="anonymous"></script> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
CSS frameworks are resource heavy, and add a non-trivial overhead for maintainers. This website was built using bulma. Here you're adding full support for Bootstrap. We don't want that. Use either bulma or Bootstrap, not both.
@@ -96,3 +96,16 @@ | |||
</div> <!-- .navbar-menu --> | |||
</div> <!-- .container --> | |||
</div> <!-- .navbar --> | |||
|
|||
<script src="https://code.jquery.com/jquery-3.5.1.slim.min.js" integrity="sha384-DfXdz2htPH0lsSSs5nCTpuj/zy4C+OGpamoFVy38MVBnE+IbbVYUew+OrCXaRkfj" crossorigin="anonymous"></script> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This project already includes jQuery 3.6 (see under the themes folder).
<script> | ||
$(function () { | ||
$(document).scroll(function () { | ||
var $nav = $("#mainnav"); | ||
$nav.toggleClass("scrolled", $(this).scrollTop() > $nav.height()); | ||
}); | ||
}); | ||
</script> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
navbar.html
shouldn't contain embedded script
elements. Instead add the code in a manner consistent with this project (see the javascript.html
partial).
<div class="column" style="display: flex;justify-content: center;align-items: center;"> | ||
<img style=" transform:scale(1.2);" src="{{ $logo }}" class="is-footer-logo" alt="containerd footer logo"> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Don't hardcode style
attributes.
Btw, when working on the burger contrast issue, consider increasing the height of |
Signed-off-by: Priyanshu Singh [email protected]
made changes to hero section and navbar, as part of initial changes. Improved their look. Please provide your feedback or any changes.