Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted over 1 year ago

news-letter-sign-up using CSS and Javascript

Eric Anderson•140
@shinhosuck
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


On this project the hardest part was adjusting the height for the image on sign up page/index page when transitioning from mobile to large screen. I eventually figured it out by using flex-box and grid. Also, on success.html on mobile, the success card gave me some issues. As the screen got smaller, the card height would shrink and the card parent container would show with dark background. I fixed this issue with little bit of JavaScript.

I have some question regarding CSS.

  1. What is the best practice when working with images?
  2. How to organize CSS?
  3. Best practice for naming selectors?

Thank you very much for your help!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Antonain E.•220
    @antoebtfr
    Posted over 1 year ago

    Great job ! 👍

    • Missing the cursor: pointer on the subscribe button
    • ash@loremcompany.com is static in the success modal. Try to set it dynamically. Ask me if you need help

    Answering questions

    1. Depends of the project and of the situation
    2. In the project architecture or in a CSS file ?

    Architecture :

    Depends of the structure, frameworks, CMS used but essentially you regroup them in style folder with different files like style/main.css, style/card.css

    Ex : https://github.com/antoebtfr/fM_TODO_list/tree/master/styles

    File :

    No organisation needed, it's not like scss. Just try to not duplicate the selector like .news-container at line 34 and the same .news-container at line 356 so try to search ( with the command ) in the file if there is no selector yet. If there is media queries in the file try to place them at the end but it's not a "rule"

    3.Make it obvious, and use kebab-case

    It triggers me so much to see the "Challenge by" like this. So ugly😂

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