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

Responsive Newsletter Sign Up using React + Vite

react, vite
ren•50
@ktmagno
A solution to the Newsletter sign-up form with success message 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'm proud of accomplishing the whole challenge using React + Vite (which was VERY challenging for me 🫠). It's not perfect, but I believe it serves its purpose so I decided to upload it. Next time I want to learn Sass or enhance my skills in React.

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

I encountered many challenges, from building up to deploying. That's why I relied more on YT tutorials.

What specific areas of your project would you like help with?
  1. How to change an image/illustration when the screen size changes to mobile view
  2. Error state input field
  3. There's a huge white space appearing below the button when the user inputs invalid email (mobile view)
  4. Footer not showing

Update:

  • problems #3 & #4 are fixed, all thanks to @Code-Beaker 😁
  • displays an error message if the input field is empty upon submission
Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Tharun Raj•1,330
    @Code-Beaker
    Posted about 1 year ago

    Hi there, congratulations on completing this challenge. You've done a great job here! 🎉

    I will try my best to answer the questions you've shared.

    • To switch the images on different screen sizes, we usually use an HTML attribute called srcset. It is used to create responsive images on the web without the use of CSS. This property also helps in increasing the performance of your website by loading the appropriate image with the required size, dimensions, etc. Here is an example syntax:
    <picture>
    <source media="(min-width: 50rem" srcset="folder/DesktopImageFile"/>
    <img src="folder/MobileImageFile" alt="My responsive image"/>
    </picture>
    

    Here, the browser will automatically load the larger image when the screen size is 50rem or above. Otherwise, it will be a smaller image that's meant for mobile phones or other smaller screens.

    • I checked the error state and it seems to be working as expected. But, If I submit the form leaving the input empty, it displays no error.
    • The whitespace might have been caused by position: absolute that you've used to centre the component on the screen. Fortunately, there is an easier way to centre things on the screen!

    On the main container, give a min-height: 100vh, so that the content doesn't get hidden on a taller viewport. Then use a simple flex layout to centre things.

    .signup {
    display: flex;
    justify-content: center;
    align-items: center;
    min-height: 100vh;
    }
    

    Using this will remove the issues caused by position: absolute and related properties on the .newsletter.

    • Using the above layout will fix the issue of the footer getting hidden.

    Aside from these, I would like to share some of my suggestions regarding your code.

    • Use relative units like rem instead of absolute units like px. This will be better when handling responsive layouts. This can be used for various properties including font sizes, padding, margins, etc.

    Hope this helps you improve your solution! 😃

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