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

Newsletter sign-up form with success message

tailwind-css, typescript, vite
Olexii Bulhakov•300
@bulhakovolexii
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?

This was my first time using Vite to automatically bundle HTML, CSS, Tailwind, and TypeScript. I am proud of the result, as the setup process turned out to be faster and more flexible compared to traditional bundlers.

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

I encountered issues with relative paths not working correctly when publishing to GitHub Pages. To fix this, I had to explicitly set the base option in the Vite config and connect Tailwind through a plugin:

// vite.config.ts
import { defineConfig } from "vite";
import tailwindcss from "@tailwindcss/vite";

export default defineConfig({
  base: "/newsletter-sign-up-with-success-message/",
  plugins: [tailwindcss()],
});

Additionally, setting up GitHub Actions for automatic deployment was necessary. I used a static.yml template and added an extra build step:

- name: Build
  run: npm run build
What specific areas of your project would you like help with?

Currently, I am resetting the application state by triggering a page reload via an <a href=""> element. I would like to find a more elegant solution using TypeScript, such as resetting the state without a full page reload. However, my current knowledge of TS is not sufficient to implement this yet.

<a href="">Dismiss message</a>
Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Amiko Elvis•260
    @amikoelvis
    Posted 2 months ago

    Your code is clean, well-typed with TypeScript, and the validation logic is solid. However, replacing the entire main content with innerHTML isn't ideal consider toggling visibility instead. Also, the "Dismiss message" link doesn't work as expected; use a button or prevent the default behavior. Overall, great job with structure and user feedback handling.

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