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

Responsive Clipboard Landing Page Using Grid Layout

Gabriel Ayuba•270
@Tzienom
A solution to the Clipboard landing page challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hey, folks. Completing the challenge was a fun one for me after I was away for months. I'm back now. So uh, the only questions I've got:

  1. How were the buttons in the original design given the box-shadow they had? It seemed a little different from the regular ones.

  2. Is it okay adding classes or IDs to HTML semantic elements?

I'd love to hear from anyone so I could add a little to my knowledge. Thanks.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • AFIQUE•115
    @AF1QUE
    Posted over 3 years ago

    Hey, you did a good job overall. If I had to point out what you need to improve on then I would be stating the following:

    • Pay close attention to the styles of the button from original design.

    • The desktop illustration in the second section is not stretched aligned to the left as we can see in the original design. I did use the following code for the illustration in order to take it out of the wrapper and aligned it to the very left of the section. To be specific, it was done using negative margin settings.

    margin-left: calc(-50vw + 45%);

    In order to see how I've done the mentioned tasks you can follow my design in the link below: https://fm-clipboard-landing-page-challenge-hub-afique.vercel.app/

    Now, answering your questions:

    1. It is absolutely fine to use any class or id in the semantic HTML elements.

    2. The way I've managed to create the buttons is by using the border effect, you can see my code below:

    .btn {
      display: inline-block;
      font-family: "Bai Jamjuree", sans-serif;
      font-size: 1.125rem;
      font-weight: 600;
      line-height: normal;
      letter-spacing: 0.025em;
      text-decoration: none;
      color: #fff;
      border-radius: 3.125rem;
      padding: 20px 40px 16px 40px;
      transition: all 0.5s ease;
    
      &--ios {
        background-color: $strongCyan;
        border-bottom: 4px solid darken($strongCyan, 10%);
        box-shadow: 0px 5px 10px 0px rgba(38, 186, 164, 0.3);
        -webkit-box-shadow: 0px 5px 10px 0px rgba(38, 186, 164, 0.3);
        -moz-box-shadow: 0px 5px 10px 0px rgba(38, 186, 164, 0.3);
    }
    

    I hope I was able to answer your questions.

    Best regards, Afique

    Marked as helpful
  • Gabriel Ayuba•270
    @Tzienom
    Posted about 3 years ago

    I've been away for a long time, but thanks. This was quite 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.

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