Active navigation link highlighting not working on the website

[Krishna100604]

**This is how it is supposed to look

[Krishna100604]

@shivankacker please see this and let me know

[sharath-1517]

Is this issue open to be solved? I'd like to work on this issue. Thanks.

[Krishna100604]

hey @shivankacker could you please this issue?

[shivankacker]

@Krishna100604 This might not work with our current design. Maybe lets just add a small dot at the bottom of the link to indicate it is active?

[Krishna100604]

@Krishna100604 This might not work with our current design. Maybe lets just add a small dot at the bottom of the link to indicate it is active?

is this fine? @shivankacker

[shivankacker]

@Krishna100604 let's not change the color maybe? Keep it white, but fully opaque. And decrease the space between the dot and text a little?

[Krishna100604]

@Krishna100604 let's not change the color maybe? Keep it white, but fully opaque. And decrease the space between the dot and text a little?

• How about this ?

[Krishna100604]

** or This one ? @shivankacker

[shivankacker]

@Krishna100604 hi, the second one looks good to me

[Krishna100604]

@Krishna100604 hi, the second one looks good to me

so i will make a pull request then?

[shivankacker]

@Krishna100604 yes please go ahead

[michael-020]

@Krishna100604 @shivankacker hey, I have made the first thing asked in the issue, there are some adjustments to make in it, like you sort of get an underline and the color of the text changes when you hover on a nav item.
I would like to go forward and completely polish this issue, if it is needed. So please let me know.

[ARH-MNAJS]

@shivankacker I have reviewed all the comments in this issue and past PRs and now have a clear understanding of how to implement the intended design aesthetic for the navigation links. Could you kindly assign me this issue?

[shivankacker]

@ARH-MNAJS please make a PR and link to this issue

[ARH-MNAJS]

@shivankacker I have raised a PR #56 kindly review it and provide feedback if any

[ARH-MNAJS]

@shivankacker We can close this issue as we already have a ready to merge PR #56 for this issue