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

Intro Page with Sign-Up Form, Created with Vanilla HTMl, CSS, and JS!

Corbinhol•180
@Corbinhol
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’m really happy with how I managed to turn the given design into a working, responsive page with basic form validation. Especially since mobile-first development still feels difficult. Next time, I might plan out my CSS structure a bit more before diving in, and possibly try out a CSS preprocessor to keep things cleaner and more manageable.

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

The hardest part was definitely dealing with the giant background image that messed up my layout. After some trial and error, I wrapped it in a container div and tweaked its positioning until it fit nicely without causing weird overflow issues. Just experimenting and checking online tips helped me figure it out. Most of the project seemed surprisingly simple.

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

I’d love some pointers on making the page even more accessible, especially getting the color contrast right. Also, any advice on making my JavaScript validation more streamlined and flexible would be super helpful for taking this to the next level. I also would appreciate any tips to help make responsive layouts more approachable!

As always, if anyone has any questions, I include much more comprehensive information about the project on my GitHub repo!

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on Corbinhol's solution.

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.