Maintenance: revamp contributing guidelines in docs

[dreamorosi]

Summary

The current contributing guidelines are overly verbose and somewhat hard to consume. The Python version of Powertools has adopted a new structure that moves the bulk of the information from the repo to the documentation which I think could benefit the project.

The CONTRIBUTING.md will still be present in the repo as it's surfaced to contributors opening issues or PR, but it will contain only the highlights of the process, and then link to the main docs for further information/context.

Why is this needed?

Revamping the contributing guidelines and adding them to the documentation website will give us more freedom to format and organize the information in a way that is easier to digest.

We hope that this change will make it easier for prospecting contributors to get involved.

Which area does this relate to?

Other

Solution

Adopt a similar structure.

Acknowledgment

• This request meets Powertools for AWS Lambda (TypeScript) Tenets
• Should this be considered in other Powertools for AWS Lambda languages? i.e. Python, Java, and .NET

Future readers

Please react with 👍 and your use case to help us understand customer demand.

[github-actions]

⚠️ COMMENT VISIBILITY WARNING ⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.