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

Responsive design using patience, lots... of... patience... :)

Gareth•410
@Gareth-Moore
A solution to the Clipboard landing page challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


I'm getting better at sorting out the layout in a reasonable time frame. Let me know what you think of the code and any feedback is much appreciated my fellow front enders :)

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • Fluffy Kas•7,655
    @FluffyKas
    Posted almost 3 years ago

    Hey there,

    Your solution looks great! Pretty much pixel-perfect on all screen sizes 😊 There are only a few things you could double-check - mostly regarding the markup:

    1. I think using article elements isn't the best choice here. A simple div or section would do the job, there's no need to overthink it.

    2. Footer links are typically not wrapped in a nav. Using just a ul would be fine but all the list items inside should be links (so wrapped in a tags).

    3. Similar goes to the social media icons: you could wrap them in a tags and give them aria-labels (those would be useful for people who can't see the actual images).

    4. The company logos are missing alt texts. This section would also benefit from some visually hidden section title (look up an sr-only class, there are some good code snippets out there), so the user knows what's the purpose of the section before the company names are announced by the screen reader.

    5. Some github best practices: make sure you remove any commented out code that you no longer need (theres some in your footer section). Same goes for unnecessary/unused files. You could add the style guide and the design folder to the gitignore file so they don't get needlessly uploaded 😊 Your js file is also empty.

    It's also a good idea to write a nice README file, especially since Frontend Mentor provides such a good template for it. A good documentation is something that employers tend to like :)

    I hope you don't find my suggestions too nitpicky. It's always a good idea to pay attention to accessibility as well. Overall I think what you did looks great! 😊 Happy coding!

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 1st-party linked stylesheets, and styles within <style> tags.

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.

Oops! 😬

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

Log in with GitHub