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

css: flexbox, @media

Dušan•210
@osmonoh
A solution to the Clipboard landing page challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Any constructive feedback appreciated

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Rafal•1,395
    @grizhlieCodes
    Posted over 4 years ago

    Hey Dusan,

    Great job on the project. I have 1 piece of piece of advice, something I picked up from the project I just finished. See if you like it, perhaps use it yourself in your next project?

    Feedback: Your code is clean and easy to read, that's all I could ask for. Everything just made sense when looking over your CSS.

    Advice:

    1. Try using SCSS in your next project. I won't go too heavy into it but you can do something cool in SCSS that I can't really stop doing now: You can nest a media query within an element selector.

    To explain what I mean I will simply use some of your code, the end-effect would be identical to what you wrote with 1 added benefit:

    .supercharge-articles-container {
      max-width: 100rem;
      display: flex;
      align-items: baseline;
      gap: 3rem;
    
     @media (max-width: 1000px) {
            flex-direction: column;
            align-items: center;
      }
    }
    

    I love this method. It allows me to see the element I am changing as it's just a few lines above.

    1. When coding bigger projects try coding mobile-first. It's weird getting used to but it's always better to start with simplicity and build complexity into the media queries. (easier to add than it is to take away). So I code for mobile-first and my media queries are for tablet -> desktop. I almost always use @media screen and (min-width: ....).

    As I said, great job on the code and thanks for making it easy on the eyes!

    R

  • ApplePieGiraffe•30,525
    @ApplePieGiraffe
    Posted over 4 years ago

    Hey, great job on this challenge, Dušan! 👋

    Your solution looks very good and responds nicely! 👏

    I only suggest identifying each <section> tag you use with a heading and adding a <title> tag to the inline SVGs on your page to clear up the errors on your solution report. 😉

    Keep coding (and happy coding, too)! 😁

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

Frontend Mentor for Teams

Frontend Mentor for Teams helps companies and schools onboard and train developers through project-based learning. Our industry-standard projects give developers hands-on experience tackling real coding problems, helping them master their craft.

If you work in a company or are a student in a coding school, feel free to share Frontend Mentor for Teams with your manager or instructor, as they may use it to help with your coding education.

Learn more

Oops! 😬

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

Log in with GitHub