Time needed to select a CMS

[James Robertson-10]

Hi all,

I've just published a one-page article outlining the time minimum
time needed to select a new CMS:

http://www.steptwo.com.au/papers/cmb_selectiontime/index.html

This is obviously not aimed at the "CM pros" on the list, but
may be useful in helping to set client expectations...

As ever, feedback is gratefully received.

Cheers,
James

--
-------------------------
James Robertson, Managing Director
Step Two Designs

Email: jamesr@...
Web: www.steptwo.com.au
Phone: [phone]


_______________________________________________
cms mailing list
cms@...
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

[Austin, Darrel]

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
cms@...
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

[Ed Kapuscinski-2]

Darrel
Have you heard about Umbraco? It's .NET and OS, a strange combo, but  
it might be what you want.
http://umbraco.org/

I've never used it, but I'm thinking about checking it out shortly.  
One of my coworkers really likes it though. It might be worth a look.

Ed


On Feb 11, 2008, at 9:15 AM, 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
> cms@...
> 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

_______________________________________________
cms mailing list
cms@...
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

[Austin, Darrel]

> Have you heard about Umbraco? It's .NET and OS, a strange combo, but
> it might be what you want.
> http://umbraco.org/

Indeed! Aside from DotNetNuke, I'm not aware of many OS/.net combos in
CMS land (which is really no surprise, of course).

I am going to be trying out Umbraco myself. They seem to be trying to
emphasize web standards and intuitive interfaces, so we'll see.

I think the only hang-up with that option will be that it appears fairly
new, and support options slim at the moment.

-Darrel


_______________________________________________
cms mailing list
cms@...
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

[Austin, Darrel]

It appears the  list defaults to 'reply to sender'. I've gotten a lot of
off-list suggestions for both Ektron and Umbraco. So, I'd like to thank
everyone that responded with those suggestions. Both will definitely be
on my punch list for looking into. Thanks!

-Darrel

_______________________________________________
cms mailing list
cms@...
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

[srinivasan Nachinarkinar]

you can look at ConQuest CMS
(http://www.conquestcms.com)

It is written in ASP.NET and the base cost of the
product is just USD 4500/-  Customizations will cost
equally cheap, as the developers are sitting in India.




--- "Austin, Darrel"
<Darrel.Austin@...> 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
> cms@...
> 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
>

      ____________________________________________________________________________________
Be a better friend, newshound, and
know-it-all with Yahoo! Mobile.  Try it now.  http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ 

_______________________________________________
cms mailing list
cms@...
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

[Søren Laursen]

Hi Darrel

I work for Dynamicweb-cms.com. With the risk of being accused of spamming I just want to present you with a viable proprietary solution. Darrel, Feel free to flame me later on the list if you don't think this was relevant to your scenario.

Essentially I think our product is what you are looking for.

1) It is based on .Net

2) It is very straight forward in terms of how you manage content. Yes compared to larger systems it has flexibility limits but it sounds like you will not need that type of flexibility anyway. * referring to the problems you have had with Sharepoint and other solutions.

3) It is well established with 3000 customers on maintenance contracts.

4) As an intranet it will not handle collaboration well but excels in publishing content quickly and yet has reasonable user access management features.

5) You can build custom modules and use .Net controls.

6) Can be setup on Microsoft IIS and run either SQL or Access. It can be installed in less than 30 minutes by a junior system administrator.

7) Comes with a relatively low price tag since it originates from Denmark which is country of primarily small and medium sized companies not willing to pay the kind of price companies like Vignette, Reddot, Microsoft etc. are accustomed to.


Let me know if it could of interest and we will give you a free demo you can play around with.


Regards


Soeren Laursen



-----Original Message-----
From: cms-bounces@... [mailto:cms-bounces@...] On Behalf Of Ed Kapuscinski
Sent: 11. februar 2008 15:50
To: Austin, Darrel
Cc: cms@...
Subject: Re: [CMS] .net options these days?

Darrel
Have you heard about Umbraco? It's .NET and OS, a strange combo, but  
it might be what you want.
http://umbraco.org/

I've never used it, but I'm thinking about checking it out shortly.  
One of my coworkers really likes it though. It might be worth a look.

Ed


On Feb 11, 2008, at 9:15 AM, 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
> cms@...
> 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

_______________________________________________
cms mailing list
cms@...
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


_______________________________________________
cms mailing list
cms@...
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

[Nate Aune]

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
> cms@...
> 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
>

_______________________________________________
cms mailing list
cms@...
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

[John M. Morse]

Darrel

Not sure what your budget is nor the size of project your are completing
but I would suggest you need (must?) to look at

Sitecore
Ektron
Immediacy
Umbraco

