Skip to content
  • Unlock Pro
  • Log in with GitHub
Profile
OverviewSolutions
2
Comments
3

Shahar Levy

@monodonBrandKfar Yona, Israel85 points

A designer, front-end programmer, and a branding consultant, I help businesses look the way they want to be positioned within their industry.

Latest solutions

  • Mobile first, flex-box, react


    Shahar Levy•85
    Submitted over 5 years ago

    1 comment
  • All vanilla, css grid and flexbox


    Shahar Levy•85
    Submitted over 5 years ago

    0 comments

Latest comments

  • Harshit Kumar•105
    @HARSHITKU
    Submitted over 5 years ago

    Responsive using custom CSS Single price grid component

    1
    Shahar Levy•85
    @monodonBrand
    Posted over 5 years ago

    Hello Harshit,

    1. Design: the best way to get the design perfect for these challenges is to use a browser extension like pixelperfect that let you see all the small differences between the mockup and your code. But just from looking at it quickly, you have different spacings and sizes for the headers, the lower right block background color is not accurate, the text on the button is not accurate, the price is bigger then the mockup and the per month should not be aligned to the bottom. There are more inconsistencies but they can all be solved with pixelperfect extension. It's very very hard and takes much longer to get all these things right just by eye training so I really recommend you use it in your next challenges.

    2. Responsiveness: Your design does not brake in small sizes but not going mobile first made you keep the desktop layout for much too long.You should move to a single column design at about 600px width and adapt spacings around the component so you have more room for text and button. Right now at 650 about 50% of your width is the background and things get squished and long. I suggest building the mobile design first then adapting it as screen size grows. Usually you can adapt spacing and margins and font sizes an only after at about 750 and bigger (sometimes even only at 1000+ width) move to multi column layout.

    3. Functionality: I'd add a hover style to anything a user can interacts with, so in thins case the button.

  • Vanesa Perea•50
    @MinervaLong
    Submitted over 5 years ago

    Single price grid component

    1
    Shahar Levy•85
    @monodonBrand
    Posted over 5 years ago

    Hey, try not defining grid rows explicitly in this case. use inner padding for the blocks instead to set the right height. Also when you name classes, either use some kind of BEMish syntax or component oriented naming, I would avoid names like t1Div1 because they are first, chining you to a specific structure and second, hard for someone form outside to understand. Also for a project at this scope, I'd avoid utility classes they add code and can be redundant if you are not using them in the end.

  • Elena Stagg•220
    @elenastagg
    Submitted over 5 years ago

    Single Price Grid Component using Sass & Grid

    3
    Shahar Levy•85
    @monodonBrand
    Posted over 5 years ago

    Hey. My only suggestions for you for this task is to use pixelperfect extension for your browser so you can really be accurate in sizes and spacing.

    I would not use utility classes in a project of this scope, they add duplication if you are already using variables.

    And finally use some kind of a reset.css file to change browser default styles (such as list styles), and that will add clarity to your code.

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

Beta Member

This badge is a shoutout to the early members of our community. They've been around since the early days, putting up with (and reporting!) bugs and adjusting to big UX overhauls!

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