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

Responsive Landing Page using html/css/javascript

Abdullah Nassif•405
@AbNassif
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


Struggled a bit with a problem caused by the content overflowing the body element. Realized that since I assigned a height of 100% for both the HTML and BODY, it was wrong to give the MAIN element a height of 100% as well, as you want it to pay attention to the height of the content inside of it not what is available by its parents.

Let me know if you have a better approach, and thank you for your time!

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

  • Aakash Verma•9,500
    @skyv26
    Posted over 3 years ago

    Hi! Abdullah, Really nice work, even it is responsive too. But still there are some issues in your work and it takes only 20 min max to fix all issues that I am going to tell you via this feedback

    1. The main part of this challenge is email validation and I would say you made it nice, I mean the custom message and icon you placed perfectly. But your email validation logic is not 100% correct. As I tried abc@gef and hit button then it successfully submit without any issue. So I think it should need to fix.

    2. In your mobile view your text content and email submit button is not aligned properly. I mean in mobile view your button is touching the right edge of mobile screen and your main text need some margin at both side (left and right) in order to make it little bit good to eye.

    Overall Nice work. I hope you understand above minor issues.

    Best of 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
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.

Oops! 😬

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

Log in with GitHub