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

Responsive layout using Flex with JS form validation

sass/scss
IOβ€’720
@i000o
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 of persevering with this one. The layout was hard. The JavaScript didn't take me very long πŸ‘πŸ». I think this was a Grid layout that I didn't spot, so I used Flex. I did okay with it but it just took me so long and became miserable at some point. Media queries particularly slowed me down... I still don't understand background-image well. I'm happy to submit this one, and I hope to better my instincts when it comes to anticipating how layouts will behave when designing responsively so I can choose the best avenue for my workflow because this was not fun πŸ˜‚

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

The main challenge was with the layout. I hadn't used the art direction technique in a long time for the image, so I had to refresh my knowledge on that which was good. I used display: contents; for the first time which allowed me to work through some of the nuisances of the responsiveness of this design. I'm happy with the JavaScript I wrote, it's becoming clearer to me.

What specific areas of your project would you like help with?
  1. I'd love feedback on how best to use background-image for this design.
  2. I'm also not sure why on desktop, the content doesn't fill the viewport height, even though I programmed it to.
  3. When you trigger the error state, the top and bottom lines of the input field don't blend well with the arrow submit button, how might a pro refine this? I don't think it looks good this way.
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 IO'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

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.