Ecosyste.ms: Awesome

An open API service indexing awesome lists of open source software.

Awesome Lists | Featured Topics | Projects

https://github.com/yashi-singh-1/day-32-counter

I wonder how high or low is the maximum you can count here? The transitions are pure CSS, but I used some JS for the counting.
https://github.com/yashi-singh-1/day-32-counter

100-days-css 100-dayscss 100dayscss css css-challenge css3 csschallenge html html-css html-css-challenge html5 html5-css3 html5css3 htmlcss htmlcsschallenge javascript vanilla-javascript vanilla-js vanillajavascript vanillajs

Last synced: 4 days ago
JSON representation

I wonder how high or low is the maximum you can count here? The transitions are pure CSS, but I used some JS for the counting.

Awesome Lists containing this project

README

        

Counter

Challenge Description

This challenge features an interactive counter built with HTML, CSS, and JavaScript. The counter includes buttons to increment and decrement the number displayed, with smooth animations and gradient background transitions.

Preview

Counter Preview

Live Demo

Check out the live demo here.

Credits

This search component is based on a design from 100 Days CSS Challenge - Day 32, with modifications made to suit challenge requirements.

Prerequisites


  • HTML and CSS Basics

Tools Used


  1. VS Code (You can use any other code editor)

  2. A modern web browser (Chrome, Firefox, Safari, or Edge).

  3. Access to an internet connection for resource imports.

Contributing

If you'd like to contribute to this challenge:


  1. Fork the repository on GitHub.

  2. Clone your forked repository to your local machine:

  3. git clone https://github.com/Yashi-Singh-1/Day-32-Counter.git

  4. Create a new branch for your feature or bug fix:

  5. git checkout -b feature-name

  6. Make your changes and commit them with a clear and concise message:

  7. git commit -m 'Add new feature or fix'

  8. Push your changes to your forked repository:

  9. git push origin feature-name

  10. Open a pull request to the main repository.

  11. Ensure your pull request includes a detailed description of your changes.

  12. Respond to any feedback or questions during the review process.

We welcome improvements, bug fixes, and additional features that can enhance this Counter.