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

Responsive Coming Soon page using HTML, CSS and JS

Hoophelie•110
@HOOPhelie
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


Hey, everybody! 👋

My solution is definitely not pixel perfect, but I tried to make it look pretty on both mobile and desktop! (I'll make the pixel perfect version very soon) It seems to work ok, I'm just not sure of the cleanliness of my code... Any feedback would be much appreciated!

Thank you and happy coding🤗

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Rabin Gharti Magar•455
    @Rabin92
    Posted over 4 years ago

    Hey, Hoophelie! 👋

    You have done a great job on this challenge! 🙌

    The site is fully responsive and looks great on all screen devices. Nicely formatted code with semantic tags in use.

    There's just a minor issue with an overlay as it does not fully expand to viewport size on a small screen landscape mode. To fix this issue, you can follow these steps:

    Add this code to the body tag:

    body {
    position: relative;
    }
    
    

    Remove width & height property from .overlay class and add the following code instead:

    .overlay {
    top: 0;
    right: 0;
    bottom: 0;
    left: 0;
    }
    

    And lastly remove height property from a small screen devices with the class name of .landscape-page and add it to the media queries for a medium-large screens.

    To fix the accessibility issues, you can simply add a label tag. Learn more about these tag here: https://www.w3schools.com/tags/tag_label.asp

    Hope this helps and Happy Coding! 😊

  • ApplePieGiraffe•30,525
    @ApplePieGiraffe
    Posted over 4 years ago

    Hey there, Hoophelie! 👋

    Nice to see you complete another challenge! 😀 Nice job on this one! 👏

    One more tiny thing I might suggest in addition to Rabin92's helpful feedback is to perhaps add overflow-x: hidden to the body to prevent a horizontal scroll bar from appearing along the bottom of the screen in the mobile layout (or set the width of the image in the mobile layout to 100%, since the image is the element that's overflowing the body and causing this issue, and adding that seems to solve it). 😉

    Keep coding (and happy coding, too)! 😁

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

Frontend Mentor for Teams

Frontend Mentor for Teams helps companies and schools onboard and train developers through project-based learning. Our industry-standard projects give developers hands-on experience tackling real coding problems, helping them master their craft.

If you work in a company or are a student in a coding school, feel free to share Frontend Mentor for Teams with your manager or instructor, as they may use it to help with your coding education.

Learn more

Oops! 😬

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

Log in with GitHub