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

Responsive Sign Up Form With Validiation Using Js CSS

Ahmed Ali•680
@qayoommunawar
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


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

I am proud of using fluid grid layout, i know it is not that much ideal for this situation for this design, but i enjoyed doing it.

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

Using js for the very first time, so not a good experience. But I did it somehow. I will be looking forward to any suggestion particularly css, because i love it and it also is hard for me, the responsive part is more of a headache for me. looking forward to your suggestion and comments on form's design as it is just seem tricky to me like making it more of responsive.

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

Mention in above section.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Marzia Jalili•9,430
    @MarziaJalili
    Posted 2 months ago

    Running like clockwork! 🎉

    🌟 Some tiny little tweaks?

    ✅ A pro tip for centering the form:

    display: grid;
    place-items: center;
    

    ✅ You could consider using the clamp() function for responsive font sizes, margins and paddings instead of setting different sizes in media queries.

    • Here's an example of how it works:
    /* Syntax of clamp() */
    clamp(minimum, preferred, maximum)
    
    /* Example...*/
    h1 {
      font-size: clamp(1.5rem, 5vw, 3rem);
    }
    

    🌟 Overall, the web is lit, man!

    😎😎😎

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