Skip to content

Conversation

@hars-21
Copy link
Contributor

@hars-21 hars-21 commented Aug 19, 2025

I have fixed the spacing and alignment issue in the nav and the footer components.
fixes: #346

1. Improved spacing in nav:

previously - Image

after improvement -
image

2. Improved alignment in footer:

previously - Image

after improvement -
image

@hars-21 hars-21 requested a review from a team as a code owner August 19, 2025 12:06
@hars-21
Copy link
Contributor Author

hars-21 commented Aug 20, 2025

@sxd Sir, Please review the PR and let me know if any other changes are needed. Thanks!

@hars-21
Copy link
Contributor Author

hars-21 commented Aug 30, 2025

@sxd @jsilvela @gbartolini Sorry for tagging again but please can you review the PR and let me know if any changes are needed. It would be very helpful. Thanks!

@sxd
Copy link
Member

sxd commented Aug 30, 2025

@hars-21 you need to have some patience, I have PRs in my queue from may/June sadly we're not so many reviewing and we don't get so much help either, please, I ask you for some patience it's in my radar

@hars-21
Copy link
Contributor Author

hars-21 commented Aug 30, 2025

Okay sure sir, Sorry again for messaging

Copy link
Contributor

@jsilvela jsilvela left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hello:

  1. please sign your commit. Have a look at the failing DCO check, which includes instructions on fixing your commit
  2. I took your PR for a spin. The footer seems improved. The nav bar does not. See grab:
Screenshot 2025-09-01 at 10-03-52 CloudNativePG - PostgreSQL Operator for Kubernetes

@hars-21
Copy link
Contributor Author

hars-21 commented Sep 1, 2025

I have signed my commits and DCO check is now approved. Also, I have fixed navbar at my end.
Result:
image

Please let me know if the problem still persists. Thanks!

@hars-21 hars-21 requested a review from jsilvela September 1, 2025 17:54
Copy link
Contributor

@jsilvela jsilvela left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not fixed. Not at all.
The problem with the navbar persists.
Looking at the nav partial, I see the same change as you had made originally, i.e. using gap-10 instead of gap-14.
So, you changed nothing but merged from main and messed up your commit history.

@hars-21
Copy link
Contributor Author

hars-21 commented Sep 4, 2025

Sorry sir for creating mess and troubling you, now I have tried my best and fixed the issue.

I have fixed spacing in navbar and footer.
Signed the commit.
Also, cleaned my commit history.

Sir, please run the development server after pulling the changes so that the output.css file can be updated (through the tailwind build script).

Copy link
Contributor

@jsilvela jsilvela left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Are you testing your PR with different sizes of window?
Given the problem is the collision of the first item with the logo and the last item with the github icons, I don't understand your insistence on changing the inter-item gap.

Two different window sizes that produce collisions with your fix.

Screenshot 2025-09-04 at 17-29-04 CloudNativePG - PostgreSQL Operator for Kubernetes Screenshot 2025-09-04 at 17-27-54 CloudNativePG - PostgreSQL Operator for Kubernetes

@hars-21
Copy link
Contributor Author

hars-21 commented Sep 5, 2025

Sir can you please share your window sizes on which this problem is occurring.

I have tested on my changes on mainly these 2 sizes: 1024 * 1366 (ipad pro) and 1280 * 800 (macbook pro 13-inch) -> These are common sizes for ipads and 13 inch laptops.

Result:

image image

@jsilvela
Copy link
Contributor

jsilvela commented Sep 5, 2025

Resizing is a continuum. Drag your window around and see the bunching up.
If your CSS cannot survive that, then you don't have the fix you claim you have.

@hars-21
Copy link
Contributor Author

hars-21 commented Sep 5, 2025

Okay Sir, now I have fixed the issue.
I have changed hamburger menu from max size 768px to 1024px. Now in mobile and tablet view there will be hamburger menu.
After 1024px i.e, Laptop screens will have the expanded menu.
The reason: in tablet view the expanded menu could not be fitted, so it will be good if we provide hamburger menu.

image image

@hars-21 hars-21 requested a review from jsilvela September 5, 2025 11:37
@jsilvela
Copy link
Contributor

jsilvela commented Sep 5, 2025

I'm not convinced. Your fix is ballooning in complexity, and you're solving the collision by removing the navbar altogether.
I don't understand why the nav cannot be fixed surgically in one line.

@hars-21
Copy link
Contributor Author

