-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Navbar : Scroll To Reveal Navbar #4341
Comments
Hey @kunalcoder45 , i can work on this , kindly assign it me..... |
Okay @Thanush19 |
i can work on this please assign this to me @kunalcoder45 |
@thecrusader25225 Ok I can assign . .but what are your ideas about it . . |
`Dynamically featch year for copyright section. In React - const currentYear = new Date().getFullYear(); const year = () => { {currentYear} ) } export default year In Java Script - const currentYear = new Date().getFullYear(); |
hi @kunalcoder45, i'm not able to find source code for this page (https://nightwatchjs.org/blog/ ) in this repository. can you tell me in which directory source code available. |
Description
First Feature: On your blog website (https://nightwatchjs.org/blog/), the navbar becomes visible only when scrolling upward, which is not ideal for user experience. On your main website, the navbar is sticky, and it would be better if it remains sticky here as well. However, if you wish to keep it this way, consider adding a "Scroll to Top" button to make accessing the navbar easier.
Second Feature: In your footer section, why have you used images instead of icons for social links? Using icons would look better and more consistent. This is optional, but it could enhance the design.
Third Feature: In the copyright section, why are you writing the year manually? This will require updating it every year. Instead, you can fetch the year dynamically using JavaScript to ensure it updates automatically every year.
Suggested solution
No response
Alternatives / Workarounds
No response
Additional Information
No response
The text was updated successfully, but these errors were encountered: