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

Newsletter sign-up form solution through TailwindCSS and RegEx

Abdullah Zafar•180
@ei-abdullah
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 making my first project using TailwindCSS and regular expressions and for my future projects, I want to enhance my tailwind CSS further more.

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

I faced problems when I was creating regular expression patterns for the valid email address and through the help of chatGPT, I was able to understand and implement it for faster email validation.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Danae Lescano•270
    @Lescano713
    Posted 12 months ago

    Here are three improvements you could make:

    Order of CSS Files: Ensure that style.css is loaded after output.css if there is a possibility of style conflicts. This ensures that custom styles in style.css take precedence.

    Descriptive alt Text for Image: Update the alt attribute for the image to provide a more descriptive text. This enhances accessibility and SEO.

    Comment in JavaScript: Add a comment in the JavaScript code to explain the purpose of the code, improving readability and maintainability.

    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.

Oops! 😬

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

Log in with GitHub