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

pettik--contact-form

pettik•600
@pettik
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'm most proud of the clean and responsive design of my HTML and CSS code, ensuring it works well across various devices and screen sizes. Next time, I would optimize the JavaScript further to improve efficiency and readability, and also consider implementing more comprehensive form validation to enhance user experience.

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

One of the challenges I encountered was integrating the provided error messages smoothly within the form validation logic. Ensuring that the predefined messages appeared at the right time and in the correct context required careful coordination between HTML, CSS, and JavaScript. I overcame this by setting up clear conditions in the JavaScript code and using CSS to control the visibility and styling of the messages. Another challenge was maintaining a consistent look across different browsers. To address this, I tested the form extensively in multiple browsers and made necessary adjustments to the CSS.

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

I would appreciate help with optimizing the JavaScript code, particularly in improving the efficiency of the form validation process. Specifically, I'm looking for feedback on how to handle multiple conditions and error messages in a more streamlined manner. Additionally, I'd like advice on making the CSS more modular and maintainable, particularly regarding the responsiveness of the design. Suggestions on how to better organize my CSS and possibly use a preprocessor like SASS would be very helpful.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on pettik'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
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 1st-party linked stylesheets, and styles within <style> tags.

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.