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

Launch Countdown done with NextJS (TS) and animation with pure css

next, react
Anto Joy Nellissery•80
@antojoy23
A solution to the Launch countdown timer 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?

Using NextJS was an overkill for this challenge. But since I wanted to learn more about NextJS went ahead with it. If not would have gone for just React with Vite bundler without any framework like NextJS.

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

The animation to do the flip was challenging, checked out some online resource on how to do it and implemented it in a way which I would easier to implement in react and less use of dom manipulation

What specific areas of your project would you like help with?

I feel the animation can be better, maybe i need to use some external animation framework like Gsap but thought it would not be required for this challenge.

Would like to create a more realistic flip which flips the entire half of the container. The current implementation feels like only the number flips.

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

  • Kim Fransson•420
    @kim-fransson
    Posted 5 months ago

    Hi! Nice work, really like the overall structure and look and feel. Here is some quick feedback.

    Tips

    Insted of creating two divs for the background images, you could stack images using the background property.

    html {
        background: url("./assets/images/pattern-hills.svg") bottom / contain
            no-repeat,
          url("./assets/images/bg-stars.svg") repeat, var(--very-dark-blue);
      }
    

    First background layer:

    url("./assets/images/pattern-hills.svg") → Sets an image as the background.

    bottom / contain → Positions the image at the bottom and scales it to fit while maintaining its aspect ratio.

    no-repeat → Ensures the image appears only once.

    Second background layer:

    url("./assets/images/bg-stars.svg") repeat → Uses another image that repeats across the entire background.

    Third background layer: var(--very-dark-blue) → Sets a solid color (--very-dark-blue) as the base layer.

    Since CSS backgrounds stack, the solid color appears underneath, the stars repeat over it, and the hill pattern is placed on top at the bottom of the viewport.

    Animation

    This one may be a bit trickier and would probably break the current css. But you need to play around with perspective, transform-style: preserve-3d; and backface-visibility: hidden;.

    Here are an example of 3D like rotation. 100days CSS and the codepen. You may also need to play around with perspective-origin.

    Fun personal touches

    • Try to add sound effects for the countdown, and maybe even some background music? When adding sound you will probably need to add a on/off toggle (a lot of browsers suppress sound before interacting with the site).

    • Try and animate the background stars, maybe add a small rotation, making it look like the "earth is rotating".

    All the best, // Kim

    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

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.