Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 29 days ago

My version of base apparel comming soon page challenge.

bem
Maynor López•230
@mlopezl
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’m proud to have completed this challenge. Even when I’m unsure how to do something, I always find a way. I know this is a small project, but it’s a step toward taking on bigger and tougher ones.

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

I’m still working on getting better at responsive design and JS interactions.

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

Responsive design and JavaScript. I’m open to any feedback that can help me improve my skills.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Harsh Kumar•3,850
    @thisisharsh7
    Posted 29 days ago

    Great job completing the challenge! Here’s feedback to enhance your project:

    HTML/CSS: The structure is clean, and the use of CSS custom properties for colors/gradients is excellent. However, the responsive design can be improved. The .hero__container width transitions (80% to 100%) feel abrupt; consider smoother scaling with max-width. The mobile layout works, but the .hero__main fixed width (300px) may cause overflow on smaller screens—use relative units like vw or minmax. The .hero__error positioning could be more robust using right: calc(100px + 10px) to align with the button.

    JavaScript: The email validation logic (inputEmail.value.includes('@' && '.')) is flawed due to incorrect operator precedence. Use inputEmail.value.includes('@') && inputEmail.value.includes('.') for proper validation. Consider adding a regex for more robust email checking (e.g., /^\S+@\S+\.\S+$/). Also, the button lacks a click event to handle form submission—add one to validate on submit.

    General: Test across more devices to ensure no overflow. Keep practicing responsive design and JS validation.

    Awesome work—focus on refining these areas for even stronger projects!

    Marked as helpful

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