Excellent!

I say this is ready for review!

Also, before the word release in the SVG, can you try adding Latest? It might make users clear that we are giving the latest release.

@not-nef @im-coder-lg I still think there should be a banner to inform users about new releases.

Yeah even me... Why not the banner be on the website? I mean, that's where users would head for documentation, a gist of features, and etc.
Maybe... We'll enlarge the SVG sizing and maybe modify the text(not the size) a bit.

@not-nef Maybe we can add more badges through this: https://github.com/Ileriayo/markdown-badges

Maybe these badges:

![Python](https://img.shields.io/badge/python-3670A0?style=for-the-badge&logo=python&logoColor=ffdd54)
![Gitpod](https://img.shields.io/badge/gitpod-f06611.svg?style=for-the-badge&logo=gitpod&logoColor=white)
![Vercel](https://img.shields.io/badge/vercel-%23000000.svg?style=for-the-badge&logo=vercel&logoColor=white)
![GitHub Actions](https://img.shields.io/badge/githubactions-%232671E5.svg?style=for-the-badge&logo=githubactions&logoColor=white)
![Repl.it](https://img.shields.io/badge/Repl.it-%230D101E.svg?style=for-the-badge&logo=replit&logoColor=white)

These are the ones that seem related for us; any ideas?

We could make the SVGs into links, so I could try linking them like a suggestion.

This one as well:
![Repl.it](https://img.shields.io/badge/Repl.it-%230D101E.svg?style=for-the-badge&logo=replit&logoColor=white)

I thought of it, well let's add them!

ok

it looks terrible @im-coder-lg. i wouldnt use those and just leave the release bade there. But you guys say what to do.

i mean cmon it just looks trash with that small release badge. But i say we definitely need to keep the release badge and tbh i dont think the others are that important.

@not-nef Let me try to make a custom release badge

Wait are you designing a SVG?

@not-nef that's what we need.

i mean cmon it just looks trash with that small release badge. But i say we definitely need to keep the release badge and tbh i dont think the others are that important.

Hold up! You are using HTML! Just use a width attribute inside your <img> tag!

@im-coder-lg Yours is a much better idea

@not-nef seems to be confused. I think 50px is a better idea. I will give the code here, all you need to do is replace and commit.
Don't get confused, it's so easy. Just copy the line, replace it on Line 8 and commit.
Line 8:

        <img src="https://img.shields.io/github/release/sumeshir26/TimerX.svg?style=flat-square" alt="Releases" />

To:

        <img src="https://img.shields.io/github/release/sumeshir26/TimerX.svg?style=flat-square" alt="Releases" width="50px" />

✔️ Deploy Preview for timerx-app canceled.

🔨 Explore the source changes: 3ad1eb1

🔍 Inspect the deploy log: https://app.netlify.com/sites/timerx-app/deploys/61d98efdd3324300074f7c41

@im-coder-lg @sumeshir26 what do you guys think of the new Contributing file?

Never noticed it... I will inspect it to fix grammatical issues. Also #41 needs urgent merging!

I will manage the Contributing guide. Do I need write access to edit since it's on your fork?

The contributing guide is kinda messed up. It's haywire, like my method. But don't you worry. I will fix things up. I was waiting to make this, you did! I will make the same file over at the website too!

cool

Updated the contributing guide. Made sure the base was yours, I added some extras. Maybe I'll make it easy for new people to contribute here.

Now, I can approve.

@sumeshir26 your opinions needed! PS: Some new PRs opened, please inspect)

@im-coder-lg i think we should get rid of the todo list since i dont think it belongs in the readme. if we keep it i think we should put it in another document.

Should I merge?