Comments for ContentMatters http://www.contentmatters.com Putting content in context Wed, 10 Mar 2010 07:31:06 +0000 http://wordpress.org/?v=2.7.1 hourly 1 Comment on Open Text and Vignette not a CA-style acquisition by Jon Marks http://www.contentmatters.com/2009/05/20/open-text-and-vignette-not-a-ca-style-acquisition/comment-page-1/#comment-17 Jon Marks Mon, 25 May 2009 17:45:30 +0000 http://www.contentmatters.com/?p=60#comment-17 While I agree it isn't a CA-style acquisition, I don't think it is clear whether the Vignette Content Management solution is going to be enhanced significantly. Vignette have struggled to enhance it much for the last 5 years - I doubt this will change. I see these possibilities for the VCM if it is going to continue: - VCM becomes the "Enterprise" offering, while RedDot becomes the "Corporate" edition. Alterian style. I don't think this is likely - would be a bit on an embarrassing step-down for RedDot which OpenText have been touting as Enterprise Ready - They both become Enterprise ready. VCM becomes the Java solution, while RedDot becomes the .NET edition - They split on vertical. Vignette could become the solution for Media/Telco/etc where they are traditionally strong VAP will stick around and become the defacto Open Text portal. I don't see which of the other offerings will survice. Full thoughts here: http://jonontech.com/2009/05/10/will-vignette-give-open-text-food-poisoning/ Jon While I agree it isn’t a CA-style acquisition, I don’t think it is clear whether the Vignette Content Management solution is going to be enhanced significantly. Vignette have struggled to enhance it much for the last 5 years - I doubt this will change.

I see these possibilities for the VCM if it is going to continue:

- VCM becomes the “Enterprise” offering, while RedDot becomes the “Corporate” edition. Alterian style. I don’t think this is likely - would be a bit on an embarrassing step-down for RedDot which OpenText have been touting as Enterprise Ready
- They both become Enterprise ready. VCM becomes the Java solution, while RedDot becomes the .NET edition
- They split on vertical. Vignette could become the solution for Media/Telco/etc where they are traditionally strong

VAP will stick around and become the defacto Open Text portal. I don’t see which of the other offerings will survice.

Full thoughts here:
http://jonontech.com/2009/05/10/will-vignette-give-open-text-food-poisoning/

Jon

]]> Comment on About by Tony Karrer http://www.contentmatters.com/about/comment-page-1/#comment-12 Tony Karrer Thu, 12 Mar 2009 23:08:31 +0000 http://contentmatters.com/wordpress/?page_id=2#comment-12 Hi Michael, We’ve built technology that takes existing content organizes it in a way that's a good user experience such that it helps with long tail search optimization. We've tested this and it has done a good job of getting traffic. I'm trying to figure out business models and I'm looking to get feedback. Based on your background, I think you might have some good input. Are you open to a conversation around this? Tony Hi Michael,

We’ve built technology that takes existing content organizes it in a way that’s a good user experience such that it helps with long tail search optimization. We’ve tested this and it has done a good job of getting traffic.

I’m trying to figure out business models and I’m looking to get feedback.

Based on your background, I think you might have some good input.

Are you open to a conversation around this?

Tony

]]> Comment on Content management vendors should court interactive agencies who have their own content mangement solutions by Kenny Tomlin http://www.contentmatters.com/2009/02/18/content-management-vendors-should-court-interactive-agencies/comment-page-1/#comment-10 Kenny Tomlin Thu, 19 Feb 2009 01:10:59 +0000 http://contentmatters.com/?p=11#comment-10 Interesting article and perspective. Thank you for highlighting our agency. I thought I would add a little commentary from the inside. I made the decision when starting Rockfish that we would develop our own Content Management Software for a few reasons: 1) We are a technology driven digital agency. Our programmers outnumber our creative's 3 to 1. We love getting our hands dirty with the code. 2) We wanted complete control and flexibility. We have never had to say "the software can't do it." Our CMS has been deployed numerous times for both small and large companies, and each time it's custom tailored to their exact needs. You would be surprised how scalable and robust our CMS is. You may also be surprised by some of the custom functionality we have developed for a client that you wouldn't find in even a full-scale CMS. 3) We want form and function to compliment each other. Our sites are hopefully as easy to manage as they are to browse. I think it is every bit as important that a digital agency architect the back-end experience for their client as it is the front-end for the sites audience. I do know that there are a lot of great CMS products on the market. We have worked with some on projects where the client already had a relationship or preference. However, at Rockfish we have found that owning our own technologies has been a competitive advantage for us and has allowed our team to support our clients needs, regardless of how unique they may be. By the way, most of the craziest requirements we have created didn't come from the IT department or our users, but from their legal department. Thanks again for the great posting and insight. Interesting article and perspective. Thank you for highlighting our agency. I thought I would add a little commentary from the inside.

I made the decision when starting Rockfish that we would develop our own Content Management Software for a few reasons:

1) We are a technology driven digital agency. Our programmers outnumber our creative’s 3 to 1. We love getting our hands dirty with the code.

2) We wanted complete control and flexibility. We have never had to say “the software can’t do it.” Our CMS has been deployed numerous times for both small and large companies, and each time it’s custom tailored to their exact needs. You would be surprised how scalable and robust our CMS is. You may also be surprised by some of the custom functionality we have developed for a client that you wouldn’t find in even a full-scale CMS.

3) We want form and function to compliment each other. Our sites are hopefully as easy to manage as they are to browse. I think it is every bit as important that a digital agency architect the back-end experience for their client as it is the front-end for the sites audience.

I do know that there are a lot of great CMS products on the market. We have worked with some on projects where the client already had a relationship or preference. However, at Rockfish we have found that owning our own technologies has been a competitive advantage for us and has allowed our team to support our clients needs, regardless of how unique they may be. By the way, most of the craziest requirements we have created didn’t come from the IT department or our users, but from their legal department.

Thanks again for the great posting and insight.

]]> Comment on Pros and cons of getting laid off by contentmatters http://www.contentmatters.com/2009/02/03/hello-world/comment-page-1/#comment-3 contentmatters Tue, 10 Feb 2009 18:36:23 +0000 http://contentmatters.com/wordpress/?p=1#comment-3 <a href="#comment-2" rel="nofollow">@Imelda</a> I guess coming from the days when Web Content Management meant writing your own in Perl, I have a respect for the Vignette products. Usability was never the strong suit, but that architecture scales like crazy. @Imelda
I guess coming from the days when Web Content Management meant writing your own in Perl, I have a respect for the Vignette products. Usability was never the strong suit, but that architecture scales like crazy.

]]> Comment on Pros and cons of getting laid off by Imelda http://www.contentmatters.com/2009/02/03/hello-world/comment-page-1/#comment-2 Imelda Tue, 10 Feb 2009 16:59:36 +0000 http://contentmatters.com/wordpress/?p=1#comment-2 At my last job, I had to work with Vignette. I went to the Austin offices for 2 weeks to learn and help with content ramp-up. I loved being in Austin but hated Vignette with a passion. At my last job, I had to work with Vignette. I went to the Austin offices for 2 weeks to learn and help with content ramp-up. I loved being in Austin but hated Vignette with a passion.

]]>