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

Tailwind CSS

Michelle Wayua•150
@Mishywayu
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 used HTML, Tailwindcss, JavaScript, and deployed it on Netlify. Reviews are highly appreciated

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Krishna Vishwakarma•1,390
    @KrishnaVishwakarma1595
    Posted over 1 year ago

    Hey, @Mishywayu

    Congrats on completing the challenge.

    I've got a few points to mention -

    • While working with the Forms we should use <label> element for input labels. For example you can use <label > tag instead of <h2> tag like this -
    <label for="email-input" class="font-bold">Email address</label >
    <p class="hidden text-red-500 text-sm text-right font-semibold" id="invalid-msg">Valid email required</p>
     <input type="email" name="" placeholder="email@company.com" class="mt-2 p-3 w-full border border-slate-500 rounded-lg cursor-pointer" id="email-input"/>
    

    So, we can focus the input automatically by clicking on the label. If there isn't any use case to define a label like this just the input field with a placeholder, in that case too we should define the label using the aria-label attribute.

    • You can start using HTML5 Semantic elements

    • There are some responsiveness glitches for tablet screens which makes the design bit unresponsive. What you can do is make the main container width: 100%` and some padding around the body.

    I hope these points will help you. Nice solution.

    Happy Coding

    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