Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted over 4 years ago

Responsive Clipboard Landing Page

Anil•150
@willinglywill
A solution to the Clipboard landing page challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Amazing!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Raymart Pamplona•16,040
    @pikapikamart
    Posted over 4 years ago

    Hey, great job on this. The layout looks fine in desktop and in mobile it seems good as well, but there is this horizontal scroll which we want to avoid.

    Some suggestions would be:

    1. Making the font-text color more visible. Right now it is sort of gray-ish which is not really being contrasted well enough of the white background. Making it more darker will really help people to read it clearly.

    2. I think your breakpoint is too far, you set the desktop only for min-width: 1440px, this makes a bit lower of that, then they get the mobile version which is really too soon. You could either lower it down so that we will get desktop layout at those desktop points.

    3. Your footer logo gets overlapped by its sibling, it will be better if you removed the margin-left on the footer-navs selector to prevent that. To achieve that spaced out layout on the footer, you could just add both the footer-logo and footer-navs into one block, then make it flex. That way they will be side-by-side and more easy to handle. Also make the max-width of the footer-logo image itself a fixed and not 100%, since it is a flex-container, width of element varies according to space left.

    4. Also, those footer links should be wrapped inside a tags, links and social media links.

    5. Mobile layout needs to be refactored. Right now that is causing the horizontal scroll, looking at it, I think you forgot to declare some on it.

    6. Too many h1 elements, we want to avoid overusing h1 in a single page, you could just either use h2 on those. Making a habit of only using h1 per page will be really awesome.

    But still, good work on this one^

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

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