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

Contact Form | CSS, HTML

bem
luis Colina•270
@Silkiercomet
A solution to the Contact 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 applied new grid concepts to make the layout responsive. Instead of using grid areas like I normally do, I decided to use grid template columns and assign the amount of space each element should take.

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

It was a challenge to manage the layout state of the inputs and the error messages when an error occurred, I thought of using siblings selector but for certain cases it was cumbersome, so I just added a special class to every input and changed the style of both the input and the error message to appear in case of an error

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

I think I did a good enough job in the JS part of my project but I would like to hear if I could have done it any better

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Samuel Richmond•190
    @Samuel-501
    Posted 8 months ago

    I absolute love your application of css in this code it's really wonderful

  • Mohammed Aljabali•90
    @MoAjabali
    Posted 8 months ago

    I really like you website and the touch you put, However, I believe that it will be better if you tye email filed check if it was the input correct or not.

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