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

Flexbox, inclues, thuthy, new fromData, if

FREDERICO GARCIAS ALVES•330
@FredericoGarciasAlves
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


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

I am proud to have gone through a process where I am already finding it easier to take on more difficult projects.

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

This code came entirely from my mind, which is why I had difficulties with typos. It's not something specific to this project; it can happen in others (though I hope it happens less or not at all). That was the challenge I faced in this project. In JavaScript, I had trouble with the if statements in the first function because I wanted to stop a function with return to execute the correct one, but if return is triggered, the function stops, and there’s more code below for responsiveness. I solved it by adding two conditions in the if for the invalid email message due to the lack of @.

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

I was thinking that these if statements could be done with a switch, but I considered the syntax, and it doesn’t work. So, I believe these if statements can’t be made more concise. As for the window.mediaMatch, I placed it inside the function, but I think keeping it separate might be a good idea!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Hicham Abderrahim•280
    @hichamweblog
    Posted 8 months ago

    Great job tackling this challenge! 🎉

    Here are some tips to improve it:

    • Test the webpage on various devices and screen sizes to ensure proper responsiveness.

    • Avoid using:

    body {
      height: 100vh;
    }
    

    Instead, use:

        body {
          min-height: 100vh;
        }
    
    • Try to minimize using fixed widths or heights to maintain flexibility.

    Keep up the great work!

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.

Oops! 😬

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

Log in with GitHub