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

Newsletter sign-up built with Astro, Zod, and Tailwind CSS

astro, tailwind-css, zod
SmartAce•390
@Smart-Ace-Designs
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?

Using Astro Actions and Zod for the form validation. I would try to use a Vue component, as an Astro Island, the next time.

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

I wanted to use a separate Astro component as the success message, but could not find a way to show/hide it dynamically. I ended up having to scrap that idea and place the HTML for the message within the index file and use JavaScript to hide/display it.

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

I used margin to place the button in the success message at the bottom. It seems to me that there should be a better way to do this instead of using a huge margin value that I eye-balled to get right. Should I be able to use something like grid or flex to automatically position it at the bottom?

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • haquanq•1,555
    @haquanq
    Posted 11 months ago

    Hello Smart Ace 👋

    About your solution:

    • The margin for the button (success message) is not huge (to me it's small), it's ok.
    • Each page must only have one h1 to give it a title of the entire content of the page. For success message you should use h2 instead (remember when using headings don't skip any level as it's break the flow of the content and confuse users).
    • The items with checked icons is considered an unordered list in many ways (padding on the left, same icons, talking about the same thing which is what the newsletter offers), you can use ul, li to structure it (sometimes when a list have number the indicate the index - ordered list then use ol, li instead).
    <ul>
        <li>...item content...</li>
    </ul>
    

    Have a nice day and 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