Products

Solutions

Resources

Partners

Community

About

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeDevelopment and...Development and...Getting StartedGetting StartedDNN as an 'Engine' for website designer?DNN as an 'Engine' for website designer?
Previous
 
Next
New Post
6/29/2014 7:34 AM
 

Hi,

I'm 'shopping around' for a cms that I can use to build multiple websites. My aim is to use the CMS as an engine to build websites for customers and then hand them over (with hosting) and then move onto the next project.

I currently use Visual Studio (VB.NET) to build websites, but I'm looking for something that has a more pluggable dynamic in terms of add-ons.

Would I be able to develop sites for others via DNN? Is it possible to have many projects going on under one DNN username/membership, or would it be a case of creating a site within my account and then copying that site to another hosting account before deleting the info from my DNN account and starting the next project? Or setting up DNN on the clients hosting account and building the site 'in-situ'?

Also, I've already installed 'dotnetnuke' on my hosting, which cost me nothing, yet there's the Evoq thing going on which appears to cost money, I'm confused as to whether the thing I've got in my (Plesk) hosting account will even work.

Finally, I read that 'dotnetnuke' will now only work with MSSQL 2009, whereas, even though my hosting account only offers 2008, it installed fine and I can log in.

Anyway, before I get stuck in and start creating I wanted to know if I was barking up the wrong tree - Joomla instead?!?

 

 
New Post
6/30/2014 7:19 AM
 
If your clients are different, you would probably keep them separate and create a new DNN installation for each. At least that's what I would do.

Typically I have my clients move to a new hosting account because their current one doesn't support DNN or some of their needs. They'll create a new hosting account, send me the details from the "welcome" email that's typically sent from the host and I'll start building the site there. I'll still run a DEV copy locally for module development and testing but I spend a lot of time working on the actual site so I don't duplicate effort. Once the site is done and the client gives final approval, we update their name servers to point to the new host and the domain names resolves to the new web site/host.

Unless you paid for Evoq, you won't have it and I wouldn't worry about it.

There is no 2009 version of SQL Server, so I assume it was a typo or something else. As long as you have 2008 you will be fine unless the requirements change in the future.

As far as Joomla or any other CMS, obviously most people here will recommend DNN because we use and love it. I'll tell you why I love it - it's the easiest one to use from a user stand point. There is no back-end or admin section per-se. People log in and make edits on the page in question. I also like the fact that pages are called pages, not articles or some other cryptic word. Non-tech users may have issues understanding CMS basics but not with DNN. IMO it's the easiest to use and I find module development pretty decent too.

Hope this helps. If not, post more questions and we'll try to help.

Mark
 
New Post
6/30/2014 4:18 PM
 

Based on the details you've provided so far, DNN would be a good fit.  DNN Platform is an open source platform that is a great choice for people who are just getting started and want to keep costs to a minimum.  If you have a customer project where professional support and advanced features are needed then you can purchase an EVOQ license for that customer.  The good thing is that the money from these license purchases are used to help fund further development of DNN.

As a .Net based CMS, it is easy for you to use any .Net language to write extensions to suit your customers specific needs.  Of course, you can probably just use some of the thousands of modules and skins that are available in the store to get you up and running pretty fast.  Whether you choose to go the fully customized route or use off the shelf extensions, DNN makes it all pretty easy.

DNN supports multiple portals out of the box and I have known more than one system integrator who used this feature to provide an inexpensive hosting option for their customers who were on a tight budget.  The downside to this approach is that if any of your customers outgrows your hosting plan it can be a bit of a challenge to split their site out from the others in the installation (it is doable, but it is not a recommended task for someone just getting started with DNN).  It is definitely something you need to think about as you are planning how you want to host your customers.  

If you can afford it in the budget of your projects, I would setup each customer with their own hosting account.  This ensures that you can scale each customer as needed without worrying about what other customer might be located in that installation.  It also provides you a lot more flexibility in terms of installing just the modules and skins needed to support a single customer.  Finally, it ensures that hosting companies are getting fairly compensated for their services.  If you have multiple accounts with a hosting company, they are much more likely to give you a good deal on rates and support than if you try and go the cheap route.  Hosting companies operate on a small profit margin and don't prefer to support multiple sites hosted off a single low cost account.  My experience is that you will get much better support from them if they know you have multiple accounts and continue to grow their business as well as your own.  You can't go wrong by looking for the WIN/WIN.


Joe Brinkman
DNN Corp.
 
New Post
7/1/2014 2:08 PM
 
Hi,

Thanks for two very good replies, I'm settled on DNN (I tried the default site after I signed in and was impressed by the ease of use, though I am confused about how to set the destation email on the contact form, where the 301 redirects would be hosted, and how one would replace the current files with the new ones where a DNN site was 'taking over' from a current site on the same hosting account. Anyway - impressed!

I've been wondering about where to actually do the developing. I've read that one can develop on WebMatrix, then publish to an account, but I don 't want to get into it to then find that it's a pain to actually do so
 
New Post
7/1/2014 2:18 PM
 
Hi,

Thanks for two very informative (and positive) replies. I've decided that I like what I see with DNN, I had a look at the default site when I logged in and I was very impressed with the dynamism of the thing. Though I was a bit confused as to how to set the destination email on the contact form, how one would replace the files of a current site with those of a DNN site on the same hosting account, and where one would keep the 301s once the old pages had been replaced. Anyway - Impressed!

I'm now deciding where I should do my developing: on the internet via the site, or locally with WebMatrix. I think the WM approach would be far more multiple site-development friendly, as it would be a case of developing the site locally then simply publishing it to the destination hosting account. Though I'm a bit nervous as I don't want to find that I made the wrong decision. So, are there any issues with developing locally on WebMatrix then publishing, would you advise to just stay online?

Thanks again for your help.
 
Previous
 
Next
HomeHomeDevelopment and...Development and...Getting StartedGetting StartedDNN as an 'Engine' for website designer?DNN as an 'Engine' for website designer?


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out