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

Newsletter subscrition

sass/scss
P
clickglue•440
@clickglue
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?

Learned SASS

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

Styling placeholder in input field with SCSS

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    thibault.deverge•310
    @thibault-deverge
    Posted 8 months ago

    Hey, you've done some really great work here, well done!

    About the visual:

    • Some design elements are slightly different from the Figma file, like the border-radius being smaller and the background color not matching exactly. However, I actually prefer your version to the original design. Maybe that was intentional?
    • The responsiveness is broken between around 768px and 1000px. You might want to adjust the breakpoint to fix this, or avoid using a fixed width on the card in the desktop layout. Instead, you could use a percentage of the page width with a max-width, allowing the newsletter to adapt smoothly and grow with the screen up to a certain point.

    About the code:

    • I personally love the BEM naming convention for classes, and it's widely used professionally. It works especially well with SASS's nesting feature. It's a personal preference, but if you're unfamiliar with it, you might want to look into it and see if it suits you. :)
    • Consider using more variables for colors, font sizes, font weights, etc. For a small project, it’s not critical, but if you ever want to revisit the design, using variables will allow you to change things like the primary color across the project easily. It’s also useful if a client wants to make quick adjustments.
    • Also, not a big deal, but you could remove unnecessary files like the original README, template README, or HTML comments in index.html to keep things clean.

    As you can see, these are just small suggestions, as the code is really clear and the project is very well done. I hope some of this is useful. Wishing you the best with your next project! :)

    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 1st-party linked stylesheets, and styles within <style> tags.

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.

Oops! 😬

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

Log in with GitHub