Skip to content

Conversation

@heshanthenura
Copy link
Collaborator

This PR addresses issue #3 and implements the following changes:

  • Added a Navbar according to the Figma design provided.
  • Navbar is fully responsive across mobile and desktop screens.
  • Added placeholder links (currently not functional).
  • Minor layout and design adjustments are welcome for further refinement.

@SadeeshaPerera
Copy link
Member

@heshanthenura Please replace the logo with the SVG one since it fits better in all aspect ratios. Also, add some top margin to the navbar for better spacing. Other than that, everything looks great!

@heshanthenura
Copy link
Collaborator Author

@heshanthenura Please replace the logo with the SVG one since it fits better in all aspect ratios. Also, add some top margin to the navbar for better spacing. Other than that, everything looks great!

Sure ayya I’ll do

@heshanthenura
Copy link
Collaborator Author

  • Add SVG instead of PNG
  • Add top margin

Copy link
Collaborator

@Seniru Seniru left a comment

Choose a reason for hiding this comment

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

Because you requested a review- looks ok, maybe a little padding from either sides (left and right) if we are going exactly with the figma design

@heshanthenura heshanthenura requested a review from icy-r as a code owner October 22, 2025 19:21
@pawan-live
Copy link
Collaborator

Hi all, as a practice please attach screenshots of what you have developed in desktop & mobile views for faster reviews 🙌

Copy link
Collaborator

Choose a reason for hiding this comment

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

is it possible to move this to a folder inside assets?

ex:

  • assets
    • images
    • logos
      • logo-dark.svg
    • icons

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

yes ayya Ill do

Copy link
Collaborator

Choose a reason for hiding this comment

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

Is this component necessary in this PR?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

my bad. forgot to switch branch ill remove


return (
<div className="w-screen flex items-center justify-center md:mt-[25px]">
<nav className="md:rounded-[24px] bg-[linear-gradient(90deg,rgba(141,198,255,0.61)_0%,rgba(173,101,255,0.61)_100%)] p-[2px] w-screen md:w-[70%] md:flex md:items-center md:justify-center">
Copy link
Collaborator

Choose a reason for hiding this comment

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

is this the purple-blue gradient that we'll be using throughout the site? if so pls move the gradient style to the tailwind config and we can reuse it 😉

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

sure

open ? 'flex' : 'hidden md:flex'
}`}
>
<Link href={'#'}>Home</Link>
Copy link
Collaborator

Choose a reason for hiding this comment

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

These links and any texts in the navbar should be loaded from a separate file from within the codebase, for ease.
ex:
lib/data/navbar.ts and include the data in it as an object.

ex:
navbarData

  • logo
    • imageUrl
    • link
  • links (array)
    • text
    • linkUrl

something like this

@@ -0,0 +1,58 @@
'use client';
Copy link
Collaborator

Choose a reason for hiding this comment

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

Also using use client on the top of the component makes the whole component client-side, which misses the whole point of using SSR, so let's try to use use client in the smallest components possible .

Ex: if only a button needs to have local states, then use use client in the button component separately and use it here

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

sure

<Image
src="/assets/logo-dark.svg"
alt="Logo"
width={0}
Copy link
Collaborator

Choose a reason for hiding this comment

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

we'll have to use width & height rather than setting it to zero 😉
Please refer: https://nextjs.org/docs/app/api-reference/components/image#width-and-height

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

sure

/>

<div className="md:hidden">
<button onClick={() => setOpen(!open)}>
Copy link
Collaborator

Choose a reason for hiding this comment

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

can we have a reusable button component with some variants?

Copy link
Collaborator

Choose a reason for hiding this comment

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

I added a Button component in my own PR. Maybe we can all use that.

@heshanthenura
Copy link
Collaborator Author

  • Moved the logo to the public/assets/logo folder
  • Removed the irrelevant PR component
  • Made the gradient a global variable
  • Defined image size

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.

4 participants