We're just beginning the process to implement DNN as our content management tool that will compliment a site-wide redesign. 

As I question my sanity for agreeing to this, I'm wondering if I could get some advice on the big questions I have so far:

1.) This is a site for a college - is it best practice to have one DNN instance for the whole site, or would it be better to create child portals for the different areas of the site (ie: one for admission information, one for academic information...).  I wasn't sure for re-purposing content if having child portals made things harder to work with.

2.) Our current website has several dynamic applications that I've written over the years.  While I know I can replace some of them with DNN modules (like our news feeds and events listings), what is the best way to handle the rest?   Should I be focusing on re-developing them as DNN modules?

I'm sure I'll have a million more questions, but that's a fine start for now if I could get some advice!

Thanks!

Michelle

Well since you offered!

I started looking at the XML module yesterday - would that be a way to translate my existing database content into something useful in DNN?