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

Clipboard landing page challenge using flex and grid

Cyril•110
@cjeanneau
A solution to the Clipboard landing page challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hello, I started this challenge very well and was thinking that would be done quickly but as usual i made wrong choice and had to redo it. Then I faced few problem to layout everything. For the first time i use the mobile first design (not easy even if im sure it is the best way). Then I had problem with the layout of the first picture. Finally i manage to put everything in place. I will be very grateful for your feedback especially concerning my CSS code. Is is stodgy but i spent so much time to finish my challenge that i'm afraid to break everything by re-arranging it;-) Enjoy coding !

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Patrick•14,265
    @palgramming
    Posted about 4 years ago

    code start over, code star over, learn, start over learn.... That is the normal that is called progress. The more I try to rebuild things the more I learn and hope it works like that for you.

    Your results look very good the only thing you might want to try is to transition your footer elements to the desktop layout sooner once the view-port become wide enough to accept the elements in the row vs column layout

  • John Rey Faciolan•220
    @juani2
    Posted about 4 years ago

    Hello cjeanneau,

    Wow! almost pixel perfect! You might wanna try to adjust the sizing of your background at the header too to match the original design. In my case I used a contain background size and positioned the image on top. (see below snippet):

    body {
        background-image: url("/images/bg-header-mobile.png");
        background-repeat: no-repeat;
        background-position: top;
        background-size: contain;
    }
    

    I can relate to you, at first I thought this challenge will be easy but I was proven wrong when I observed some minor details that needs to be addressed like the changing font sizes, line-heights, letter-spacings, and margins at different view-ports. It took me 5 attempts before I was able to finish the challenge.

    About your css code, all I can recommend is to place comments on your code explaining what the block or line of code will do in your page.

    But overall, great work! It was near pixel perfect!

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

Oops! 😬

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

Log in with GitHub