Skip to content
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

Open
wants to merge 13 commits into
base: main
Choose a base branch
from
Open

Conversation

reveurguy
Copy link

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.

@estesp
Copy link
Member

estesp commented Jun 27, 2022

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.

@reveurguy
Copy link
Author

I squashed the commits but the previous failed commit is still showing.

@reveurguy
Copy link
Author

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]>
@estesp
Copy link
Member

estesp commented Jun 27, 2022

Looks like a nice refresh to some of the UI elements on the main page; anyone else @containerd/committers have an opinion?

@dmcgowan
Copy link
Member

I agree it is a nice refresh, a few questions/comments

  1. Where does the background blue come from, is it used somewhere else for consistency?
  2. The "Getting Started" button could have more contrast with the background so it pops out a little more
  3. "containerd Branding" or "containerd branding", we always keep references to the project as lower case, even in titles.

@reveurguy
Copy link
Author

I agree it is a nice refresh, a few questions/comments

  1. Where does the background blue come from, is it used somewhere else for consistency?
  2. The "Getting Started" button could have more contrast with the background so it pops out a little more
  3. "containerd Branding" or "containerd branding", we always keep references to the project as lower case, even in titles.
  1. I have used the background just for header and hero currently, I will apply the background to the footer and features section as well, that would give a nice scroll effect on the section and would be consistent as well. I used blue just to give a dark background with light text on it like the current one where a blackish shade is present. If it doesn't look great, I can try some other dark shades or try to do a vice-versa, a lighter background with dark text.
  2. Ok I will change that to some light color so that it stands out and is clearly visible as well.
  3. I'll change that to lower case.

@reveurguy
Copy link
Author

I have made the changes I mentioned above.

Signed-off-by: Priyanshu Singh <[email protected]>
@reveurguy
Copy link
Author

Any suggestion or changes ?

@dmcgowan
Copy link
Member

Need rebase to remove merge commit. Also either remove the npm packages lock or if necessary move under the node.js comment

@reveurguy
Copy link
Author

removed the package-lock file. Also can you do the rebase while merging the PR. Trying to do that locally can become quite messy.

Copy link

@chalin chalin left a 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.

package-lock.json Outdated Show resolved Hide resolved
@chalin
Copy link

chalin commented Jul 21, 2022

Here are a few screenshots illustrating design issues that appear for narrow views:

  1. Top-nav containerd logo is clipped:
    top-nav logo clipped

  2. IMHO, the top-nav logo is too big (the previous size seemed better).

  3. IMHO, the CTA buttons are too big (see the screen shot above).

  4. The vertical logo doesn't work for narrow displays:

image
  1. The social media buttons in the footer are too big (the previous size was ok). They used to fit nicely together in the default view, but they don't anymore
image
  1. The top-nav color needs to be adjusted for doc pages:
image

/cc @nate-double-u

@chalin
Copy link

chalin commented Jul 21, 2022

/cc @thisisobate for insight into design issues

@reveurguy
Copy link
Author

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.

@thisisobate
Copy link

I completely agree with everything you said @chalin
Also, the flipped logo doesn't sit well with the overall design.

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!

@reveurguy
Copy link
Author

I have made the changes @chalin mentioned for small screen devices.

@chalin
Copy link

chalin commented Jul 22, 2022

Thanks @reveurguy, I'll let @thisisobate have a look at the updates when he has the time.

@chalin
Copy link

chalin commented Jul 22, 2022

@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]>
@reveurguy
Copy link
Author

reveurguy commented Aug 1, 2022

Any update on this? @chalin

@reveurguy
Copy link
Author

Hii, any update on this PR? Do let me know if any changes are required.

@chalin
Copy link

chalin commented Dec 16, 2022

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).

@thisisobate
Copy link

@chalin LGTM! Thanks for your patience! @reveurguy

Copy link

@chalin chalin left a 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:

image
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:

image

Thanks!

check-links: clean production-build install-link-checker run-link-checker
check-links: clean production-build install-link-checker run-link-checker
Copy link

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 ">
Copy link

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.

Comment on lines +100 to +102
<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>
Copy link

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>
Copy link

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).

Comment on lines +104 to +111
<script>
$(function () {
$(document).scroll(function () {
var $nav = $("#mainnav");
$nav.toggleClass("scrolled", $(this).scrollTop() > $nav.height());
});
});
</script>
Copy link

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).

Comment on lines +13 to +14
<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">
Copy link

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.

@chalin
Copy link

chalin commented Feb 4, 2023

Btw, when working on the burger contrast issue, consider increasing the height of .navbar-burger span to 2px. That'll help make it more visible.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Needs Update
Development

Successfully merging this pull request may close these issues.

5 participants