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

Clipboard Landing Page using Flexbox

Nathasha•150
@NathashaR1997
A solution to the Clipboard landing page challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hey Everyone, I have completed the challenge using flexbox.

Check out my following article, where I have briefly explained the steps I have followed to complete this challenge.

https://uxplanet.org/challenge-004-clipboard-landing-page-7d7e088c5b33

Thank you for checking this out, and feel free to leave your feedback and thoughts!! Any feedback and tips are welcome.

Many Thanks! Nathasha 😊

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Vanza Setia•27,715
    @vanzasetia
    Posted almost 3 years ago

    Hello, Nathasha! 👋

    Congratulations on finishing this challenge! 🎉 Also, you have written a nice blog post on how you finished the challenge. Great job! 👍

    Some suggestions from me.

    • I would recommend using the img element for the logo SVG. It will clean up the HTML a lot and then the logo image is not going to have :hover effect (it is much easier to use inline SVG when the color of the image needs to be changed).
    • Also, the logo is an important image. It needs to be accessible by the screenreader users as well. So, I would recommend having an alternative text. Just tell the company name, alt="Clipboard". This way, the screenreader users and potentially the search engine bots will know that it is the site of the Clipboard company.
    • Not all images need an alternative text. So, I recommend leaving the alt="" empty for all the images that don't add meaningful information or just for decorations. For example, if the image-computer.png doesn't exist on the site then there would be no missing information. But, the images inside the advertising section are meaningful images. If those images don't exist on the site then there are some missing information.
      • Some resources to learn about the alternative text.
        • Avoid these common alt-text mistakes - The Big Hack
        • Axess Lab | Alt-texts: The Ultimate Guide
        • Images Concepts • WAI Web Accessibility Tutorials
    • I highly recommend writing the styling using the mobile-first approach. It often leads to shorter and better performance code. Also, mobile users won't be required to process all of the desktop styles.

    I hope this helps! Keep up the good work! 👍

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