Telligent 的社区服务器
我工作的公司想要在我们的网站上添加博客功能，他们希望花费大量资金在他们购买的 CMS (sitecore) 上构建一些垃圾。 我向他们介绍了 Telligent 的社区服务器，今天我们举行了一场类似于销售的会议，以吸引营销人员加入。 我的问题是是否有人在使用社区服务器、剥皮和扩展它时遇到问题？
我想解释一下为什么我正在考虑社区服务器，该公司想要多个作者的多个博客。 我希望尽可能地摆脱管理部分，并且不认为有太多引擎拥有多个博客并不意味着数据库工作。 我还喜欢社区服务器提供的其他功能，并认为公司会发现它很有用，特别是媒体部分，因为现在我们有一些非常简单的方式来处理白皮书和其他东西。
编辑：我们实际上正在将 Sitecore 博客模块用于我们的 Intranet 上的单个博客（这实际上是 CMS 所提供的服务）。 我不喜欢我们的公共网站的一些原因是它们位于不同的服务器上，它不支持多个作者，没有内置的联合组织，从查看源代码和内容来看，我感觉有点脆弱我个人认为社区服务器的其他功能使其物有所值。
另一个编辑：在我公司的情况下，需要坚持使用在sql服务器上运行的.net软件，但我不介意看到其他人的推荐。 ExpressionEngine 看起来很有前途，将在我的个人盒子上尝试一下。
The company I work for is wanting to add blog functionality to our website and they were looking to spend an awful amount of money to have some crap being built on top of a CMS they purchased (sitecore). I pointed them to Telligent's Community Server and we had a sales like meeting today to get the Marketing folks on board.
My question is if anyone has had issues working with Community Server, skinning it and extending it?
I wanted to explain a bit why I am thinking Community Server, the company is wanting multiple blogs with multiple authors. I want to be out of the admin part of this as much as possible and didn't think there were too many engines that having multiple blogs didn't mean db work. I also like the other functionality that Community Server provides and think the company will find it useful, particularly the media section as right now we have some really shotty way of dealing with whitepapers and stuff.
edit: We are actually using the Sitecore blog module for a single blog on our intranet (which is actually what the CMS is serving). Some reasoning for why I don't like it for our public site are they are on different servers, it doesn't support multiple authors, there is no built in syndication, it is a little flimsy feeling to me from looking at the source and I personally think the other features of Community Server make its price tag worth it.
another edit: Need to stick to .net software that run on sql server in my company's case, but I don't mind seeing recommendations for others. ExpressionEngine looks promising, will try it out on my personal box.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（8）
Community Server 2008.5 允许您添加多个可以发布文章的成员。 还带有
Community Server 2008.5 您现在拥有 wiki、论坛和博客。 这可能是我一段时间以来见过的最好的基于网络的管理控制面板之一。 这使您可以轻松更改一些内容，包括网站的主题（或皮肤）。 对我来说，这是我一段时间以来见过的最具可扩展性的应用程序之一。 我们将其用于我们的网站 http://knowledgemgmtsolutions.com。
Community Server 2008.5 lets you add several members that can post articles. Also with
Community Server 2008.5 you now have wiki's along with forums and the blogs. This probably has one of the better web based admin control panel's I seen in a while. This let's you easily change several things including the site's theme (or skin). To me it is one of the most scalable applications I have seen in a while. We are using it for our site http://knowledgemgmtsolutions.com.
您还可以查看 Telligent Graffiti CMS。
http://graffiticms.com/
它支持多个博客和作者。
更新：它现已开源，可在 http://graffiticms.codeplex.com/ 获取
You can also take a look at Telligent Graffiti CMS.
http://graffiticms.com/
It supports multiple blogs and authors.
Update: It's now open source and available at http://graffiticms.codeplex.com/
换肤非常简单，并且侧边栏小部件创建起来并不困难（如果您不介意在代码中构建控件）。 这些小部件还允许用户在控制面板中轻松地进行自定义选项。 不过，我怀疑您是否会为社区服务器找到一个强大的小部件构建器社区。 与 WordPress 等博客的开发社区相比，没有什么可比的。
我建议从头开始模板并根据需要添加 CS 控件，以获得您喜欢的样式标记并仅使用您需要的内容。
设置不同的角色让用户发布到不同的博客也非常容易，不需要编码。 您可以拥有博客组，并只允许某些用户向某些博客发帖。
Skinning is pretty straightforward, and the sidebar widgets aren't very difficult to create (if you don't mind building controls in code). The widgets also allow options for the users to customize them in the control panel very easily. I doubt you'll find a strong community of widget builders for Community Server however. Nothing compared to the dev community for blogs like wordpress.
I recommend starting templates from scratch and adding in CS controls as needed, to get the markup you prefer for styling and to use only what you need.
Setting up different roles for users to post to different blogs is also very easy and requires no coding. You can have blog groups, and allow only certain users to post to certain blogs.
Sitecore 的论坛模块由社区服务器提供支持，并与 Sitecore CMS 集成。
Sitecore's Forum module is powered by Community Server and integrated with Sitecore CMS.
带有多站点管理器的表达式引擎非常适合这种情况。
Expression Engine with the Multi-Site Manager works great for that kind of situation.
您是否查看过 Sitecore 的共享源博客模块？
Have you had a look at the Shared Source blog module for Sitecore?
我使用社区服务器完成了很多项目。 如果您对开箱即用的功能感到满意，或者您不介意坚持使用开始的版本，我想您会很高兴。
我在使用 CS 时遇到的麻烦是客户想要 CS 不提供的功能，但又坚持在 Telligent 发布更新时保持升级到最新版本的能力。 您可以通过在单独的项目中进行所有更改或仅修改 aspx/ascx 文件（无代码隐藏）来支持这一点。 不管你计划得多么好，都需要某种形式的合并。
I've done quite a few projects using Community Server. If you're okay with the out-of-the-box functionality, or you don't mind sticking to the version you start with, I think you'll be very happy.
The times I've run into headaches using CS is when the client wants functionality CS does not provide, but also insists on keeping the ability to upgrade to the latest version whenever Telligent releases an update. You can mostly support that by making all of your changes either in a separate project or by only modifying aspx/ascx files (no codebehinds). Some kind of merge is going to be required though no matter how well you plan it out.
社区服务器本身对我来说非常可靠，但如果您需要的只是一个博客引擎，那么它可能有点大材小用了。 例如，剥皮是一项相当多的工作（尽管它们有非常强大的 Chameleon 主题引擎）。
如果您需要的话，我可能会仔细研究其中一种专用博客引擎，例如 BlogEngine.NET、dasBlog 或 SubText。 如果您认为需要更多“以社区为中心”的功能（例如论坛等），请选择社区服务器。
Community Server itself has been very solid for me, but if all you need is a blogging engine then it may be overkill. Skinning it, for example, is quite a bit of work (despite their quite powerful Chameleon theme engine).
I'd probably look closer at one of the dedicated blog engines out there, like BlogEngine.NET, dasBlog or SubText, if that's all you need. Go with Community Server if you think you'll want more "community-focused" features like forums etc.