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

Mobile first responsive page using HTML, CSS and vanilla JavaScript

Nick Carlisi•180
@nickcarlisi
A solution to the Pod request access landing page challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


This is my third challenge and I'm pretty happy with it. The first challenge was simple enough that I didn't really have to worry much about responsiveness. For the second challenge, I didn't use a mobile first approach and after getting the layout looking good on large screens, it fell apart on mobile size(s), and I had to start over again. This time around I used a mobile first approach and it was soooo much easier. Quite happy with the way this turned out, but of course, always open to suggestions for improvements, tips, etc. As for the javascript, I did have to look up how to verify an email address and found some crazy code that I can't imagine myself (or too many other people) coming up with. If there are better ways to do this, please let me know. Thanks!!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Matt Studdert•13,611
    @mattstuddert
    Posted almost 4 years ago

    Nice work on this challenge, Nick! I'm glad to hear you found working mobile-first to be a big improvement. I find it a much simpler workflow and find it leads to less code, which is always nice!

    As for the email validation, I'd recommend changing the type attribute on the input to be type="email". You can then listen for when the form is submitted and use the JS Validity State API to check whether it is a valid email pattern or not.

    As for improvements, you can see in the design comparison slider a few small sizing and spacing differences with the design, which could be tackled. But it's nothing major.

    I hope this helps. Let me know if you have any questions! 🙂

    Marked as helpful
  • Bulumko Papu•180
    @bulumkopapu
    Posted almost 4 years ago

    Hey Nick

    Great work and dig your interpretation. I like what your JS logic its short and sweet.

    Its a pity that Front End Mentor leaves it up to us to decide how the design should look like In-between devices. I find it tricky myself to decide how elements should interact and shift.

    I would look into your code that dictates how things look for tablet (768px). If you look at the design file @768px (device width) you'll see that there a specific layout the designer has prescribed. Your layout could use just little bit more tweaking to look exactly like the design at that specific width.

    I love your mobile interpretation as well. All in all great stuff!

    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.

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

Oops! 😬

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

Log in with GitHub