Posted Jun 21, 2011 by Human Element
Hold on to your pocket protectors! Human Element’s own Gregg Milligan II has completed his first DotNetNuke Module, Sport Events. It is now in Beta Testing… word.
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 the real question is: How did I do it? First things first…
If you’ve never heard of DotNetNuke or think a module is some sort of growth, let me fill you in. DotNetNuke is a content management system for web sites. It helps people dynamically control and generate site content.
DotNetNuke is also a development framework. Developers [also known as “Nerds”] code “Modules” that can be plugged-into DotNetNuke, providing a slice of sweet, sweet functionality for the site and a unique interface in the overall management system.
The major place to find and download third party modules is
. There really are some great DNN modules out there! However, the landscape of DNN modules is mostly unregulated. Think of it like the Wild, Wild West of the Developer World. The quality of a module mostly depends on the work of the third-party developer and not all developers regulate their work the same way or try to fulfill the same standards, even though DotNetNuke modules are pretty big business.
Here’s the quick run-down of what we were going for:
Sport Events has three main Admin Categories.
If you don’t create your own template, don’t worry, a default template is used. Yeah, it’s the little things like that, which make a module pretty sweet, but that’s just the tip of the “NICEburg.”
…no one knows this more than the end user.
A lot of my work involves getting the most out of them to meet client needs. That’s why I really appreciate when a module is smartly designed and behaves predictably. I kept this in mind when creating Sport Events out of empathy, perhaps, but also because I would also have to be one of the primary users.
Sport Events has many of these “little things” designed to make lives easier, such as including modify timestamps (in case you need to ostracize someone for making a bummer modification), but I won’t cover all of the module’s little cool perks… at least not in this blog post.
Here’s another example of a little thing that can seem like a big thing to an end user.
: You want to link some text in your template to the event box score. You insert the following code into your template to do this:
Great! Now the word, “Box Score” is a link to your box score. Makes sense right? Well… what if you don’t have a box score link defined for your event? Now the word “Box Score” doesn’t have a URL link. Uh oh.
: Well, Sport Events is designed to remove link HTML and inner text that doesn’t have a URL. Great! The problem is solved!
You want to link your opponent name to the article about the event.
If no article URL is defined for the event, your whole opponent name, along with the link is removed from the output! Uh oh!
What if I include Cross Country into my event list? Cross Country doesn’t have a score, only a rank. The rank would be assigned as the “Home Result.” Therefore, cross country ranks would always be followed by the word “to.” Uh oh!
Everything between the span tags will only be included if the value of the Name attribute is not empty. Therefore, if there is no Opponent Result, the word, “to” will not be included.
Have you died and gone to nerd heaven or what?
Currently, Sport Events is in the Beta phase. Small improvements or enhancements may be made in response to user feedback from Siena Heights. Once the creative styling is applied to the module, I will put together some screenshots as an addition to this post.
Once the module is proven to be stable, I will look into entering it into the public DotNetNuke module community as a free demo download. Depending on demand, I may make Sport Events available to public community through the normal channels, such as Snowcovered.com.