Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted about 1 year ago

Responsive coming soon page using HTML, CSS, JS and Bootstrap

bootstrap, accessibility
NatSolo•110
@nataliiasolomchak21
A solution to the Ping single column 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 am proud of finishing this challenge pretty quickly.

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

I encounter some challenges with form validation and used Bootstrap fomr validation to solve this problem.

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

I need help with responsibility, is there any tip to how to make the content as responsible as possible without using a lot of media queries? Thank you in advance ;)

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Jhon Alessandro (@Master_Aless)•140
    @The-BoxHead-Guy
    Posted about 1 year ago

    Hey Nat, I've checked out your solution, and it seems amazing. I needed to zoom it a little bit as in my screen it was displayed a little bit small (I use a 1980x1080 monitor) but at the end, I could see it all

    My favorite part was indeed the validation method, you saved yourself so much time there as it's not easy to do it from zero

    On the other hand, there are several ways to make your website responsible without using many media queries summonings...

    I recommend you to take the course of responsive design from google at Google-Web-Dev as it will teach you such useful ways to develop the font-sizes of your website using the viewport width as well as learning how to use properly width and height properties and finally comprehending how to use: Unit measurements such as:

    • rem
    • em
    • px
    • ch

    What results useful for me it's to use @container and css functions such as min(), calc(), max() and so forth, as well as starting by making the "mobile-layout" first but thinking a little bit about how it'd be better to do it.

    I dare to say that it's a fact of: 50% structure and 50% of styling

    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, SASS, 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