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

Clipboard Landing Page - HTML/CSS - Flexbox/Grid

Josh Prentice•235
@jfprentice
A solution to the Clipboard landing page challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Work is definitely slowing my progress with these challenges..

I'm not sure why, but the image-computer.png isn't showing up off the left of the page like it did in the 1440p view in chrome dev tools.

I'm not sure I did the footer correctly - I used space-around but I think there is too much space between the logo and the links. I think I had the most trouble with the footer. I originally used the supplied social media icons in my anchor tags but couldn't figure out how to get the color to change on click - I tried using icon:active{ color: } and icon:active{fill: } - I ended up just going to fontawesome and using their icons instead.

I also see that I have an html issue because <section class="companies"> doesn't have a heading. How would I go about creating a heading for that section, but only for a screen reader? - I added an h2 with an sr-only class with visibilty:hidden, hopefully that fixes it.

Any feedback or tips would be greatly appreciated!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Emmilie Estabillo•5,600
    @emestabillo
    Posted almost 5 years ago

    Hey Josh, it's me. Once again 😄 Congrats on your first landing page! Awesome to see your progress. Here are a few notes:

    • there's a horizontal scroll from small to medium widths due to the margins on .main-images. I would probably play with the widths of the images per breakpoint. Or it might be helpful to look into responsive images to control the stretch and sizing.

    • For the footer: I agree working the svg icons can be tricky, I had a similar question in my last project. What I've gathered is that if I was placing them inside an img tag, as you've done prior to FA, the only thing that worked for me was using filter. Another option would be embedding the svgs inline and changing the fill attribute in CSS.

    For the spacing, you can wrap the logo and link-container into one div and adjust the spacing between them as you wish, separate from the icons. If you don't want to touch html, you can add margin-left: auto to the icons to push them to the right of the page. You would also be adjusting the space between the logo and links.

    • Lastly, I saw a few repeating snippets that can be cleaned up. In the footer for example, display: flex and align-items: center were written for both mobile and desktop. Same with the color for footer-link - it appears 3x on the stylesheet starting with the a tag. Nothing major, I know, but if this was a big site, it would all add up. Best to keep it DRY :-)

    Hope this all helps! See you on your next one lol

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.

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