Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted over 1 year ago

Responsive Clipboard Landing page using Flex

Raza Abbas•770
@RazaAbbas62
A solution to the Clipboard landing page challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Any feedback will be accepted

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Petrit Nuredini•2,860
    @petritnuredini
    Posted over 1 year ago

    Congratulations on completing your project! Here are a few recommendations to enhance your code:

    1. Semantic HTML Elements:

      • Utilize semantic HTML elements to improve accessibility and SEO. For instance, in the <header> section, consider using <nav> for navigation links and <section> tags for distinct sections of your content. This makes your HTML more readable and accessible. Learn more about semantic HTML here.
    2. CSS Class Naming Conventions:

      • The class names like hero__text-wrapper, btn__ios, and btn__mac suggest a BEM (Block Element Modifier) naming convention but are not consistently applied. Consistency in naming conventions makes your code easier to read and maintain. You can read more about BEM here.
    3. Responsive Design Practices:

      • While you've included media queries for responsiveness, consider using a mobile-first approach. This approach starts with styling for smaller screens and then adding queries for larger screens. It often leads to cleaner and more maintainable CSS. Here's a guide on mobile-first design: Mobile First CSS.

    Keep up the fantastic work! Remember, coding is a journey of continuous learning and improvement. Your dedication to this project is commendable. I can't wait to see what you'll build next! 👏💻🌟

    Marked as helpful
  • Theunis•210
    @theYuun
    Posted over 1 year ago

    Other than a few alignment issues with the reference image, the top image on the background stops short of the right edge of the page.

    Marked as helpful

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

Oops! 😬

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

Log in with GitHub