Skip to content
  • Unlock Pro
  • Log in with GitHub
Profile
OverviewSolutions
10
Comments
51

Laharl

@UrbanskiDevFrance1,000 points

A young full-stack freelancer who seeks to learn more while sharing his knowledge to assist other developers. My github link since I don't find a way to update it manually : https://github.com/Laharls

Latest solutions

  • Entertainment web app

    #next#react#tailwind-css

    Laharl•1,000
    Submitted almost 2 years ago

    0 comments
  • Responsive designo-multipage-website using NextJS & TailwindCSS

    #next#tailwind-css

    Laharl•1,000
    Submitted almost 2 years ago

    0 comments
  • Time Tracking Dashboard using HTML, CSS and vanilla Javascript


    Laharl•1,000
    Submitted almost 2 years ago

    0 comments
  • Single Price Grid Component


    Laharl•1,000
    Submitted almost 2 years ago

    0 comments
  • Newsletter sign-up


    Laharl•1,000
    Submitted almost 2 years ago

    0 comments
  • Order Summary Component


    Laharl•1,000
    Submitted almost 2 years ago

    0 comments
View more solutions

Latest comments

  • Jasmin Hidanovic•20
    @dexinho
    Submitted almost 2 years ago

    grid, flexbox, media

    1
    Laharl•1,000
    @UrbanskiDev
    Posted almost 2 years ago

    Hello Jasmin Hidanovic !

    Good job on completing this challenge. To answer your question, I feel you did great on the responsive, there's not many things to change, but I would adjust when the media query occur, because it happens way too soon (at 415px, which doesn't really make a good design for small device which has a width higher than 415px, but not much higher either)

    The most common breakpoints for media queries are :

    • 640px
    • 768px
    • 1024px
    • 1280px

    You can adapt them to the design you have to work on, but it should gives you a better idea at which width you should use a media query.

    Apart from that, it looks great, congrats again, hope it is useful and answer your question, happy coding !

    Marked as helpful
  • Emmanuel Luka•10
    @Emmyluks
    Submitted almost 2 years ago

    QR component

    #accessibility
    1
    Laharl•1,000
    @UrbanskiDev
    Posted almost 2 years ago

    Hello Emmanuel Luka !

    vw and vh correspond to the viewport width and the viewport height, which is based on the width and the height screen of a device. It is useful to size sections.

    Meanwhile, percentages is based on the relative size of the parent, and not the screen of the device used.

    I have found some links, which may help you to understand better the topic :

    • Stackoverflow difference between vh-vw and percentage
    • Blog unit explanation

    I hope it answer your question, keep learning and happy coding !

  • Uzair Bajwa•330
    @bajwacodes
    Submitted almost 2 years ago

    Order Summary Card made with HTML and CSS only

    1
    Laharl•1,000
    @UrbanskiDev
    Posted almost 2 years ago

    Hi Uzair Bajwa !

    To fix your issue with the centering, I did this on the body tag to center the card :

    display: flex;
    justify-content: center;
    align-items: center;
    flex-direction: column;
    height: 100vh;
    

    The centering wasn't doing anything because the body element wasn't taking all the height available.

    Don't forget to remove the padding you added, and it will work like a charm, hope it helps, keep learning and happy coding !

    Marked as helpful
  • Laurie Jefferson•160
    @lauriejefferson
    Submitted almost 2 years ago

    Intro Section with Dropdown Navigation Solution

    1
    Laharl•1,000
    @UrbanskiDev
    Posted almost 2 years ago

    Hello Laurie Jefferson !

    I feel there is something wrong with the dropdown on the desktop view, it works, but if you look closely, some elements get a little more space, and the page get bigger in height. I feel it would be better for the dropdown to not affect the height of the page. Also, when you click on one dropdown button, then the other, the first one clicked doesn't close off automatically. Also, I think you could add some kind of effect to make it visually appealing when you hover an element of the dropdown menu (for the desktop part)

    For the mobile part in general, I would add more spacing between element, it feel kinda cramped (not the menu), but otherwise, I think it looks cool. You may try to add a sort of transition to make the mobile menu look smoother. There is also a bug on the mobile menu, when you click to open the dropdown, then close the entire menu, the content of the dropdown is still visible ! (I think it is the same as the desktop version I mentionned earlier)

    Globally, you did a good job, keep learning and happy coding !

    Marked as helpful
  • jaedon farr•40
    @AltaOfficial
    Submitted almost 2 years ago

    Responsive newsletter signup using vanilla HTML, CSS, and JS

    1
    Laharl•1,000
    @UrbanskiDev
    Posted almost 2 years ago

    Hi Jaedon !

    Positioning and aligning is not really difficult, you can use flex and grid to do the job (which I saw you used in your code) which make it way easier to position or align element, maybe you need to go deeper on the subject

    For the transitions to the gradient, it is possible to achieve, but it's a bit tricky to achieve, I have found a codepen element which may help you to achieve the effect you wanted : Transition gradient

    For the javascript files,since it's a simple and small project, it does not really matter if they are in the same page, but for bigger project, it's better to sort the file by their functionalities, what they do.

    I hope it answer well your questions, keep learning and happy coding !

    Marked as helpful
  • Carolina Borba•510
    @anacarolinabmv
    Submitted almost 2 years ago

    Responsive newsletter signup form with vanilla JS

    1
    Laharl•1,000
    @UrbanskiDev
    Posted almost 2 years ago

    Hello anacarolinabmv !

    I don't know how you tackled this challenge, by starting to build the desktop version or the mobile version but I would recommend to always start with the mobile version, which makes it easier after to work for the tablet view & the desktop view.

    Also, if you test the responsive of the page, you will see it is not really responsive, the mobile size is working until your mobile screen is doing a width of 375px. (you can test it with your browser dev console)

    To make sure your design works well for larger devices, I recommend you to work with max-width, and medias query, here's a link about media queries : MDN media queries

    Otherwise, great job on the challenge, keep learning and happy coding !

    Marked as helpful
View more comments
Frontend Mentor logo

Stay up to datewith new challenges, featured solutions, selected articles, and our latest news

Frontend Mentor

  • Unlock Pro
  • Contact us
  • FAQs
  • Become a partner

Explore

  • Learning paths
  • Challenges
  • Solutions
  • Articles

Community

  • Discord
  • Guidelines

For companies

  • Hire developers
  • Train developers
© Frontend Mentor 2019 - 2025
  • Terms
  • Cookie Policy
  • Privacy Policy
  • License

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub