CMS 驱动内容的部署
我正在研究改变当前创建营销网站的策略。目前，我使用简单的包含系统，完全用 PHP 从头开始构建网站。所有代码（以及内容）都存储在文件（而不是数据库）中，允许我使用 Subversion 进行历史记录和部署。
我想转而对网站使用 CMS，但我不知道如何处理大量内容更改和部署。
大多数时候，营销网站的变化并不简单。产品发布可能涉及同时更改、添加、删除和移动多个页面。所有这些更改都需要在临时服务器上进行和审核。当一切准备就绪后，就需要在特定时间立即投入生产。
大多数 CMS 的工作流程解决方案是允许编辑在 CMS 内进行单页审阅。大多数时候，他们正在审查尚未发布的页面，而不是对已经存在的页面进行更改。最重要的是，该审查是在生产站点上完成的。这更适合定期文章的创建，例如博客。营销网站确实有新闻部分，但这无助于推出整个“全新事物”产品部分。
我似乎找不到适合我的工作流程的 CMS 解决方案：
- 在开发环境中创建内容。
- 将所有更改部署到登台服务器，供所有相关方审核（无需在 CMS 中单击“预览”按钮）。
- 在指定时间部署所有批准的更改。
- 允许通过 CMS 调整内容
I'm researching changing my current strategy for creating marketing websites. Currently, I build sites entirely from scratch in PHP, using a simple system of includes. All code (and therefore content) is stored in the files (rather than a database) allowing me to use Subversion for history and deployment.
I'd like to move to using a CMS for sites, but I don't know how do deal with large sets of content changes and deployment.
Most of the time changes in marketing sites are not simple. A product launch could involve changing, adding, deleting and moving around of many pages at once. All these changes need to be made and reviewed on a staging server. And when everything is ready, it needs to go into production, all at once, at a specific time.
Most CMS's solution to workflow is to allow single page review, by an editor, from within the CMS. And most of the time, they are reviewing a page that is yet to be published, rather than changes to a page that is already there. On top of that, this review is done on the production site. This is geared more towards periodic article creation, like blogging. Marketing sites do have news sections, but this doesn't help in launching the entire "Brand New Thing" product section.
I can't seem to find a CMS solution for my workflow:
- Create content in a development environment.
- Deploy all changes to a staging server for review by all parties involved (without having to find a click some "preview" button within the CMS).
- Deploy all approved changes at a specified time.
- Allow for tweaks to content through the CMS
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
可信度：我领导的团队构建了一个相当大的 CMS*，我们有很多与您描述的相同的需求。例如，编辑需要创建一百页的营销材料、图像、电影；将其翻译成 65 种语言并在全球范围内同时部署。
如何接近它？有很多方法，而您建议的方法有其自身的一系列困难。我们发现效果很好的模型是单页审核模型与批量调度相结合。大多数内容管理系统允许编辑者创建页面，但签入为“草稿”而不是“发布”。对于未登录的用户，该页面将返回 404，但对于登录的用户，他们将看到最新的草稿版本。一旦批准者验证了所有内容，他们就可以安排同时发布所有 n 个页面。这确实可以很好地扩展和扩展。
如果不了解更多有关您的独特问题集的信息，我无法推荐特定的解决方案，但我鼓励您不要在此过程的早期将自己锁定在特定的系统模型中。根据您所说的，大多数优秀的 CMS 系统都应该是可行的候选者，只需进行少量的定制。
*近一百万页、超过 65 种语言、数千名编辑、每天数百万次点击 - http://www.volvo.com沃尔沃.com
Credibility: I lead the team that builds a rather large CMS* and we have a lot of the same demands you describe. For example, editors needing to create a hundred pages of marketing material, images, movies; translate that into 65 languages and deploy it all at the same time worldwide.
How to approach it? There's plenty of approaches, and the one you're suggesting has its own set of difficulties. The model we've found works quite well is the single-page-review model combined with batch scheduling. Most content management systems allow editors to create pages but check-in as "Draft" rather than "Publish". To a non-logged-in user, that page will return a 404, but to a logged-in user, they will see the latest draft version. Once an approver has validated all the content, they can schedule all n pages to be published at the same time. This does indeed scale up and out quite well.
I can't recommend a specific solution without knowing more about your unique problem set, but I encourage you not to lock yourself in to a specific system model this early in the process. Based on what you've said, most good CMS systems should be viable candidates with a small amount of customization.
*Nearly a million pages, over 65 languages, thousands of editors, millions of hits a day - http://www.volvo.com