Although this is still in the works, DotNetNuke 5.2 beta has a minor improvement in panes preview functionality.

When the core team decided to remove the borders around panes when a user logged in with edit right, the replacement for visual cue is a simple animation shows a pane preview with borders surrounding it. However, the animation was implemented in a way that it goes too fast and users can hardly notices.

Dang and I are doing a presentation next week at Open Force entitled “UX in DotNetNuke: Designing Your Applications the Right Way.” One of the challenges we face as presenters is making sure we attract the right people and set their expectations appropriately as to what the actual content of the presentation will be. While our title and description are accurate, it may be helpful to go into more detail.

Many web visitors know what a link does on a web page. For web developers and designers, links can perform certain actions in different context; however, it still is going to look like a link to end-users. Pre-defining the CSS selectors (doing the designer's job) on certain links in DotNetNuke framework or any CMS for that matter is not necessary. Sometimes it can cause some additional work for others.

In DotNetNuke, there are CSS selectors called SkinObject and CommandButton. These two selectors are essential parts of DotNetNuke links to define the look and feel. It is kinda self-expalined that if you want to style the links for any skin objects, you'd find the SkinObject selector and override it in your skin.css file. The same technique goes with CommandButton, but you need to identify which link in the framework that uses SkinObject and which one that uses CommandButton.

Rating is something that I have never seen anybody in DotNetNuke community has done it right. It might sounds pretty extreme, but if you have seen something that provide values as what I am going to discuss in this blog, please feel free to direct me there.

I sometimes run into modules (whether if it is free or commercial) that provide rating ability on articles or products in a way that is… somewhat useless to visitors. Things like five-star-rating is one of most common mistake I’ve seen around. Unless you show the amount of people rated on the article and give them an average rating, it does not mean much if you just show visitors that this article has been rated 4 out of 5. This isn’t rocket science that you have to be a UX expert to figure out how to provide values; I believe this is just common sense to most people.