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

Newsletter Sign-up Form with Success Message

P
Mustapha•200
@Mustapha909
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 most proud of figuring out how to build a more complex layout and discovering the techniques needed to bring my design to life. It was a challenging process, but every obstacle taught me something new about responsive design and CSS. Next time, I'd like to streamline my workflow even more and experiment with advanced layout methods from the start.

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

One of the main challenges I encountered was structuring the layout correctly, especially ensuring responsiveness across different screen sizes. At first, some sections didn’t align as expected, and spacing issues appeared when resizing the window. To overcome this, I experimented with CSS Grid and Flexbox, adjusted breakpoints, and carefully inspected the design details. Debugging with browser dev tools and referring to documentation helped me refine the layout until it looked just right.

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

I’d appreciate some help fine-tuning my media query breakpoints. I’m looking for advice on setting the optimal screen sizes and ensuring a smooth, responsive layout transition between desktop, tablet, and mobile views. Specifically, I'm interested in learning how to adjust the breakpoints to better match the design requirements and handle edge cases where elements might not behave as expected.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Jonatan Samuelsson•540
    @jonatan-samuelsson
    Posted 4 months ago

    Well done, looks nice.

    Like you say, there are some layout issues. First of all, the success message is too large at desktop sceen size, and the spacings are off. Secopnd, at mobile size, the success message gets very stretched out along the vertical axis. Try constraining the containers vertical size and provide consistent spaces between elements to ensure the layout works as intended.

    Overall, the layout looks fine at small and big screens, but it breaks completely at medium sizes (widths between 480px and 700px).

    One small thing is that the submit button doesn't display its active state when the user fills out the form. If you want to achieve this, use the ~ selector on the input:focus pseudo-element.

    The JS is really good, particularly the validation process. One small tweak is to insert the actual email from the form into the success message in stead of the ash@loremcompany one. Easiest way I think to do it is with an empty span which you then fill using JS befor dispalying the message.

    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