-
-
Notifications
You must be signed in to change notification settings - Fork 106
merge dev to main (sponsors and contributors) #1071
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
WalkthroughWalkthroughThis update introduces a new section in the README dedicated to showcasing sponsors and contributors, complete with images and links. It aims to encourage sponsorship by highlighting the community's support visually, thus fostering greater engagement and potentially attracting further development resources. Changes
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (invoked as PR comments)
Additionally, you can add CodeRabbit Configration File (
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please also consider [sponsoring our work](https://github.com/sponsors/zenstackhq) to speed up the development. Your contribution will be 100% used as a bounty reward to encourage community members to help fix bugs, add features, and improve documentation. | ||
|
||
## Sponsors | ||
|
||
Thank you for your support! | ||
|
||
<table> | ||
<tr> | ||
<td align="center"><a href="https://github.com/j0hannr"><img src="https://avatars.githubusercontent.com/u/52762073?v=4" width="100" style="border-radius:50%" alt="Johann Rohn"/><br />Johann Rohn</a></td> | ||
|
||
<td align="center"><a href="https://github.com/baenie"><img src="https://avatars.githubusercontent.com/u/58309104?v=4" width="100" style="border-radius:50%" alt="Benjamin Zecirovic"/><br />Benjamin Zecirovic</a></td> | ||
</tr> | ||
</table> | ||
|
||
## Contributors | ||
|
||
Thanks to all the contributors who have helped make ZenStack better! | ||
|
||
#### Source | ||
|
||
<a href="https://github.com/zenstackhq/zenstack/graphs/contributors"> | ||
<img src="https://contrib.rocks/image?repo=zenstackhq/zenstack" /> | ||
</a> | ||
|
||
#### Docs | ||
|
||
<a href="https://github.com/zenstackhq/zenstack-docs/graphs/contributors"> | ||
<img src="https://contrib.rocks/image?repo=zenstackhq/zenstack-docs" /> | ||
</a> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The addition of the sponsors and contributors section is well-executed, enhancing the README with visual acknowledgment of support. However, consider the following improvements for accessibility and consistency:
- For images, adding
alt
text descriptions improves accessibility for users with screen readers. Ensure all images have meaningfulalt
text. - The use of inline styles (e.g.,
style="border-radius:50%"
) for images might not be consistent with the rest of the README styling. If the README or the project has a CSS stylesheet, consider moving styles there for maintainability. - Verify the links to ensure they are correct and lead to the intended profiles or pages. Broken links can detract from the user experience.
- Encourage sponsorship with a clear call to action. The section "Please also consider sponsoring our work" is a good start, but consider making the call to action more prominent or providing more details on how sponsorship can help.
Summary by CodeRabbit