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

Responsive coming soon page using Semantic HTML, SCSS, and JS

accessibility, bem, sass/scss
Venus•1,790
@VenusY
A solution to the Base Apparel coming soon page challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


First time using media queries in JavaScript! I used them to change the border-width on the desktop version when the user enters an invalid email. Is there a way to do this with pure CSS?

If there are any issues with the functionality or appearance of the website, please let me know!

Also, any feedback regarding how to check the validity of the email through JS more elegantly would be appreciated.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • szam•800
    @k-stopczynska
    Posted almost 3 years ago

    Hi!

    For email validation- just use regex. Your solution unfortunately got me submit successfully the email: %^%&^*@gmail.com and kstop@$%^&%$&$.com. As you know they are not correct email adresses. As for the media-queries in JS- when you really need to- use them. But mostly styling should be done in css. You could use JS to add a class for certain elements and just style this class. I used to do the same thing:)

    Congratulations on finishing the challenge! You really did well on matching the design:) Keep on coding!

    Marked as helpful
  • szam•800
    @k-stopczynska
    Posted almost 3 years ago

    Hi!

    Well, there is at least one reason I would think of: regex doesn't check if there is such a domain or if this email is actually yours (so security reasons, probably some tokens would be in play for this). Usually in regex you also don't check for addresses with IP in it.

    But for email validation like this newsletter- I would say it's enough for filtering if email is valid. For logging purposes- definitely not but I never dived into it that much at this point of my learning.

    Hope this helps:)

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