Hi all DNN pros and Mitch

I'd like to ask a few questions about the blog module and how www.mitchelsellers.com has installed it. Mitch, is it the core standard blog module you have installed in your portal www.mitchelsellers.com? The way you are having your url:

http://www.mitchelsellers.com/blogs/articletype/articleview/articleid/220/dotnetnuke-484--installupgrade-instructions.aspx

with changing the classic /default.aspx to /dotnetnuke-484--installupgrade-instructions.aspx how have you achived this? Is it standard DotNetNuke blog or is it something you have customized?

/Johan     www.chefsrekrytering.biz

Ok, I see, can you Mitchel describe briefly why you selected that module in favoure instead of the DotNetNuke Blog module there is here? I am studying severald modules and the reason you choose that one interest ma very much. Had it to to with performance or stability or something or just better architechture?

/Johan  www.vattenskoter.info

I realize I'm not Mitch, but I know that people end up using News Articles and other publishing platf0rms out there like DNNArticle and Engage Publish because they're looking for a list of features that don't existin the blog module (yet).  I had one client that looked everywhere and finally settled on Engage Publish because of the image they wanted to convey through their blog.  Some features supported by these other products that don't exist in the blog module (yet) are:

• Category management
• Tagging
• Multi-Author support
• Approval Workflow
• SEO Enhancements
• Multi-Page support

I haven't seen customers making these decisions based on perf0rmance or stability or architecture.  The choices I've seen people making are based more on the balance between cost and features. 

HTH,

Don