Have varying degrees of exposure to all of these solutions, Sitecore
being our current tool of choice mainly because of its more of a content
delivery platform rather that a CMS and you should look into its
Sharepoint connector which will help with your legacy systems,l it hsas
a fully open API, which our developers like ;)

Ektron is a very feature rich CMS with excellent tools and also has a
Sharepoint connector, good support, an active developer community, great
web 2.0 social toolset and a published API

Immediacy is a smaller still WCMS also with Sharepoint connector

Umbraco is, well Umbraco, secretly I have a soft spot for this CMS and
are looking for an opportunity to use it in anger


HTH

John Morse
Information Architect
Professional Services Group
UPA, Prince 2, ISEB IT Architect, IAI

Eduserv Internet
Managed hosting & development
john.morse@...
tel: [phone]
fax: [phone]

http://www.eduserv.org.uk/internet/ 
Eduserv Internet is a service of Eduserv Technologies Ltd





-----Original Message-----
From: cms-bounces@...
[mailto:cms-bounces@...] On Behalf Of Austin, Darrel
Sent: 11 February 2008 14:15
To: cms@...
Subject: [CMS] .net options these days?

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
cms@...
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



Unless otherwise agreed expressly in writing by a senior manager of
Eduserv, this communication is to be treated as confidential and the
information in it may not be used or disclosed except for the purpose
for which it has been sent.
If you have reason to believe that you are not the intended recipient
of this communication, please contact the sender immediately.
No employee or agent is authorised to enter into any binding agreement
or contract on behalf of Eduserv or Eduserv Technologies Ltd., unless
that agreement is subsequently confirmed by the conclusion of a written
contract or the issue of a purchase order.
Eduserv (Limited by Guarantee) – company number 3763109 - and
Eduserv Technologies Ltd – company number – 4256630 - are both
companies incorporated in England and Wales and have their registered
offices at Queen Anne House, 11 Charlotte Street, Bath, BA1 2NE.


_______________________________________________
cms mailing list
cms@...
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

[Søren Laursen]

Darren,

Still you should add Dynamicweb to your shortlist too ;-) Considering Dynamicweb is doing pretty well in Denmark where actually Sitecore, Typo3 and Umbraco also originate from.



Regards

Soeren


-----Original Message-----
From: cms-bounces@... [mailto:cms-bounces@...] On Behalf Of John M. Morse
Sent: 13. februar 2008 12:48
To: Austin, Darrel; cms@...
Subject: Re: [CMS] .net options these days?

Darrel

Not sure what your budget is nor the size of project your are completing
but I would suggest you need (must?) to look at

Sitecore
Ektron
Immediacy
Umbraco

Have varying degrees of exposure to all of these solutions, Sitecore
being our current tool of choice mainly because of its more of a content
delivery platform rather that a CMS and you should look into its
Sharepoint connector which will help with your legacy systems,l it hsas
a fully open API, which our developers like ;)

Ektron is a very feature rich CMS with excellent tools and also has a
Sharepoint connector, good support, an active developer community, great
web 2.0 social toolset and a published API

Immediacy is a smaller still WCMS also with Sharepoint connector

Umbraco is, well Umbraco, secretly I have a soft spot for this CMS and
are looking for an opportunity to use it in anger


HTH

John Morse
Information Architect
Professional Services Group
UPA, Prince 2, ISEB IT Architect, IAI

Eduserv Internet
Managed hosting & development
john.morse@...
tel: [phone]
fax: [phone]

http://www.eduserv.org.uk/internet/ 
Eduserv Internet is a service of Eduserv Technologies Ltd





-----Original Message-----
From: cms-bounces@...
[mailto:cms-bounces@...] On Behalf Of Austin, Darrel
Sent: 11 February 2008 14:15
To: cms@...
Subject: [CMS] .net options these days?

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
cms@...
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



Unless otherwise agreed expressly in writing by a senior manager of
Eduserv, this communication is to be treated as confidential and the
information in it may not be used or disclosed except for the purpose
for which it has been sent.
If you have reason to believe that you are not the intended recipient
of this communication, please contact the sender immediately.
No employee or agent is authorised to enter into any binding agreement
or contract on behalf of Eduserv or Eduserv Technologies Ltd., unless
that agreement is subsequently confirmed by the conclusion of a written
contract or the issue of a purchase order.
Eduserv (Limited by Guarantee) – company number 3763109 - and
Eduserv Technologies Ltd – company number – 4256630 - are both
companies incorporated in England and Wales and have their registered
offices at Queen Anne House, 11 Charlotte Street, Bath, BA1 2NE.


_______________________________________________
cms mailing list
cms@...
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

_______________________________________________
cms mailing list
cms@...
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