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

css js countdown

Dharmik_487•1,740
@Dharmik48
A solution to the Launch countdown timer challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Just did another challenge, to be honest it was the most challenging one I did so far. I really wanted to the flip animation but I couldn't do a refined version, please teach me how to do it if you know how to🙏.

Also suggest for any improvements I can do.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Marlon Passos•920
    @MarlonPassos-git
    Posted over 3 years ago

    hello Dharmik_487 congratulations for having completed your 7th WEF challenge, I liked your solution, there was only animation hehe

    • Regarding animation, it's a bit complicated because I haven't done it yet, I would recommend you look for good solutions to this challenge and try to understand the code of others, if you're patient, there's this video here where a guy shows how he did it https: //www.youtube.com/watch?v=t56nSwjozf0

    • The stars they only occupy the middle of the screen, the borders are missing on larger screens, see https://prnt.sc/1tqrjjc

    • In the footer about social media I would have put them in a list <ul>

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