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

HTML and CSS flex box

Syed-Ansar•195
@Syed-Ansar
A solution to the Clipboard landing page challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


I was really had problem with the adjusting the width of the paragraph. But tried bit hard to fix it. Any kind of feedbacks will be appreciated.......

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Mojtaba Mosavi•3,760
    @MojtabaMosavi
    Posted about 4 years ago

    @Syed-Ansar you've done good job on this one, looks nice and responds well. There are a few sublte things that would make your solution look even better.

    1. Add a hover state to your button, links and social icons in the footer, it takes no to do it and makes you solution much more interactive.

    2. Your social icons need to be wrapped in a <a> tag sine they must be clickable.

    3. From around 800px to 1000px the buttons in the header are tied togather, looks a bit off, add margin to one of them throught modifier.

    4. On desktop view the image in computer section is not positioned as specified in the design, it looks ok but I suggest you play around with margin or relative positioning to get it in right place.

    5. In you markup you need to improve the way name things, for the most part you a good job but in some places you use names like class="1", I suggest you spend some time learning about BEM.

    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

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