And in truth, get off of Dot Net Nuke ASAP and build yourselves a custom platform. Sure it will cost a little bit more initially, and take a little longer... but please. And hire a good graphic designer while you're at it. The site is very boring :/ (seriously, no offense)
To everyone that jumped on the bandwaggon, classy =D
Telling them to get a custom solution is not good advice. For a small business getting a custom solution is expensive to build and expensive to maintain. Better to use open source software that is freely available and developed by thousands of people worldwide with lots of custom modules and tons of people able to work on the platform.
Been there done that on the custom solutions and while they can certainly rock they are no good if the developer goes somewhere else.
Custom platforms require a solid staff to keep them maintained. IN fact any platform requires a solid staff but a custom one is "foreign" to almost everyone but the primary developer. Using off-the-shelf platforms gives the user a broader base of people who can develop for it and trouble shoot it.
There is nothing wrong with DNN. How the site looks has nothing at all to do with the platform. That can all be changed easily.
As a CMS it's fine.
And yes I have been there on the custom solution side. I built a CMS that was WAY ahead of it's time custom for my case business. In fact I might look up the developer and see about doing something similar in the future. But I spent $40,000 on it and when I sold the business the new owners scrapped it because they didn't want to retain my developer. See the problem?
I currently run three other websites off the same backend database and each one is a wysiwyg user interface CMS that can be accessed from anywhere and changed by anyone in the company on the fly. Each site is visually different from the others due to the custom skins we built.
Again though the problem is that since me and the developers have parted ways I am stuck with having to wade through their code to make any significant changes.
So, Holly and Mark, not that you need this advice, stick with DNN - it's fine and if you find someone competent you will do well with it. My advice would be to budget for some module creation to be farmed out to freelancers so its' not ALL on your permanent hire. Let him manage the development spread out over several developers.
Oh and you're in good company with DNN users - http://www.dotnetnuke.com/Intro/Showcase-Sites.aspx There are thousands of apps and modules for you to use which are easily customizable.
Last edited: