Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted over 3 years ago

Mobile first countdown timer with BEM and Sass

bem, sass/scss
Yemisrach•1,430
@Yemisrach15
A solution to the Launch countdown timer challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hello members of frontend mentor community,

I have completed yet another intermediate challenge. This one took me around 2 months to complete😅. I couldn't get the animation quite right. So if you've got any improvement suggestions, I'm open. Any other feedbacks are also appreciated.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Rio Cantre•9,650
    @RioCantre
    Posted over 3 years ago

    Hello there! Awesome job with this challenge! Viewing your solution, you did well with the design and functionality. I would suggest the following for you..

    • Adjust the bottom margin of the icons in the .social__icons into 4rem
    • Import the attribution style in the CSS file and remove style tag
    • You can simplify the footer icon with this HTML structure...
    <li class="social__icon">
              <a href="#" class="icon icon--facebook"></a>
     </li>
    
    

    Over all you did well and Keep up the good work!

    Marked as helpful
  • Travolgi 🍕•31,300
    @denielden
    Posted over 3 years ago

    Hi Yemisrach, congrats on completing the challenge!

    I had a look at your solution and I have a few suggestions to improve your code:

    • Try to use Flexbox for center the element in the page: read here ->Flex guide Note: Flexbox aligns to the size of the parent container.
    • To fix the position of the hill image in the background change the value of background-size in contain.
    • Try to adding a little transition on the social hover effect
    • In javascript avoid using innerHTML unless strictly necessary: its use creates a security hazard. Rather use innerText which is the same thing but does not parser html [read here] (https://www.w3schools.com/jsref/prop_node_innertext.asp)

    In the end Instead of using 4 identical functions that perform the same task but with different times, try to use only 1 function by passing it the different parameters.

    Overall you did well :) keep it up 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

Oops! 😬

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

Log in with GitHub