Re: .net options these days?

Have you looked at the open source Community Server? I haven't used it 
before (as prefer Python over .Net) but it seems pretty featureful.

Nate

Austin, Darrel wrote:
> James' article post (which is nice, btw!) reminded me that this list is
> still alive.
> 
> Which is nice timing, is, once again, I'm in the middle of CMS research
> hell. ;o)
> 
> We've spent 6 months trying to roll out a CMS solution via SharePoint
> Server 2007. It failed. More for political reasons than technical, but
> either way, it's been scrapped and I'm not looking for options. They
> primary 'technical' issues were a) very hard to skin outside of
> SharePoint's own preferred templates b) the CMS features are built ON
> TOP of sharepoint, so the learning curve is large. c) admin interfaces
> to update content are complex and overly tedious. d) we really didn't
> need a lot of the features it forces upon you...page templates,
> workflow, approvals, etc.
> 
> The catch is that we really need a MS-centric solution to make it easy
> to sell to the server team. .net preferred.
> 
> 5 years ago when we went through this process we found the options to be
> slim. Products were either way overpriced or just completely inadequate
> from a tech-management side (crappy templating systems, bad web
> standards support, overly complex permissioning systems). So, we built
> our own.
> 
> 5 years later, one of the options on the table is for us to re-write our
> internal application and release a 'v2.0' of it.
> 
> I'm all for that, as I really enjoy working on that type of work, but I
> simply can't just accept that as the solution without first taking a
> look as to what's out there.
> 
> So, any suggestions? Some details:
> 
>  - the CMS solution will need to run our Intranet 'portal' and our
> public web presense.
>  - we're still going to use SharePoint for internal collaboration. As
> such, I have a hunch, over time, that the 'intranet' portal will become
> more of a directory pointing to a lot of SharePoint collaboration sites.
>  - for now, though, the intranet is going to need to be a hierarchical
> grouping of pages that will have text content, and links to documents.
> We need to delegate permissions by regional office, then by department
> within each office.
> 
> What I've begun to look at:
> 
>  - DotNetNuke. Pros: Full 'CMS'. Cons: looks a lot like sharepoint.
> Might have more features that we really need.
>  - Graffiti CMS. Pros: VEERY nice interface. Cons: mainly a blogging
> engine, and doesn't quite seem to be built for the 'enterprise'.
>  - FlexWiki: Pros: Wikis are quick and dirty. Cons: well, it's just a
> wiki. Probably a hard sell internally.
> 
> Any other OS and/or low-cost .net-centric CMS systems on the market
> these days that I should take a look at? On my list of things to still
> look at are Community Server (same company as Graffiti CMS), and Ubarco
> (looks great, but might not yet be an established OS option).
> 
> -Darrel
> 
> 
> 
> _______________________________________________
> cms mailing list
> [email protected]
> Subscription controls:
> http://lists.cms-forum.org/mailman/listinfo/cms
> Netiquette FAQ and related CMS lists - [cms-forum], [cms-pr], [contentmanagers], [cmpros]
> http://www.cmsreview.com/NetiquetteFAQ.html
> http://www.cms-lists.org
>