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

ping solution

GabFerreira•240
@Gab-Ferreira
A solution to the Ping single column coming soon page challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


@MohamedAridah @isprutfromua

I've done this challenge again and I think it's better now. In bonus I tried to change placeholder's color but I didn't succeed, don't know why.

If you have any advices please tell me :)

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Mo•840
    @MohamedAridah
    Posted about 3 years ago

    Hello, @Gab-Ferreira. You did a great job👏🎉. Now you can try to move forwards to another challenge. don't stop at this challenge. Every time you will try to make it better and free of mistakes, somehow you will find mistakes. So Go to the next challenge and never stops.

    However for this challenge you can do the following:

    • To change input placeholder styles you can use the following:

      • For more information's you can Read this W3 documnetation.
        #email-input::placeholder {
         color: var(--blue);
         font-size: 16px
        }
      
    • Extra styles for input to look close to the design

        #email-input {
          padding: 0 1.8rem; /* 3rem padding for the left was too much */
          border: solid var(--blue) 1px;
          font-size: 18px; /* previous font size was too small */
        }
      
    • For social media svg icons you can change it's color on hover by the following:

      • For more information's you can Read this article.
      .icon-box {
         border: 1px solid  var(--blue);
         transition: 200ms linear;  /* for soft transitions on hover */
      }
      
      .icon-box svg{
         fill:  var(--blue);
         max-width: 80%; /* To make icons smaller */
      }
      
      .icon-box:hover{
         background-color:  var(--blue);
      }
      
      .icon-box:hover svg{
         fill:  #FFF; 
      }
      
    • To fix the issues in the report above:

      • HTML Validations

        • remove action attribute from the form element.
        • add value to the name attribute for the input element. More information's Read this.
      • Accessibility

        • add aria-label to the attribution div like: <div class="attribution" aria-label="copyrights"></div
    • By the time your websites responsiveness will be better.

    I hope this was useful for you😍.

    Goodbye and have a nice day. Keep coding🚀

    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 1st-party linked stylesheets, and styles within <style> tags.

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.

Oops! 😬

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

Log in with GitHub