You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
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: