{"id":56221,"date":"2017-07-18T00:00:00","date_gmt":"2017-07-18T07:00:00","guid":{"rendered":"http:\/\/devblogs.microsoft.com\/nuget\/nuget-gallery-gets-a-facelift"},"modified":"2017-07-18T00:00:00","modified_gmt":"2017-07-18T07:00:00","slug":"nuget-gallery-gets-a-facelift","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/dotnet\/nuget-gallery-gets-a-facelift\/","title":{"rendered":"NuGet.org Gets a Facelift"},"content":{"rendered":"<p>It\u2019s been a long time coming, and today we are excited to announce some big changes coming to NuGet.org. With almost 3 million monthly page views, NuGet.org is the gateway for .NET developers to find packages that accelerate their projects. However, as a package management website, so much more can be done. <\/p>\n<p>We decided to give NuGet.org a redesign and use it as a platform to build out new functionality. We\u2019ve already begun to pull in a couple of new features, and have a bunch in the pipeline or planned for the future.<\/p>\n<p>In this post, we\u2019ll discuss 3 things:<\/p>\n<ol>\n<li>The motivations for the redesign and how your feedback guided our decisions<\/li>\n<li>An overview of what we\u2019ve changed and added to the website<\/li>\n<li>A sneak peak of some other features that are currently being worked on <\/li>\n<\/ol>\n<p>We encourage you to try out the <a href=\"https:\/\/preview.nuget.org\">NuGet.org Preview site<\/a> today! <\/p>\n<p><img decoding=\"async\" src=\"https:\/\/devblogs.microsoft.com\/dotnet\/wp-content\/uploads\/sites\/49\/2019\/05\/NuGet-Gallery-Home-New.png\" alt=\"New NuGet.org\" \/><\/p>\n<h2>Feedback and inspiration<\/h2>\n<p>Over the past couple of months, we\u2019ve been talking to you, and hearing your feedback on the current website and gathering ideas on what a modern NuGet.org should look like and do. Some of the common themes we\u2019ve heard in our discussions include:<\/p>\n<ol>\n<li>The website looks old and dated<\/li>\n<li>Current UI makes it hard to find existing package information to judge the legitimacy of a package<\/li>\n<li>Package info on the NuGet website can be lacking and makes it hard to gauge package viability<\/li>\n<\/ol>\n<p>Additionally, after going through accessibility testing, we found a lot of bugs with our current site. Issues ranged from pages impossible to navigate with a keyboard to colors lacking contrast. We knew that we had to do better. <\/p>\n<h2>Overview of changes<\/h2>\n<p>With all the feedback in mind, we set out to create the new, fully-accessible NuGet website that empowers you to easily discover, understand, and use the packages you need.<\/p>\n<h3>Accessibility fixes<\/h3>\n<p>We are committed to making sure that NuGet.org is fully accessible to all users. We addressed many accessibility issues for this preview in accordance with <a href=\"https:\/\/www.section508.gov\/content\/learn\/laws-and-policies\">Section 508 Laws<\/a> and <a href=\"https:\/\/www.w3.org\/TR\/WCAG20\/\">Web Content Accessibility Guidelines (WCAG 2.0 AA)<\/a>. If you find any accessibility issues, please let us know by <a href=\"https:\/\/github.com\/NuGet\/NuGetGallery\">filing an issue on GitHub<\/a>.<\/p>\n<p>Some of the changes we\u2019ve made include:<\/p>\n<ul>\n<li>Updating tab ordering on all pages to ensure proper keyboard navigation <\/li>\n<li>Setting ARIA attributes on elements to make sure screen-reader technologies work on the website<\/li>\n<li>Ensuring all interactive elements have visual feedback for when they are focused by the keyboard<\/li>\n<li>Setting text colors to properly contrast with backgrounds with a minimum ratio of 4.5:1<\/li>\n<\/ul>\n<p><img decoding=\"async\" src=\"https:\/\/devblogs.microsoft.com\/dotnet\/wp-content\/uploads\/sites\/49\/2019\/05\/NuGet-Gallery-Accessibility-Focus.gif\" alt=\"Accessibility Demo\" \/><\/p>\n<h3>More prominent package details<\/h3>\n<p>During our discussions, we heard from you what information is important when determining the viability of a package. The importance of various aspects like freshness, download count, license type, access to a project site, and many more influenced the design of a more streamlined package details page. <\/p>\n<p><img decoding=\"async\" src=\"https:\/\/devblogs.microsoft.com\/dotnet\/wp-content\/uploads\/sites\/49\/2019\/05\/NuGet-Gallery-PackageInfo-Overview.png\" alt=\"Package Details Page\" \/><\/p>\n<p>We created sections to divide package details to make it easier to parse through all the information to get a better understanding of a package. All the vital information is placed at the top of the page to be seen first when navigating to the page. Additionally, the project site now displays as the full URL (if it is under a certain number of characters), publish date is more readable, and license type is made more prominent. <\/p>\n<p>Now that NuGet is supported by a variety of consoles, we wanted to support the many ways users can add packages to their projects. We\u2019ve made it easier to copy the command to install a package, and added a new tab for the command to install using the .NET CLI. <\/p>\n<p><img decoding=\"async\" src=\"https:\/\/devblogs.microsoft.com\/dotnet\/wp-content\/uploads\/sites\/49\/2019\/05\/NuGet-Gallery-PackageInfo-CLI.gif\" alt=\"CLI Support Demo\" \/><\/p>\n<h3>Streamlined account settings<\/h3>\n<p>We\u2019ve made it easier for users to access their account settings, moving away from a centralized account page that combined non-related settings together. Now, API keys and package management controls can be accessed from any page with the account dropdown. It\u2019s much easier for authors to manage their packages.<\/p>\n<p><img decoding=\"async\" src=\"https:\/\/devblogs.microsoft.com\/dotnet\/wp-content\/uploads\/sites\/49\/2019\/05\/NuGet-Gallery-AccountSettings.gif\" alt=\"New Account Settings Menu\" \/><\/p>\n<h3>Easier package management<\/h3>\n<p>For package authors, we\u2019ve made it easier to edit and manage packages. The \u201cManage Packages\u201d page is more descriptive for each package, showing information that mirrors the search results page. <\/p>\n<p><img decoding=\"async\" src=\"https:\/\/devblogs.microsoft.com\/dotnet\/wp-content\/uploads\/sites\/49\/2019\/05\/NuGet-Gallery-ManagePackages.png\" alt=\"Manage Packages\" \/><\/p>\n<p>Additionally, we\u2019ve improved the workflow for editing and listing a specific package version by enabling users to select a version of a package from a dropdown, rather than having to navigate to a specific version\u2019s details page. <\/p>\n<h3>Giving credit to you, the community<\/h3>\n<p>Ever wonder why the <a href=\"https:\/\/www.nuget.org\/policies\/About\">About page<\/a> seemed to have such a small amount of Gallery contributors, when there were definitely more people involved? We did too! So, we made sure everyone who has ever contributed to the <a href=\"https:\/\/github.com\/NuGet\/NuGetGallery\">NuGet Gallery repo on GitHub<\/a> is properly thanked and shown on our About page. <\/p>\n<p><img decoding=\"async\" src=\"https:\/\/devblogs.microsoft.com\/dotnet\/wp-content\/uploads\/sites\/49\/2019\/05\/NuGet-Gallery-About.png\" alt=\"About Page\" \/><\/p>\n<p>We wouldn\u2019t be anything without our community, and we wanted to show how thankful we are for your contributions. <\/p>\n<h3>Updates to our blog and status page<\/h3>\n<p>Since we redesigned the main NuGet website, it only makes sense that we give the <a href=\"http:\/\/blog.nuget.org\">blog<\/a> and <a href=\"https:\/\/status.nuget.org\">status<\/a> pages some love as well. We aligned the pages with the design of the new website to ensure consistency across all of NuGet.org. We cleaned up the blog to make it easier to browse for posts, and made the status page easier to understand and find operational issues. <\/p>\n<h2>What\u2019s in the works?<\/h2>\n<p>Like we said before, we didn\u2019t want to just change pixels on the website. This is not a one-time pass to leave until we need to do another redesign in a couple of years. We\u2019re taking this opportunity to be more iterative on the website and continue to build out and bring new features that improve your experience. As such we have a couple of features that we\u2019ve begun working on that will come to NuGet.org in the coming months. <\/p>\n<h3>Package documentation integration<\/h3>\n<p>We get that packages don\u2019t always offer enough details about what the package is and how to use it. As such we want to give users more information about packages by integrating ReadMe content. <\/p>\n<p><img decoding=\"async\" src=\"https:\/\/devblogs.microsoft.com\/dotnet\/wp-content\/uploads\/sites\/49\/2019\/05\/NuGet-Gallery-Packages-Documentation.png\" alt=\"Documentation on Package Details\" \/><\/p>\n<p>Upon package upload, users will be able to upload or write a ReadMe file to attach to their package. Alternatively, they can link their package to a repository that will pull the ReadMe automatically. This will enable package consumers to get a better sense of a package without having to go to a package\u2019s project site, and empower package authors to create content to aid in the adoption of their packages. <\/p>\n<h3>Status banner<\/h3>\n<p>Being notified of the operational status is important for any service. For NuGet, we want to make it easier for users to see if we are experience issues right from the homepage rather than trying to find the <a href=\"https:\/\/status.nuget.org\">Status page<\/a>.<\/p>\n<p><img decoding=\"async\" src=\"https:\/\/devblogs.microsoft.com\/dotnet\/wp-content\/uploads\/sites\/49\/2019\/05\/NuGet-Gallery-ServiceWarning.png\" alt=\"Status Banner\" \/><\/p>\n<h3>Upcoming backlog<\/h3>\n<p>Additionally, we have a many more features in our backlog that we want to address in future updates to NuGet.org. Some items on our backlog include:<\/p>\n<ul>\n<li>Making search better by improving the relevance of returned results and offering advanced search options (e.g. Target Framework, Author, etc.)<\/li>\n<li>Adding deeper repository integration by showing repo statistics (open pull requests, last commit, star counts, etc.)<\/li>\n<\/ul>\n<h2>Conclusion<\/h2>\n<p>We\u2019re really excited to share this new experience with you, so please give the <a href=\"https:\/\/preview.nuget.org\">NuGet.org Preview site<\/a> a try! <\/p>\n<p>We&#8217;d love to hear any feedback you have on the website, or things you&#8217;d like to see. Fill out our <a href=\"https:\/\/www.research.net\/r\/XP9GS73\">feedback survey<\/a>, or leave a comment below. If you discover any bugs with the preview site, <a href=\"https:\/\/github.com\/NuGet\/NuGetGallery\">file an issue on GitHub<\/a>. <\/p>\n<p>While we work on incorporating your feedback, we will continue to maintain <a href=\"https:\/\/www.nuget.org\">NuGet.org<\/a> in case you find any workflow blockers. We\u2019ll be taking the next couple of weeks to respond to your feedback and will be continuously pushing updates to the preview site. We plan to integrate the new design into NuGet.org in August.<\/p>\n<p>This is just the first step, and we\u2019re excited to continue to bring new features to NuGet.org to make your experience discovering, using, and managing packages better.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>It\u2019s been a long time coming, and today we are excited to announce some big changes coming to NuGet.org. With almost 3 million monthly page views, NuGet.org is the gateway for .NET developers to find packages that accelerate their projects. However, as a package management website, so much more can be done. We decided to [&hellip;]<\/p>\n","protected":false},"author":4326,"featured_media":58792,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[7874,7931],"tags":[],"class_list":["post-56221","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-nuget","category-nuget-org"],"acf":[],"blog_post_summary":"<p>It\u2019s been a long time coming, and today we are excited to announce some big changes coming to NuGet.org. With almost 3 million monthly page views, NuGet.org is the gateway for .NET developers to find packages that accelerate their projects. However, as a package management website, so much more can be done. We decided to [&hellip;]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/posts\/56221","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/users\/4326"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/comments?post=56221"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/posts\/56221\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/media\/58792"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/media?parent=56221"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/categories?post=56221"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/tags?post=56221"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}