When you're using terms and privacy skinobject for your web site, it will pull in the web administrator e-mail address to display as part of a way for visitors to communicate with a site's webmaster.

If you are like me, just wanted to add something real quick and move on, you'll more likely to come back in the future when the project is done and find a way to correct it.

Well, remember during the process of installing DotNetNuke or creating a new portal for your project, you are asked to provide administrator information including name, username, e-mail address and so on? When visitors click on the terms or privacy link, they will be taken to the control that display the content pulls from a resource file somewhere on your site with the e-mail address you provided during the portal creation. If this e-mail is incorrect and you'd like to modify it, you will need to log in as an administrator and edit your profile to correct the e-mail address. I realize that a site can have multiple administrators, but this administrator have to be the one who created the portal for the change to take effect.

Recently I had an opportunity to play with UnloadCSS skinobject from Timo Breumelhof. What a nifty little tool to use for your front-end performance optimization.

I wrote an article a while back about cleaning up your default.css from the framework (or just get rid of it). There are many unnecessary CSS files get loaded within the framework (not to mention some not-so-good practices in CSS coding techniques within these files) that a web designer wants to take control of. Default.css is one of those files that need improvement.

DotNetNuke® has gained some great momentum over the past few years. But is it because I’ve been working with it for so long and being bias? Well, I don’t know but truth to be told, not many of my friends (who are also working in similar industry) or people that I’ve talked to know about it. Whether you’ve heard about it or not, Day of DotNetNuke® is a great opportunity to explore the project and meet some of the greatest minds in the community.

Day of DotNetNuke® is a one-day event that is organized by Will Strohl, creator of the Orlando DotNetNuke® User Group. He puts some great effort out to organize this event with the hope to help people learn more about the platform without spending a fortune. So far I have seen many of the respective community members hinted on coming and speaking at the event.

Designing with grid has been around for decades and applied through various traditional design mediums. But in recent years, the trend to use this technique on the web has become quite popular since many influential web designers took the initiative to introduce it to the world. Among those is Khoi Vinh, a Creative Director for The New Yorks Times Online, and Mark Boulton, a well-know author for publishing his series of his approach in grid design.

Many people have discussed the benefits of using grids so in this article, I won’t be talking much about why you should use it. There will be a different post to discuss the reasons to follow grid designs and when to use it.

One of the reasons we all (hopefully, all of us who design web sites) do cross-browser testing is to maintain the integrity of the design. This means that we make sure the site is running and displaying properly across browsers. However, some people may take it to an extreme level by pointing out the fact that their web sites do not look the same in all browsers.

As many of you may know, I work closely with the development team at Engage on various projects. One of the most common mistakes I’ve seen is that developers use <br /> (BR) to create padding between elements. Sometimes, I see big chuck of BR element being used across just to create a larger padding between their elements. This isn’t new to many developers; I often see it in many commercial modules we bought as well.

If you find yourself doing this religiously and not know what it means (some developers know what the BR element does but choose to do so), it is your time to change this bad habit by using the proper HTML tag: the <p> (P) tag.