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

Intro Component w/Signup - HTML, CSS, jQuery, JS, Google Fonts

P
Heather Smith•240
@sorengrey
A solution to the Intro component with sign-up form challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


I really enjoyed this one. I got to discover the differences between mix-blend-mode and background-blend-mode, and display: none and visibility: hidden. Both will surely help me in the future. I probably won't be applying gradients over my background images anymore to achieve the overlay look. And I'll probably use visibility: hidden for my error messages from now on to keep the layout in place and prevent elements from shifting.

This also felt like good jQuery practice. I wrote functions that check each input field to ensure nothing is left blank, and that a valid email address has been entered.

If you can think of any ways to improve my solution, I'd love to hear them. Thanks!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Ryan Calacsan•200
    @ryancalacsan
    Posted almost 4 years ago

    Good work on getting it super close to the design! Upon quick inspection I did notice a few things that may be worth looking into.

    -Your current email validation seems to work on leaving it blank but is not currently checking to be a valid email.

    -I would take a look into your error icon positioning. While they are in place for your desktop view, once you get to the mobile view they fly off to the right.

    -Lastly I would look into your media queries and or spacing when resizing your window. There is a point between the two where your text starts to get cut off.

    I am happy to go into more detailed solutions if you'd like but if you're anything like me, I learn/retain better when trying to work things out on my own first :)

    Overall, great job and happy coding!

    Marked as helpful
  • Anthony•355
    @ACdev27
    Posted almost 4 years ago

    I'm not sure if this was required by the challenge, but I thought from a user experience point of view it was good to have the form input error messages update on the blur event for each input, and recheck if input is valid. That way, if user fixes an error in one of the inputs, they would know that it was correct as soon as they leave the field.

    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 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