Episerver Nuget site up-to-date changes
Hi guys, I hope you are all doing well today :)
Recently, Episerver Nuget site made several major changes for new CMS 11, Bootstrap 4.1 and Nuget Server 2.14, as long as security update for the whole site. The old design seems legacy and not so user-friendly so that an UI improvement was carried out with responsive support.
Package Details page allow you to view more information and also provide with manual download:
There is additional information for Version download count and total download. Before Mar 18th 2018, we didn't separate version download count for each version, so the count in the past reserved as Previous and we also have single version count after that point of time.
We hope that the improvement above build up better user experience for you when you get along with Episerver framework and related packages.
As always, any suggestion or feedback please send to epw@episerver.com or mine as khanh.nguyen@episerver.com
P/S: There are several Easter eggs within the site. Hope you find it interesting and have fun :)
looks really cool! I'm lazy and would like to have copy install command to clipboard :)
also think when package has dependency to precise version (e.g. browsing this package https://nuget.episerver.com/package/?id=EPiServer.CMS.Core&v=11.1.0) if I click on EPiServer.Frameowrk dependency - I would expect to open that specific version of the package (not latest current).
also would be nice to browse by tags.
Looks so cool! Thanks a lot :)
I'm with Valdis on the suggestions. Also would there ever be plans on automating the upload process via an API? We're only just looking at creating a few packages but setting up a full VSTS package process and it would be great if we could have a step to promote a tested package in the process.
Looks much better than the old one :)
I would like the same feature of the dependency to the minimum version as mentioned by Valdis & Scott, but this is also the same behavior what nuget.org uses (if you click the dependency you are taken to the latest version of the package and not the minimum version).
The matter of not including the version into the link is that it's the maximum and minimum version only. We would like them to decide which fits user's requirement best, not provide them with something that can make a mess with their work. I'll think it twice if the request for this increasing high.
About UploadAPI: Our moderator are limit and not available with handling spamming via upload API, so no planning for this in short term.
About the content loading via http: Some are load from external resource, I'll take it into account, thanks for notice.
It's faster.
Great work @World team (Y)
Well done :)