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

Responsive Newsletter Sign-up form with HTML, SCSS, JS and Vite

accessibility, bem, sass/scss, vite
Adesh Katiya•420
@adeysh
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?

Proud of making it accessible to all with strong email validation. Made the HTML and SCSS structure/workflow that I have been using all along to create this testing my responsive design skills.

I would try to switch between classes efficiently next time. I have to look at how other people try to code when they are doing operations like hiding elements or popping them up on button clicks.

What challenges did you encounter, and how did you overcome them?
  • oof..😅 I encountered a lot of challenges. Some of them I forgot to bookmark to make a note on the readme as they really helped me with specific way of doing things (stackoverflow buddies!).

  • I was confident about the js part since it wasn't much, but had some issues with dom manipulation.

  • Including reponsiveness using scss was difficult for me. But looking at how other people who created mixins for that helped me a lot.

  • Other than that it was just problems with placing the content at right places with proper gaps and all.

What specific areas of your project would you like help with?
  • I used a simple way of showing and hiding the elements on the page by adding a hidden class on the element that I wanted hidden. Is it the standard way of doing things like these when using plain vanilla js or are there other ways of doing that?

  • If I am being provided with svg's then should I use them in html code directly or rather use img tags. which approach I should be using?

  • I did not know that you can't add a background-color to a button if the color is a gradient. Spent some time searching for answers then I understood about how do you actually provide a simple gradient to a button background with a transition.

  • I wanted to ask if there were any other ways you could add a background gradient on a button without using the pseudo-elements and opacity property that I used.

  • When I reused some classes I was challenged with the styles that I used previously being overridden by other styles used for responsiveness. So rather should I create new classes for such cases or give priority to the base classes?

These are some of the questions that I would want to explore. If you could provide me with some valuable suggestions I'll be grateful to you.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Matthew Sheldon•320
    @MatthewNgabirano
    Posted 4 months ago

    I have no feedback now

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