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

Intro component with sign up

Lucy.Sujeong•10
@chusu91
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


Hello! This is my first challenge for FrontEndMentor!

Can someone give me Feedback? lots of thanks in advance !

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Fluffy Kas•7,655
    @FluffyKas
    Posted over 3 years ago

    Hey Lucy,

    You already have some error messages defined in your HTML, why don't you use them? ^^ You could define an .active class for example, that would change their display to block instead of the default display: none. And then you can toggle this class with JS, if the input is empty/email isn't correct. You seem to be overthinking the logic a bit (which I totally understand, if you're new to JS, it can feel overwhelming). Check out this video, it may give you an idea what would be a good approach. There's also a solution for this exact challenge on the channel. I didn't want to link here that one though, as you may want to try to implement it yourself first, before checking a full solution.

    As for the error-icon, you could use a position: absolute on it, while giving the "form-input" div a position: relative. Position it where you want and then you can apply the same logic here as before: toggle its display with a class.

    I'd also note a few other things:

    1. The purple text above the form is probably not a button. It does look like a button, but honestly, that's just a questionable and misleading design choice, I reckon >.< You can just put that text in a simple div and keep the styles.

    2. You could swap your container div to a main. As a general rule, most of your main content should go inside this element, unless it's something more fitting for footer/header.

    3. For this challenge you can also remove the action attribute from the form, it won't be needed. ^^

    Overall, I think you did pretty good on your first try though! Good luck with the JS part, if you have any questions you can of course ask here or on Slack ^^

    Marked as helpful
  • Ganesh•280
    @Ganesh-Rathor
    Posted over 3 years ago

    @Lucky Hey, great work bro 99 level perfection

    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

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