I think we need a site like https://godoc.org for drone plugins.
The godoc site is that it is generated on the fly and the repository data is cached in a redis database, and is periodically refreshed. This solves an issue we have today with stale plugin documentation needing to be manually refreshed.
The on the fly generation should be possible simply by reading the
.drone.yml file and parsing the
plugin section. Any repositories lacking this information would yield a not found error. This means the plugin website could contain not just official plugins, but could also contain unofficial plugins from 3rd party authors. This will encourage more people to fork plugins, instead of expect customizations that tailor to their exact workflow.
The site would be rather simple with just a few endpoint:
/ would be the main page with some sort of search capability and list of most popular plugins
/owner/name would show the specific plugin repository in github
This idea is also inspired by Chef Supermarket (which I've never used) but seems like a great way to encourage community members to submit their chef scripts. See https://supermarket.chef.io/. The primary difference here is that a godoc approach auto-generates the website, on the fly, without having to rely and end-user data entry.