Last post May 27, 2008 08:28 PM by email@example.com
May 21, 2008 08:17 AM|OwainGDWilliams|LINK
I have been asked to look in to building a new intranet site for the company I work for. We are looking at all options i.e. building our own from scratch or buying a pre-built solution.
Does anyone have any experience in doing anything similiar.
We like the idea of building our own solution so it is exactly the way we want it from the start rather than modding a pre-built option and maybe not getting everything we want.
However, buying a pre-built system will free up our man hours to do other tasks but will it cause us more problems further down the line?
Your thoughts and suggestions welcome.
If anyone can recommend some pre-built systems for us to look in to that would be great.
May 21, 2008 04:43 PM|stiletto|LINK
CMSs: SharePoint, BeerHouse, RainbowPortal, DotNetNuke
The biggest challenge is in knowing what you'll want (or what the business users you support will want) in the future.
May 21, 2008 06:04 PM|bjsusol|LINK
I actually just did this.
I had no .NET experience at all. I was attempting to maintain the existing sharepoint site which was pretty bad and we were in the process of deciding how to replace it.
A new applications manager came in and tasked me with the job. He built a very basic frame that allowed us to have an admin section to only allow certain people access to the tools and then told me to start building.
It was a great learning experience, but it did take ALOT longer than it could have if we built something using a prebuilt solution. However, now we know EXACTLY what we have, and also have complete control over it.
The downside, is I am going thru it a second time right now, to "improve" the pages I initially built with my updated skillset. Then again - its not really a downside as I am still learning new things and putting it to use.
May 27, 2008 02:33 PM|OwainGDWilliams|LINK
So would you say it was better building your own because you have the skills and the knowledge that everything is there for a reason, rather than trying to customise a pre-built soluction?
May 27, 2008 02:46 PM|bjsusol|LINK
I think so.. all the reasons you mentioned. I learned ALOT doing it... I found myself going back and tweaking stuff I had done when I first began.
There is no bloat - everything is there for a reason.
May 27, 2008 02:59 PM|OwainGDWilliams|LINK
Thanks, just needing to make a good argument for my boss so we can build our own :) Both myself and colleage want to build our own but its always down to the money Vs manhours required to do such a thing.
May 27, 2008 08:28 PMfirstname.lastname@example.org|LINK
Reinventing the wheel is not cost effective. Start by looking at some of the base systems you can build on. DotNetNuke, Community Server, Umbraco, SiteFinity and ADXStudio (and many more I'm sure) are all extensible for what you need. DotNetNuke is probably
the most easy to custom develop, having a huge base of developers already creating modules as well as a lot of development information available. DNN and Umbraco are open source, and with most of the others you get source when you purchase them.