Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted over 3 years ago

base-apparel-coming-soon with flexbox

accessibility, foundation
MordenWebDev•500
@MordenWebDev
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


hi guys, I just completed this project. please provide any feedback.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Remus D. Buhaianu•3,125
    @remusbuhaianu
    Posted over 3 years ago

    Good job on completing the challenge, Morden!

    I know it's difficult in the beginning, but with each project, you'll become a better developer ;)

    I had a look at your live solution and I also looked through your Github code and I have a few suggestions / observations.

    Here they are, in no particular order:

    1. Your HTML and CSS code formatting is a bit hard to read through. You might want to go through it again and polish it a bit because not only it'll make it easier for you to code, but it'll also make it easier for other developers who want to read your project's code.

    2. There are a few issues with the alignment / spacing in your layout. Even without taking the original design into account, it looks a bit off. Part of being a good frontend developer is also developing an eye for detail and good UI.

    3. There's no reason to use the min-height property on the body element.

    4. You can reset the margin and padding properties for all the elements by using the * selector. So you can add margin: 0 and padding: 0 to the CSS declaration you already have for the * selector.

    5. There might be too many media queries there. I think your code can be simplified so you don't have to change these properties in so many media queries.

    All in all, you've done a good job on this challenge and as Aakash pointed out, you did well by adding the custom message for the input element. That kind of attention to detail is what makes you a better developer and improves the overall quality of your projects.

    Keep up the good work and looking forward to seeing more of your work here on Frontend Mentor! ;)

    Marked as helpful
  • Aakash Verma•9,520
    @skyv26
    Posted over 3 years ago

    Hi! I saw your work, I noticed issues that are written below:

    1. input field padding more than required, I mean just look at your field, your placeholder is in center and it look little bit bad.

    2. You haven't change the image in mobile view as per requirement, So i would suggest you to do work according to given requirement.

    You did good work by adding custom validation with custom message. I hope you understand above 2 issues.

    Good Luck

    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

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

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub