最佳开源PHP CMS 2008

It's that time of the year again. Time to cast my vote as part of the jury in Packt's open-source awards, category "PHP CMS".

又是一年中的那个时候。 是时候作为Packt开源奖项类别“ PHP CMS”的评审团之一来投票。

(for my last year's rant, check the internet archive copy)

(对于我去年的咆哮，请查看Internet存档副本)

如何判断CMS？ (How to judge a CMS?)

How to judge a CMS? Tough one. How do you judge any piece of software anyway?

如何判断CMS？ 坚强的。 无论如何，您如何判断任何软件？

Features? Usually any system or product lists the features in way meant to wow you, I mean a list of features always looks nice, it's a sales tool. And the features don't mean that much, actually some say, you should underfeature the competition. Of course, you can't take that to the extreme and build software that does nothing. You need features, but the best CMS doesn't mean the one with the most features, neither the one with less. You just need the right mix and "right" may wildly vary depending on the task. Are you building an e-commerce site, a library of articles, a 5-page business card-like site, on online community? No way to judge a system without an idea of what you want it to do for you. And no way what you want to do is what everyone else wants to do.

特征？ 通常，任何系统或产品都会以让您赞叹的方式列出功能，我的意思是功能列表始终看起来不错，这是一种销售工具。 而且这些功能并不意味着太多，实际上有人说，您应该落后于竞争对手。 当然，您不能将其发挥到极致并构建不执行任何操作的软件。 您需要功能，但是最好的CMS并不意味着功能最多的一种，也不意味着功能最少的一种。 您只需要适当的组合，“正确”的内容可能会因任务而异。 您是否要在在线社区上建立一个电子商务网站，一个文章库，一个5页类似名片的网站？ 如果不知道自己想要做什么，就无法判断一个系统。 而且，您要做的就是其他所有人都想做的。

Quality? This is much easier. Does the code validate, YSlow score, accessibility, etc. Easy, even automated, but again, the system can be written beautifully but doesn't do the right thing or work the right way.

质量？ 这要容易得多。 代码是否经过验证，YSlow得分，可访问性等。容易甚至自动化，但是，该系统可以编写精美，但不能做正确的事情或以正确的方式工作。

Documentation? A must-have, usually a problem with any software. Can be too specific in areas that don't matter and completely lacking where you really need it. Or outdated. It's also nice to have some books, sign that the system is relatively popular, mature and at the end of it, it's cozier to share the couch with a book then with an online text. Also API documentation, at least it's easier to generate and keep updated.

文档？ 必备软件，通常是任何软件都存在的问题。 在无关紧要的领域中可能过于具体，并且完全缺少您真正需要的地方。 还是过时的。 拥有一些书籍也很高兴，这表明该系统相对流行，成熟，并且在最后，与一本书共享一本沙发，然后再与一个在线文本共享，这很有趣。 还有API文档，至少它更易于生成和保持更新。

Community? Very important, you'll inevitably have questions when you start working with the system. It would be nice to have a friendly place where you can ask/answer questions. But how do you judge a community? The only way is to get involved and spend time. No way to do this when you're judging 5 systems in a matter of days.

社区？ 非常重要，当您开始使用系统时，不可避免地会有问题。 拥有一个可以询问/回答问题的友善场所，将是很好的选择。 但是，您如何判断社区？ 唯一的方法就是参与并花费时间。 在短短几天内判断5个系统时就无法执行此操作。

判决 (Verdict)

It's virtually impossible to judge any piece of software until you start using it. It may have the right features, but they might be unfriendly or virtually unusable. It may have documentation, but not the one you need, etc, etc. So the only way is to spend time with the software and try to make it work for you.

在开始使用之前，几乎不可能判断任何软件。 它可能具有正确的功能，但可能不友好或几乎无法使用。 它可能有文档，但是没有您需要的文档等，因此，唯一的方法是花时间在软件上，并尝试使其适合您。

And since I've been meaning to create my personal stoyanstefanov.com, I thought it would be a good idea to kill two birds with one stone - cast my vote and have a working site at the end, powered by my personal CMS favorite.

而且由于我一直想创建自己的stoyanstefanov.com，所以我认为用一块石头杀死两只鸟是个好主意-投我一票，最后在我的个人CMS最喜欢的地方提供一个工作站点。

内容 (Content)

So I sit down and listed the features I need, nothing overly complicated, and also decided on some rough structure. Here's my feature list:

因此，我坐下来列出了我需要的功能，没有什么过于复杂的内容，还决定了一些粗糙的结构。 这是我的功能列表：

• Blog. In English and also in Bulgarian, nice test for i18n capabilities
  博客。 无论是英语还是保加利亚语，i18n功能的不错测试
• Photos
  相片
• Syndicated Twitter feed, probably the CMS will not have it out of the box, but syndicating content and consuming web services is so common these days that the software better be capable of doing it easily or let me write an extension easily
  联合发布Twitter feed，也许CMS不会立即提供它，但是如今联合发布内容和使用Web服务非常普遍，以至于该软件能够更好地做到这一点，或者让我轻松编写扩展
• Slides, with the help of Slideshare's API, same as above
  与Slides相同，在Slideshare的API的帮助下
• Books - a page for each book maybe, reviews, image, etc
  图书-每本书的页面可能包括评论，图片等
• Projects - list of stuff I'm involved in
  项目-我参与的工作清单
• Publications - articles I wrote for other sites and magazines
  出版物-我为其他网站和杂志撰写的文章
• Conferences - list the conferences I've spoken to, encourage people to invite me, bio blurb, hi-res photo
  会议-列出我所交谈的会议，鼓励人们邀请我，生物简介，高分辨率照片
• About
  关于
• Contact
  联系
• Social - links to facebook profile, linked in, etc
  社交-链接至Facebook个人资料，已链接等
• Sites - other sites of mine
  网站-我的其他网站
• Syndicated content - again, syndicate friendfeed or a Yahoo pipe that contains pretty much all my online activity, such as other blogs and even tiny things like last.fm love/hate ratings
  联合内容-同样，联合供稿feedfeed或包含我几乎所有在线活动的Yahoo管道，例如其他博客，甚至是last.fm之类的微小内容
• Subscribe - option to subscribe to RSS feeds or even monthly email
  订阅-订阅RSS feed或每月电子邮件的选项
• custom 404
  自定义404

All these features I would combine in 5 top-level menu items: blog, news, writing, speaking, info.

我将所有这些功能合并到5个顶级菜单项中：博客，新闻，写作，演讲，信息。

检查清单 (Checklist)

So now that I know what I want to build, I can go ahead and (attempt to) do it with each CMS while looking out for some pre-defined checks.

因此，既然我知道要构建的内容，就可以继续(尝试)对每个CMS进行操作，同时寻找一些预定义的检查。

信息 (Info)

URL: Maturity: (since when the CMS exists) Frequency of new releases: (is the project active)

URL：成熟度：(自CMS存在起)新版本的频率：(项目处于活动状态)

任务 (Tasks)

The best way to get a feeling of the software is by performing some tasks, the same tasks for all CMS

感受软件的最佳方法是执行一些任务，所有CMS都执行相同的任务

1. Download
   下载
2. Install
   安装
3. setup friendly urls
   设置友好的网址
4. setup sections and content
   设置部分和内容
5. customize presentation
   定制演示
6. customize homepage
   自定义首页
7. create an extension
   创建一个扩展
8. customize 404
   定制404

质量检查 (QA)

Test both the front-end and the back-end admin sections.

测试前端和后端管理部分。

• works without js
  没有js的作品
• works without css
  没有CSS的作品
• validates html
  验证html
• validates css
  验证CSS
• jslint
  jslint
• yslow grade
  慢级
• smush.it
  ush

杂项 (Misc)

• Is there a WYSIWYG, people like those (I avoid them)
  有所见即所得，像这样的人(我避免他们)
• available extensions
  可用的扩展
• available themes
  可用主题
• Documentation
  文献资料
• API docs
  API文档
• Community
  社区
• Books
  图书

ew！(Whew!)

Lotsa stuff, wish me luck with aaall that 🙂 And I would be interested to hear any comments on the subject. Thanks for reading!

Lotsa的东西，祝我一切顺利🙂而且，我很想听听有关该主题的任何评论。 谢谢阅读！

Tell your friends about this post on Facebook and Twitter

在Facebook和Twitter上告诉您的朋友有关此帖子的信息

翻译自: https://www.phpied.com/best-open-source-php-cms-2008/