smithsson68@gmail.com
Oct 5, 2011
  5353
(2 votes)

New design and functionality on nuget.episerver.com

The first round of upgrades to nuget.episerver.com took place last night. The site now has a cleaner design as well as package searching and sorting.

image

I found that I had to clear my browser cache to get the new css to take affect so if it looks a bit weird then try this first before reporting it as a bug.

I would like to thank Cecilia and Andreas from Nansen for their help with the design.

Feedback as always is welcome.

Oct 05, 2011

Comments

Oct 5, 2011 10:39 AM

Looks really nice, great work! Will you add rating/comment possibility too?

smithsson68@gmail.com
smithsson68@gmail.com Oct 5, 2011 11:09 AM

@Michel Yep, that's the plan but not sure about the timescale yet.

Magnus Rahl
Magnus Rahl Oct 6, 2011 02:06 PM

You probably know it, but: Easiest way to avoid cached CSS:es etc is to add a querystring to the URL where they're referenced in the page and vary the querystring each time you update. Doing this manually is of course crude but it works. Better to generate the querystring from the filedate of the CSS (and use a file system watcher) or to create it from the assembly version if you only change the CSS when you release a new version.

Please login to comment.
Latest blogs
Announcing new library: SettingsManager

When you run .net app, there have been a few ways to store settings. Those can be set via appSettings.json, or via Azure Portal AppService...

Quan Mai | Apr 30, 2026

From Prompting to Production: Optimizely Opal University Cohort and the Future of Agentic MarTech

Most organizations today are still playing with AI. They experiment with prompts, test ideas in isolated chats, and occasionally automate a task or...

Augusto Davalos | Apr 28, 2026

Six Compelling Reasons for Upgrading to CMS 13

Most software updates ask you to keep up. Optimizely CMS 13 asks something different — it asks whether your digital strategy is built for a world...

Muhammad Talha | Apr 28, 2026

Optimizely CMS 13 breaking changes: GetContentTypePropertyDisplayName

When upgrading from CMS 12 to 13, resolving property display names may not work as before. Here’s what changed.

Tomas Hensrud Gulla | Apr 27, 2026 |