Using A Website Template For Your Business

I have a need for 2 websites:

  • One of my business ideas has as its foundation an informational website. In other words, the information on the website is how I would make money, either through ads or subscriptions.
  • The other website would be my company website.

I am not a web designer, by any means. My artistic ability is near nil. So starting a website from scratch seems counterproductive.

However, I am technically savvy and, maybe to my detriment sometimes, like to try technical projects myself before going off and hiring someone to do it for me.

I am considering choosing and using website templates from Open Source Web Design for both of my website ventures.

My reasoning is that there are many free, artistically viable templates that I can start with such that some of that legwork has been started for me. I can then take the source code and modify it to match my needs. Also, did I say they are free!

I have heard mixed thoughts around using canned website templates for business ventures.

Some of those against citing that you don't want your website to look like any possible shady (e.g. porn) websites. Others against the idea say if you don't know what you are doing enough that you need to use a template, then you should just hire a professional to do the work correctly.

However, people for the idea say if you use modifiable templates (e.g. open source), you can customize the site enough to make it look original and provide a unique look and feel value proposition for your business.

I am hoping to hear from people for and against the "use a template for your website" idea. Specific case examples would be great.

Let the comments roll.....

Microsoft Shares Source Code to the .NET Framework

I saw this on Scott Guthrie's blog yesterday (I must have had a brain freeze for leaving him off my blogroll): Releasing the Source Code for the .NET Framework Libraries

This is good to see. And this is great news for software developers. For this post, let's leave out the obvious technical reasons as to why this is a good idea for .NET software developers. Releasing the .NET Framework source in and of itself is to me, maybe surprisingly, really not the biggest news. We have been able to "view" the source code for a while now (thanks Lutz!) -- although, being able to "step" into the .NET Framework code in the debugger is huge!

Let's instead focus on the business perception reasons. Microsoft has been slammed by many a person for being the 800 pound gorilla, an opportunistic monopoly, the evil empire, the company that pretends to care about software developers but doesn't, <insert your Microsoft slam here>. Many of these come from the open source community. While Microsoft isn't releasing the source to Windows or Office to the world, the .NET Framework is hardly a flash in the pan. I mean, they are integrating the .NET Framework and all of its siblings and underpinnings into many cash cows, including Windows. With this release, Microsoft is taking a huge step to fully understanding the importance of the software development community. I see this as just one of many steps that Microsoft is going to take in the future to make it real easy to have software developers target .NET, Windows and/or Microsoft technologies in their development --- one semi-bold prognostication I have (and others do too) is the *full* .NET Framework on the Mac, not just via Silverlight.

This alone won't change many of the "gorilla" perceptions that people think about Microsoft, but it's all about baby steps, and I think the baby is beginning to at least toddle around now.

Oh, and to those that think the licensing is's nothing that isn't expected. All it is really saying in a nutshell is that you can view the source code but can't modify it. That is perfectly reasonable. Microsoft is not a purely open source company, and won't be, so this licensing allows exactly what the intention of the announcement is -- for you to view the source code during your development process.