Since then, thanks to commitment from @baris.leenders and @makhan , we made quite a few changes based on your feedback:
removed uninformative banners;
introduced the new tab for packages you are subscribed to;
introduced consistent update dates throughout the Exchange – now the date of the update is the date when the last version was uploaded;
the search results now show both the date when the package was uploaded and the date when it was last updated;
screenshots can now be added to the descriptions of the packages, as long as they are linked from the place where they are permanently hosted;
There are also changes that are not visible but will improve the efficiency of the Exchange.
As well as changes that are in review or in the works – for example the option of discussing the packages on the Forum.
We hope that together with you, we will be able to keep improving the Exchange.
That is why if you have any ideas, or are ready to share your experiences when using the Exchange, please let me know or email me at community@checkmk.com, so we could set up a call and discuss your perspective.
Thank you for working on Exchange. At the moment, there is still one issue that bothers me. When I upload a package, I have to fill in a description. Why? Why not use the description from the uploaded file?
The description from the uploaded file is shown in the version description and the one above is the general package description that is shown on the exchange for all versions, and is stable (unless you want to change it within the Exchange).
A lot of the version descriptions I saw were mostly applicable to a specific version – for example they include a short changelog or some pointers on how to use the plugin efficiently in this specific version. While the general description is there to simply state what is the higher level purpose of the plugin.
Can be the very same text though, if you prefer it this way
Edit: the general description also allows for more formatting, adding pictures and much more, again – if you wish to do so
@Sara
I see. Might be still a good idea to first read the description form the package then let the user modify it. The second issue, it took me quit a bit to find that you can switch the litle input field to a full editor. Maybe would be easyer if you switch this to the default view.
