Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted about 1 year ago

base-apparel-coming-soon-master

tucecifci•150
@tucecifci
A solution to the Base Apparel coming soon page 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 most proud of the seamless integration of form validation techniques into the Validation Form Project. Implementing robust validation logic using JavaScript allowed for real-time error detection and user feedback, enhancing the overall user experience. The visual feedback provided to users when entering incorrect or incomplete data was a significant achievement, as it greatly improves usability and helps guide users towards correct inputs. Additionally, ensuring accessibility principles were followed to make the form usable for all users was another aspect of the project that I take pride in.

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

Complex Validation Requirements: One challenge I encountered was implementing validation logic for complex input requirements, such as validating email addresses, phone numbers, or password strength. Each type of input had its own set of validation rules, which required careful consideration and implementation to ensure accuracy and effectiveness. Dynamic Form Updates: Another challenge was dynamically updating the form UI based on user input and validation results. Managing the DOM elements and displaying error messages in real-time while maintaining a clean and intuitive user interface posed a significant challenge, especially when dealing with complex form structures or multiple validation rules.

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

Enhancing Validation Logic: I would appreciate guidance on refining the validation logic for specific form fields, such as validating email addresses, phone numbers, or complex input patterns. Additionally, I'm interested in exploring more advanced validation techniques to improve the accuracy and efficiency of the validation process. Improving User Experience: I'm seeking assistance in enhancing the user experience of the form, including optimizing the layout and design to make it more intuitive and visually appealing. I'm also open to suggestions for incorporating interactive features or animations to engage users and improve usability.

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 tucecifci'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 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.