As a request from PackElend, I create this post to discuss what shall be shown in the Website Plugin.
I've posted the rough outline for the info that should be shown in the devlog. And I believe it's better to list all the fields we need now.
Here is the list and its source:
manifests.json from joplin/plugins
name
version
description
author
keywords
category
app_min_version
stats.json from joplin/plugins
download count
create time
README from plugin creators' repo
Is there anything else that you want to add to the page or something is unnecessary to be included? Any feedback would be appreciated!
Ok but it seems you expect people to answer your post and provide their opinion? (I'm not even sure?) It's very vague as it is, so maybe try to make the post self-contained, and add an actual question if you want some feedback.
that is good news, @Retr0ve may you pick up this offer
beisded these could you work on a prototype, regardless its UI, to show that you are able to pull all information we wish to see.
It could be, that the GitHub readme etc. needs to provide information differently formated and so on...
As for images, we'll probably allow developers to specify one at some point. I think it's quite important especially we have a website like this to showcase the plugins.
In the meantime, if an image is necessary maybe you can set it based on the category. For example, a paintbrush for the "theme" category, a cog for the "dev" category, etc.
we would like to see a prototype which shows all the promised features.
Where information is missing you can use dummies.
You can use your plug-in, to show how it shall be presented on GitHub e.g. first paragraph, one to three lines describing it in nutshell, than pics or gif, then details, then installation ....
Yes, these data are from GitHub. And I'm pulling data using the Github API. I mean, these Infos are pulled from joplin/plugins repo and the README file, and maybe other relevant docs are pulled from plugin creators' repos.
Thanks for the hint, I'm aware of it, the trending plugins will be based on the stats.json. The README file is for detailed description of a plugin since it might be the only doc that some plugin provides.
My idea is that in addition to comments and ratings, we could have a way to advertise plugins.
For example, the Google search engine to make the first pages accessible charges an ad fee.
The same case could be used here, we could have plugin ads so that the community itself has the benefit of having the money invested in the community itself.
For example, I could donate money on the joplin plugin site so that my plugins are seen first. That would make sense, if I wanted more people to install it.
@Retr0ve correct me if I'm mistaken but the current concept does not allow this.
The website simply pulls the available plug-ins from the invotory site on GitHub and pulls additional information from each plug-in's repo.
The information required for Google to have each plug-in be well indexed has to be added to a plug-in's site (repo). I doubt that we can fill the plug-in website information of each plug-in to make them listed well on Google.
Thank you all for feedback ;D But... I archived this idea of paid ads and plugins. My current idea was just to show the number of Downloads, Comments, Ratings, Installations.