hars-21 commented Sep 6, 2025

Sir this is the second approach in which I have added javascript to resize the github star button based on screen size. It was necessary as it could not be solved through simple CSS.
I have removed the hamburger menu from tablet and reduced the size of logo and github button.
please tell me if this would work.

@jsilvela
Copy link
Contributor

jsilvela commented Sep 8, 2025

My previous comment was that your approach was over-complex for fixing the collision.
And now you've added Javascript.
It should not surprise you that I don't think this is justified at all. As I mentioned previously, the collision could be fixed in a single line.
I don't approve, perhaps you can find someone else who will.

@hars-21
Copy link
Contributor Author

hars-21 commented Sep 8, 2025

Sorry sir for troubling you repeatedly. But now I have tried to reduce the complexity and also fixed the spacing.
I have also reduced my commits.
Please review and help me get this PR approved.
Thanks

@jsilvela
Copy link
Contributor

jsilvela commented Sep 8, 2025

Sorry sir for troubling you repeatedly.

And yet you ignore what I write.
I've indicated twice that a single-line fix should be possible. And I've already asked why you insist on trying to fix a collision with inter-item gap.
For my understanding, and with no code necessary, just use your own words: how would you fix the collision in only one line?

@hars-21
Copy link
Contributor Author

hars-21 commented Sep 8, 2025

For my understanding, and with no code necessary, just use your own words: how would you fix the collision in only one line?

We can apply gap to the main container which will introduce spacing between logo, links and github badge. Or provide padding or margin to left and right for removing the collision.

Are these approaches good or is there any other concept which I am unable to think of.

@jsilvela
Copy link
Contributor

jsilvela commented Sep 9, 2025

OK, then, margin or padding will avoid the collision. Why haven't you done this before?
Much simpler than tacking on Javascript or doing window-dependent resizing/gapping wouldn't you say?

And, I don't think it's very coherent to change the font size for the navbar progressively while the rest of the text on the page remains the same size.
I do agree with reducing the inter-item gap slightly. 14px was a bit much.
Keep it simple and short, and fix only the problems pointed out in the GH issue.

@hars-21
Copy link
Contributor Author

hars-21 commented Sep 10, 2025

OK, then, margin or padding will avoid the collision. Why haven't you done this before?
Much simpler than tacking on Javascript or doing window-dependent resizing/gapping wouldn't you say?

Okay, so the reason why I didn't apply margin or padding is while it solves the collision issue but it also creates other ui issues such as distorted logo, improper spacing and overflowing.

image image

As you can see there are many issues. So as a web developer I would suggest you can go with my latest commit which has only 5 lines of change in nav.html. Also, I have removed the javascript.

Or If you want only margin or padding spacing, I am ready to do that. Please let me know which one I should proceed with.

@jsilvela
Copy link
Contributor

while it solves the collision issue but it also creates other ui issues such as distorted logo, improper spacing and overflowing.

The padding does not introduce those issues. Those issues exist already in production.
Since the problems the Issue complained of were the footer spacing and the collision of the navbar, I think you should do the easiest fix. And as I mentioned, I think reducing the inter-item gap from 14 to, say, 10 px, is also relevant as part of this.

Other issues can be raised in new tickets, and fixed in other PRs.
Given the website is likely to go through some redesign soon, please keep the PR small and to-the-point.

@hars-21 hars-21 force-pushed the main branch 3 times, most recently from bc4c0ef to 17f010e Compare September 10, 2025 17:12
@hars-21
Copy link
Contributor Author

hars-21 commented Sep 10, 2025

Okay Sir thanks for the clarification, I have now reduced the gap and also added 4 px of padding to remove the collision.

Now I guess, this PR can be merged.
Also, I would love to contribute in website redesign. Please tell me whenever any help is needed.

jsilvela
jsilvela previously approved these changes Sep 10, 2025
@jsilvela
Copy link
Contributor

Thank you.
To be pushed to prod, this would need a maintainer anyway, and I'd like to have a second approval for merge, too.

Signed-off-by: Harshil <harshilgupta.2005@gmail.com>
Signed-off-by: Harshil <harshilgupta.2005@gmail.com>
@jsilvela jsilvela self-requested a review October 15, 2025 14:49
@sxd sxd merged commit 2a1b20c into cloudnative-pg:main Oct 15, 2025
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Fix Navbar Overlap on Medium-Sized Screens and Add Spacing to Footer on Mobile View

3 participants