Ironclad / Ironclad/rivet

[Feature]: Community Page for Sharing Charts made with Rivet

Open
#229 1 comment 0 reactions 0 assignees View on GitHub
enhancement
Dominant language
TypeScript
Stars
4.7k
Forks
388
PR merge metrics
No merged PRs in 30d

Description

### Feature Request

# Community Page for Sharing Charts made with Rivet

## Request:
I propose the creation of a community page where users can share and collaborate on charts made with Rivet. This would not only foster a sense of community but also help in showcasing the potential of Rivet through real-world use cases.

## Benefits:

Having a community page would:
- Showcase: Allow users to demonstrate the diverse capabilities and applications of Rivet through their charts.
- Collaboration: Foster a platform where users can give feedback, iterate on existing charts, and jointly create new ones.
- Learning: New users can learn from experienced ones by observing and dissecting shared charts.
- Inspiration: Witnessing the varied use-cases can inspire teams to devise innovative solutions for their unique challenges.

## Suggested Features for the Community Page:
- User Profiles: Allow users to create profiles showcasing their charts and contributions.
- Search & Filter: Provide robust search and filtering options for users to find specific charts or use-cases.
- Feedback & Comments: Enable users to leave feedback or comments on shared charts.
- Versioning: Allow users to upload different versions of their charts, showcasing the evolution of their work.

## Closing:
The addition of a community page would undeniably augment the value proposition of Rivet. It would be a nexus for collaboration, learning, and innovation. I believe this would be a significant stride towards nurturing a thriving ecosystem around Rivet.

Thank you for considering this feature request. I eagerly await feedback from the community and the Rivet team.

### Code of Conduct

- [X] I agree to follow this project's Code of Conduct

Contributor guide

Open the contributing guide

Research direction

No files, tests, or entry points are named. Start by scoping the proposed community page and resolving which features are required—profiles, search and filtering, feedback, and versioning—before identifying the affected parts of Rivet and defining acceptance criteria.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
backend, frontend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
15/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.