1) 尽管我们有内部 PHP Wiki 和 Dot Net Nuke 站点也包含用户内容，但我们正在从 Microsoft Content Managemet Server 2002 迁移到 Sitecore 6.0。
2) 1,000-2,000 人需要迁移大约 3500 页的 Web 内容。
3) 到目前为止我很满意。 迁移过程中仍有大量工作要做，可能需要几年时间才能迁移所有内容，其中包括几年来未进行过处理的遗留 ASP 和 ASP.Net 1.1 和 2.0 站点。出色地。 要让我对这种规模的实现感到满意，需要做很多事情才能轻松完成。
1) We are moving from Microsoft Content Managemet Server 2002 to Sitecore 6.0 though we have internal PHP Wikis and Dot Net Nuke sites that have user content as well.
2) 1,000-2,000 people with about 3500 pages of Web content to migrate.
3) I'm content with it so far. There is still a lot of work to do in the migration and it will probably take a couple of years to move everything over, which includes legacy ASP and ASP.Net 1.1 and 2.0 sites that haven't been worked on in a few years as well. It would take a lot of things going easily for me to be happy with an implementation of this size.
Companies I worked for usually developed CMS systems inhouse I've mostly worked for webshops and when cranking out websites is your core business the best way to get an edge is to be on top of this sort of thing.
So custom CMSes for:
Simplicity, just deliver what the client wants and nothing else.
Understanding it, it's developed in house so you can usually just talk to the guy who wrote it.
Our external business orientated site is running joomla which once you get passed the learning procces of how it constructs sites, is very good for a multi-user environement.
The centre within which I work is somewhat multi-institutional (a good history of collaborative work) (one of two research centres situated within the same building) and the Plone sites that I'm setting up are fitting very nicely with diverse user/group requirements.
Tridion. And yes, there is that 3-year itch. Is Oracle on a new release or did the first implementation just look wrong now? I remember Stellent being on the development team's shortlist.
Us: Mid-sized (small?) 700+ employee company, with over a dozen websites, but not all sites have the CMS implemented. In-house development team has worked on, and still support, a few custom solutions. Legacy code never dies. :-)
All of the CMS we researched had compelling features, but for content re-use, cross-site sharing, and programmability we found Tridion to be a good fit (compared to Ektron and RedDot). Our mandate was to stay ".NET programmers" and not have the tool take over the site.
I'm comfortable with and like with Tridion, but admire those of you who've done CMS with multiple platforms.
1) We're using a CMS that was custom written in vbscript and sucks horribly. We're going to start using MODx for our external stuff, but we're not sure what's going to happen with our internal stuff.
2) A university with about 30,000 students (about 10,000 of which have ties to my department).
3) MODx looks cool, but haven't had much of a chance to use it. As stated previously, our other CMS sucks.
1) CMS: Oracle's BEA Aqualogic 2) Size: 10,000+ 3) Experience: As an end user with full community and content admin privileges, I find the tool to be outdated and stifling in terms of knowledge sharing and trying to get the benefits that exist in social networks. Perhaps this is due to the implementation, and not an inherent weakness in the product. Not sure of the future direction of the product either, since Oracle recently acquired it.
发布评论
评论（13）
我们使用 Plone 开源作为内部站点...
We use Plone open source for the internal site...
我们使用 DotNetNuke 内联网站点。 我认为我们需要升级或重新设计，因为我更喜欢 Joomla。
We use a DotNetNuke intranet site. I think we need to upgrade or redesign cause I like Joomla much more.
1) 尽管我们有内部 PHP Wiki 和 Dot Net Nuke 站点也包含用户内容，但我们正在从 Microsoft Content Managemet Server 2002 迁移到 Sitecore 6.0。
2) 1,000-2,000 人需要迁移大约 3500 页的 Web 内容。
3) 到目前为止我很满意。 迁移过程中仍有大量工作要做，可能需要几年时间才能迁移所有内容，其中包括几年来未进行过处理的遗留 ASP 和 ASP.Net 1.1 和 2.0 站点。出色地。 要让我对这种规模的实现感到满意，需要做很多事情才能轻松完成。
1) We are moving from Microsoft Content Managemet Server 2002 to Sitecore 6.0 though we have internal PHP Wikis and Dot Net Nuke sites that have user content as well.
2) 1,000-2,000 people with about 3500 pages of Web content to migrate.
3) I'm content with it so far. There is still a lot of work to do in the migration and it will probably take a couple of years to move everything over, which includes legacy ASP and ASP.Net 1.1 and 2.0 sites that haven't been worked on in a few years as well. It would take a lot of things going easily for me to be happy with an implementation of this size.
我工作过的公司通常在内部开发 CMS 系统，我主要为网上商店工作，当制作网站是您的核心业务时，获得优势的最佳方法就是掌握此类事情。
因此，定制 CMS 可以用于：
Companies I worked for usually developed CMS systems inhouse I've mostly worked for webshops and when cranking out websites is your core business the best way to get an edge is to be on top of this sort of thing.
So custom CMSes for:
我们面向外部业务的网站正在运行joomla，一旦您通过了如何构建网站的学习过程，就可以非常适合多用户环境。
公司 = 25+ 人
Our external business orientated site is running joomla which once you get passed the learning procces of how it constructs sites, is very good for a multi-user environement.
Company = 25+ people
在整个机构范围内，我们看到了各种各样的系统。
一些克隆人网站。 我是克隆人的粉丝。
我工作的中心在某种程度上是多机构的（协作工作的良好历史）（位于同一栋大楼内的两个研究中心之一），并且我正在建立的 Plone 站点非常适合不同的用户/群体要求。
Institution-wide we see a variety of systems.
A few Plone sites. I'm a Plone fan.
The centre within which I work is somewhat multi-institutional (a good history of collaborative work) (one of two research centres situated within the same building) and the Plone sites that I'm setting up are fitting very nicely with diverse user/group requirements.
在我的日常工作中，我使用 Tridion，我的一些同事使用 Hippo。 在家里我使用 Plon。
In my daily work, I use Tridion, and some of my colleagues use Hippo. At home I use Plone.
1) 我的公司目前使用Word Press 或根本没有 CMS。 然而，我们正在开发一个 CMS，它将完全按照我们想要的方式工作。
2) 这是我和我的朋友，所以我们两个人
3) 我们仍在启动并寻找客户，所以还没有机会使用它。
1) My company currently uses Word Press or no CMS at all. We are however working on a CMS that will work exactly as we want it to.
2) It's me and my friend so 2 of us
3) We're still starting up and finding clients so haven't had a chance to use it.
特里迪翁。 是的，还有三年之痒。 Oracle 是否发布了新版本，或者第一个实施现在看起来有问题？ 我记得 Stellent 曾在开发团队的候选名单中。
我们：
中型（小型？） 700 多名员工的公司，拥有十几个网站，但并非所有网站都实施了 CMS。 内部开发团队已经开发并仍在支持一些定制解决方案。 遗留代码永远不会消亡。 :-)
我们研究的所有 CMS 都具有引人注目的功能，但对于内容重用、跨站点共享和可编程性，我们发现 Tridion 非常适合（与 Ektron 和 RedDot 相比）。 我们的任务是继续成为“.NET 程序员”，而不是让该工具接管网站。
我对 Tridion 感到满意并喜欢，但钦佩那些使用多个平台完成 CMS 的人。
Tridion. And yes, there is that 3-year itch. Is Oracle on a new release or did the first implementation just look wrong now? I remember Stellent being on the development team's shortlist.
Us:
Mid-sized (small?) 700+ employee company, with over a dozen websites, but not all sites have the CMS implemented. In-house development team has worked on, and still support, a few custom solutions. Legacy code never dies. :-)
All of the CMS we researched had compelling features, but for content re-use, cross-site sharing, and programmability we found Tridion to be a good fit (compared to Ektron and RedDot). Our mandate was to stay ".NET programmers" and not have the tool take over the site.
I'm comfortable with and like with Tridion, but admire those of you who've done CMS with multiple platforms.
1) 我们使用的 CMS 是用 vbscript 自定义编写的，非常糟糕。 我们将开始使用 MODx 来处理我们的外部内容，但我们不确定我们的内部内容会发生什么。
2) 一所拥有大约 30,000 名学生的大学（其中大约 10,000 名与我的系有联系）。
3）MODx看起来很酷，但是还没有太多机会使用它。 如前所述，我们的其他 CMS 很糟糕。
1) We're using a CMS that was custom written in vbscript and sucks horribly. We're going to start using MODx for our external stuff, but we're not sure what's going to happen with our internal stuff.
2) A university with about 30,000 students (about 10,000 of which have ties to my department).
3) MODx looks cool, but haven't had much of a chance to use it. As stated previously, our other CMS sucks.
德鲁帕尔。 我已经将它用于中小型项目。
Drupal. I've used it for small and medium sized projects.
我们使用 Alterian 内容管理器应用程序。 它非常强大，非常适合我们的需求。
20000 名员工+
非常高兴。 开发人员和业务团队发现该应用程序非常易于使用。
We use the Alterian Content Manager application. It is very robust and suites our needs well.
20000 staff+
Very happy. Developers and business team find the application very easy to work with.
1) CMS：Oracle 的 BEA Aqualogic< /a>
2）规模：10,000+
3) 经验：作为拥有完整社区和内容管理权限的最终用户，我发现该工具在知识共享和试图获得社交网络中存在的好处方面已经过时且令人窒息。 也许这是由于实施造成的，而不是产品固有的弱点。 也不确定该产品的未来方向，因为 Oracle 最近收购了它。
1) CMS: Oracle's BEA Aqualogic
2) Size: 10,000+
3) Experience: As an end user with full community and content admin privileges, I find the tool to be outdated and stifling in terms of knowledge sharing and trying to get the benefits that exist in social networks. Perhaps this is due to the implementation, and not an inherent weakness in the product. Not sure of the future direction of the product either, since Oracle recently acquired it.