Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted almost 2 years ago

Notification Page with NextJS

next, tailwind-css
Tyler Nichols•210
@FLuffy-teddy
A solution to the Notifications page challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


When working on a project and you don't have adesign file to work with just an image, what is the best way to match the design, especially with media queries? Just eyeball it?

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • solitary_coder•1,000
    @kabir-afk
    Posted almost 2 years ago

    Well the design images provided to us have a desktop resolution of 1440 x 900, height can vary in some designs but majority of the times it is somewhere around 800 and 900 . . . in order to match the design and generate a pixel perfect screenshot, you can check out this article here. It'll give you a step-by-step guide on how to achieve design accurate web page.

    But that's just the first part . . . in order to achieve pixel perfection , you'll need to get the dimensions of your components right as well. Mere eyeballing isn't gonna get you anywhere. You can check the dimensions in your design using photoshop and reassure those dimensions in your webpage either by inspecting the element or using extensions like Meausre It. Since we have to make our sites responsive , we obviously need to use relative units , and inspecting the element again and again only slows us down , so I prefer using the extension . This'll help you be more accurate . . . hope I was able to help , keep grinding!! 💪💪

Join our Discord community

Join thousands of Frontend Mentor community members taking the challenges, sharing resources, helping each other, and chatting about all things front-end!

Join our Discord
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

How does the accessibility report work?

When a solution is submitted, we use axe-core to run an automated audit of your code.

This picks out common accessibility issues like not using semantic HTML and not having proper heading hierarchies, among others.

This automated audit is fairly surface level, so we encourage to you review the project and code in more detail with accessibility best practices in mind.

How does the CSS report work?

When a solution is submitted, we use stylelint to run an automated check on the CSS code.

We've added some of our own linting rules based on recommended best practices. These rules are prefixed with frontend-mentor/ which you'll see at the top of each issue in the report.

The report will audit all CSS, SCSS and Less files in your repository.

How does the HTML validation report work?

When a solution is submitted, we use html-validate to run an automated check on the HTML code.

The report picks out common HTML issues such as not using headings within section elements and incorrect nesting of elements, among others.

Note that the report can pick up “invalid” attributes, which some frameworks automatically add to the HTML. These attributes are crucial for how the frameworks function, although they’re technically not valid HTML. As such, some projects can show up with many HTML validation errors, which are benign and are a necessary part of the framework.

How does the JavaScript validation report work?

When a solution is submitted, we use eslint to run an automated check on the JavaScript code.

The report picks out common JavaScript issues such as not using semicolons and using var instead of let or const, among others.

The report will audit all JS and JSX files in your repository. We currently do not support Typescript or other frontend frameworks.

Oops! 😬

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

Log in with GitHub