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

Newsletter sign-up with success message using Grid

John Carruthers•310
@techyjc
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


I managed to keep the entire form post interaction contained within the same page. I normally use PHP for form submissions (POST method combined with the PHP Super-Globals).

I think you can use Fetch in Javascript for the POST method but I've didn't think that was necessary in this case and the form GET method is best avoided for user data.

Used some data attributes in various elements to show/hide various sections. and took advantage of this as you can format with CSS using an attribute selector .something[attrib="value"]

The transition between break points is a little jarring but It's about practice not perfection.

You decide.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Marcus Azevedo•40
    @marcusAzevedo93
    Posted over 1 year ago

    Congratulations on solving your challenge! I noticed that you need to move down the address div a bit. You could also bold your h1, increase the font size, and center it. Overall, I really liked it, and I even found yours more beautiful than the original. 😊

    Marked as helpful
  • John Carruthers•310
    @techyjc
    Posted over 1 year ago

    Hi Marcus,

    Thank you, very kind of you. I had made a few adjustments after you commented but before seeing your comment. The email address on the Subscription Success element is a nested empty 'span' with a class. I push the email address entered by the user into the span using JS '.innerHTML'. I completely forgot to style the element at the time.

    I will be updating the email entry form to use regex to validate the correct email address as it's never a good to rely on form elements for proper validation. (Even with HTML 5 feature set). Although probably not as important, as the user could bypass the JS as well.

    John Carruthers.

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

Oops! 😬

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

Log in with GitHub