Update contributing guide

[cassidoo]

Right now CONTRIBUTING.md could use some more guidance at the top.

Add more of a walkthrough for users, for example:

• "If you want to add a new event, go here"
• "If you want to add a new resource, do it like this"
• etc.

Also, add contribution guidelines for folks wanting to do minor fixes like typos, or more structural code changes.

[iambel]

hi!
i'd like to work on this issue, if it's still available. thanks (●'◡'●)

[cassidoo]

@iambel go for it!

[adiati98]

Love this initiative! ❤

We might as well want to consider having:

• if folks should or no need to create issue before working on a fix
• if folks can go ahead working on an issue and creating a PR without asking permission or if they need to ask permission first and get assigned

Which one to apply is maintainers' call. 👍🏼

Also:

• As there is no issue form & PR template yet in this repo, what info would you want to have in the issue & PR from contributors? For example:

  • Issue: Clear description, how to reproduce a bug (if it's bug reporting), screenshot/screen recording if it's UI related, etc.
  • PR: Clear description, link to the issue (if any), etc.

Edit: What I mean by issue form here is the form to submit a bug report and feature request.

---

Adding clarity might be helpful for new (even experienced!) folks in OSS. And it'll make the maintainers' tasks lighter as well.😊

I'll chime in more ideas when I can think more! ✨

[LukysYeep]

Hi!

I am looking forward to fix this issue if it is still open, thanks!

[adiati98]

Hey @LukysYeep ,
This issue is already assigned. You can see at the "assignees" section on the right. 🙂

[LukysYeep]

Oh my bad, I did not notice @adiati98 ,
is it fine, if I collaborate on this issue? 😊