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

Base Apparel Coming Soon page with Email Validation and CSS grid

bem
Tharun Raj•1,330
@Code-Beaker
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?

This is the third time I've completed a project with email validation. This one seemed easy when I looked at the preview images. But, it turned out to be a little confusing from the responsive side of the website.

Built with:

  • HTML
  • CSS
  • JS
  • Validator.js

It was easy to create the error states with messages and icons. I'm proud of not doing lots of googling and instead just going through an MDN article to get help with the order of the grid on mobile screens.

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

As I said, making this website responsive was a bit of a challenge mainly because the image used to break when I shrunk the browser window.

I also found it a little hard to create the form. Adjusting the padding and width of the form took a lot of time and work. The form icons also disappeared when I switched to a small screen. I had to re-write and add lots of code to fix it. I'm still not very confident if it looks good on smaller screens.

Thankfully, the Validator.js library took care of the email input.

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

I would like to get recommendations on how I can improve my code and also the responsiveness of the website. Let me know if it works correctly on your devices!

As always, any suggestions are welcome! 😇

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on Tharun Raj'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.