Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted about 2 months ago

Clipboard landing page - Using Responsive HTML , CSS, and a little JS

Nathan Ray•400
@NathanRayM
A solution to the Clipboard landing page challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


What are you most proud of, and what would you do differently next time?

I wanted to challenge myself and take on a little of a larger project like this landing page. I'm glad I did. I'm proud I was able to work through the quirks of building the page. I did also add a bit extra to the logo, the buttons, and the footer links 😁

Overall, this was really fun to build.

What challenges did you encounter, and how did you overcome them?

There were many challenges throughout the project. Getting close to the design without an actual figma file is a challenge within itself. I was able overcome the majority of challenges by referencing w3 schools, and the MDN.

What specific areas of your project would you like help with?

I'm looking to improve overall but for this would appreciate any feedback on the semantics, and how I can more efficiently write my code including the CSS.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Chamu•13,860
    @ChamuMutezva
    Posted about 2 months ago

    Well done with your project, here are a few items that you can have a look at:

    • the logo <img class="logo-img" id="logoFly" src="images/logo.svg" alt="" /> is an important element of the page and is usually a link for the homepage. That is the logo will have an anchor element as the parent.
    • alt values for images can be empty for decorative images (alt=" ") or in other cases should be a summary of the image. What is the message being potrayed by the image. Words like image, picture , logo etc should not be part of the alt value.
    • most recommendations these days favours to style mobile first rather than desktop. So your initials styles will be for small devices and then add media queries when appropriate using min-width instead of max-width.
    • the display for small devices looks good up until it hits 400px, from there the site breaks until it reaches about 760px. You will need another media query for this layout to look better on medium devices
    Marked as helpful
  • P
    Nick J•90
    @troy71
    Posted about 2 months ago

    I really like how you managed to get the logo to float into the page when loaded, and the wiggle on the buttons, just amazing.

    Well done, fantastic job!

    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
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.

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

Oops! 😬

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

Log in with GitHub