---
title: Widget Context UI Update 2011, Version 2
date: 2011-08-30T17:31:09+00:00
modified: 2020-05-13T13:58:52+00:00
image:: https://kaspars.net/wp-content/uploads/2011/08/widget-context-ui-v2.png
permalink: https://kaspars.net/blog/widget-context-ui-2011-v-2
post_type: post
author:
  name: Kaspars
  avatar: https://reverse.kaspars.net/gravatar/avatar/92bfcd3a8c3a21a033a6484d32c25a40b113ec6891f674336081513d5c98ef76?s=96&d=mm&r=g
category:
  - Design
  - WordPress
post_tag:
  - Plugin
  - User Experience
  - Widget Context
---

# Widget Context UI Update 2011, Version 2

[![Widget Context UI Update, Version 2](https://kaspars.net/wp-content/uploads/2011/08/widget-context-ui-v2.png?strip=all&quality=90&resize=506,333 "Widget Context UI Update, Version 2")](http://lab.konstruktors.com/widget-context-ui-2011/?v2)

Here is the second iteration of the [UX update](https://kaspars.net/blog/feedback-widget-context-ui-2011-v1) for the Widget Context plugin. Please [check out the live demo](http://lab.konstruktors.com/widget-context-ui-2011/?v2) and let me know what you think!

### The Concept

The number of locations where you might want to show or hide a widget can vary significantly — having “Related Posts” widget on all blog entries except on posts that are tagged “twitter” (many); or showing the “About Me” widget only on the front page of a blog (few). However, the combinations are endless.

Therefore, I realized that the most important feature should be the **ability to find those groups of locations very fast**. So there will be only two ways to sort through the content: (1) search, or (2) choose one of the core locations such as homepage, blog index, **all** pages/(custom)posts or their indices (archives).

Once you have found and selected the sections, it is only a matter of ordering (or chaining) them according to their “power” — low power locations sink to the bottom and are overwritten by the ones floating above them. This is done via drag-and-drop.

The question is — can you think of a combination of locations that can’t be covered using this approach?