tauri-apps / tauri-apps/tauri-docs
[docs] [plugins] Community plugins aren't visible enough
Nobody has claimed this yet.
- Dominant language
- MDX
- Stars
- 1.1k
- Forks
- 887
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 48
Description
Following this discussion with @FabianLars , I create this issue.
I mainly use Tauri for the mobile part, and while Tauri mobile is still quite young, its growth is, imho, probably undermined by the lack of two things :
- visibility : some plugins that cover (sometimes) basic stuff must be dug on github or crates.io (mobile task scheduler, mobile intents...)
- consensus: a lot of plugins do the same thing. While it's normal in an open source community to see multiple approaches of the same problem, newcomers should be able to select the default, battletested, community approved approach. The Push Notifications feature depicts well this case.
Here are some possible actions to address these two issues, from quite to less easy :
- Reorganize the community ressources page. Plugins should be filtered or searched by platforms at list, or with a basic search term. This would allow to search among the curated list, and that's a good start.
- make a kind of crates.io wrapper site, that would query crates.io results by only matching tauri-plugin-* results. This way we could search among all the published crates, even when their owned hasn't opened a PR on awesome tauri. With this you could also view and compare different plugins that treat similar use cases.
- On this wrapper site, "Rank" plugins with a metric / label that shows consensus. Github stars are a good start, but this is platform centric. Labeling good plugins could also be done, maybe a kind of "seal of approval" given by the maintainers or the community for a given usecase ? This may be done through surveys to the community
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the community resources page linked in the issue and review how community plugins are currently presented. The issue lists several possible directions, from filtering the curated page to building a crates.io wrapper and adding rankings; a maintainer decision is needed before implementation can begin. Done should mean the selected discovery or consensus improvement is documented and its scope is agreed.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100