Blog

Think back to the last technical implementation that you were involved with. Were there any surprises after the project finally rolled it out? Right before rolling the project live, did a gut feeling tell you something may be amiss?

If the memory of a previous implementation is still clear, I'm probably preaching to the choir when I say that user testing is highly underrated. And that's what this article is all about: a few guided user testing suggestions that you probably already know... and most of us have to re-learn from time to time.

So your web page has a background image that fades to black (or some other solid color). You want to make sure that when the page expands vertically beyond the height of the background image, the black background will also expand vertically without limit.

No one will notice that the background image is shorter than the page because it fades oh-so-smoothly into that solid color. You're a genius web designer!

The best way to make sure that the background color shows up behind the image is to assign the background color to the body tag using CSS. Or you could assign the color to the html tag. You're done. End of article.

Here's the catch. Sometimes you have elements, such as iFrames on your page. iFrames have a nasty habit of inheriting color from html tag. Or, if you have a color set for the body tag, likewise, the body tag within the iFrame will also get that same color. So, here's a solution... 

If you have ever developed for the web, you may have discovered that not all browsers interpret HTML or CSS styles the same way. Frustrating, we know. And we have some good news and bad news for you on the HTML email template front...

Work on the Sport Events DNN module officially began March 8, 2011. Three-and-a-half glorious months later, it is now a fully functioning module... A real thing of beauty. But how did I do it?

For those who have never heard of Ajax, let me bring you up to speed.

Ajax stands for Asynchronous Javascript and XML. But that’s just a fancy way of saying: Ajax can make things move or update on a web page reloading entire page. (doing that flickering thing that happens when you press the roundy arrow button on your browser or go to a new page).

Note: Click here to check out various Ajax controls in action.

So how can you get DotNetNuke to play nicely with Ajax?

‘Can you reword the second paragraph at…’, ‘can you correct the spelling at…’ or ‘can you add this picture to…’.

You don’t want to have to make a million tedious changes all by yourself so maybe the client can make most of these changes. Besides, who knows what’s best better than the client. Right?