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

Ping Coming Soon Page using Sass & JS

Nafsuki•245
@Nafsuki
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


I coded desktop first, mobile responsive design using Sass and flexbox layout.

form validates the value and gives error if input value is empty, and if email address is not formatted correctly.

Any feedback & suggestion for improvement would be very much appreciated ☺️🙏!!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Steven Toben•750
    @steventoben
    Posted over 4 years ago

    This looks pretty great tbh. I only have a couple small critiques which is rare for me when reviewing other peoples' stylesheets. First off I want to say that I love your use of rem units throughout the project and actually using them properly. I also love the inter-activeness from all of the buttons, however I feel like the textbox doesn't reciprocate the same feeling. I know it's a small thing, but even changing the cursor from a pointer to a caret once it has focus, and maybe even throwing an effect on the placeholder text would make a big difference. Another tiny detail that's purely semantics is you shouldn't skip a header level in html. It should go from h1 -> h2, which again isn't really a big deal especially with the fantastic accessibility of the rest of your markup. Your SASS file is pretty big, for a small project like this it's not a huge deal but a few more small improvements you could make would be splitting your variables into a partial, it also seems like you used some styles enough(ex: flexbox) to warrant breaking them off into mixins, perhaps into into another partial with your media query mixins? Another thing is in your last media query I think you nested to deep. For example, your button and input share the same exact set of rules. And here's the last little nitpick: are you using a typographic scale? A lot of your font-sizes are quite weird and stray from a typical modular type scale and I'm curious how you came to those numbers. Also you also never include line-height or letter-spacing into any of your text. I honestly had to dig pretty hard to find anything wrong with this, overall it looks pretty amazing and no one would ever really notice such small details. Great work!!

  • Gerben Dol•3,115
    @GerbenDol
    Posted over 4 years ago

    Hey Nafsuki!

    Your solution looks great - really well done! 🤩

    One thing I'd consider paying attention to is the nesting of your SASS. Right now your style on, for example, your h1 only works as long as it is in the .container. Do you really need that depth in your selector or risk the style breaking as soon as it is used outside of the .container?

    In a small project like this obviously it's no problem at all, but keep this in mind on bigger projects! 😄

  • ApplePieGiraffe•30,525
    @ApplePieGiraffe
    Posted over 4 years ago

    Hello, Nafsuki! 👋

    Just wanted to say, nice to see you complete another challenge yet again! 😀 Good work on this one! 👍 Your solution looks great and I like the hover state you gave to the button! 😉

    Keep coding (and happy coding, too)! 😁

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

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