CQ aka AEM |蓝图与实时副本 [英] CQ aka AEM | Blueprints vs. Live copies

问题描述

在cq中，我们可以通过选择新站点... 或直接通过蓝图创建实时副本。通过选择 New Live Copy ... 来使内容节点处于低谷。

In cq we can create live copies by either blueprints by opting "New Site..." or directly trough content nodes by opting for "New Live Copy...".

在两种情况下，都保持了继承力和推出也以相同的方式工作。那么，使用一个相对于另一个的优势是什么。

In both the cases inheritance is maintained and roll-out works too in same ways. So what is the advantage of using one over other.

有任何意见吗？

推荐答案

实时复制

可以为一个简单的页面或一棵页面的树创建实时副本，并且根据发布配置的不同，可以创建页面及其子页面。实时副本可以链接到部署配置，也可以使用系统的默认配置。
在源页面的结构上没有正式的要求。
实时副本可能引用一个蓝图，而只能引用一个蓝图。

Live copies can be created for just a simple page or a tree of pages and might the page and it's subpages depending on the rollout configuration. A live copy can be linked to a rollout config or will use the system's default one. There is no formal requirement on the source page's structure. A live copy might reference a blueprint, while it can only reference to a single blueprint.

蓝图

蓝图针对完整的多语言网站项目的推出，并且是控制多个推出配置和实时副本的工具。
蓝图要求源站点具有某种结构：
-一个根级页面
-根的直属子级定义站点的语言分支
-每种语言都包含一种或多种更多的子页面。

Blueprints target the rollout of complete multilingual website projects and are a tool to control multiple rollout configs and live copies. A blueprint requires a certain structure for the source site: - One root level page - The root's immediate childs define the language branches of the site - each language contains one or more child pages.

借助蓝图，您可以控制多个实时副本，并可以为蓝图的实时副本集中一致地部署配置。
蓝图部署将推动对其所有实时副本的修改。

Blueprints allow you to control multiple live copies and centrally consistent rollout configs for the blueprint's live copies. A blueprint rollout will push modifications to all it's live copies.

蓝图的使用场景

继承和推出的工作方式相同。仅仅因为蓝图使用实时副本。
但是，蓝图可帮助您组织大型多语言站点的部署方案。试想一下一个公司网站，该网站提供需要翻译并保持同步的两位数或什至三位数的语言环境。
在这种情况下，您最终可能会获得难以理解和可维护的数量的实时复制和推出配置。
取决于设计蓝图标准化新语言/市场/区域设置的推出，因为可以通过蓝图模板集中管理整个流程，因此可以为您的流程提供更高程度的治理。

Inheritance and rollout work the same way. Just because blueprint make use of live copies. But blueprints help you to organize your rollout scenarios for large multilingual sites. Just imagine a corporate website that provides a two or even three digit number of locales which that need to be translated and kept in sync. In such a scenario you will likely end up with a hardly understandable and maintainable number of live copy and rollout configurations. Depending on a blueprint to e.g. standardize the rollout of a new language/market/locale provides you higher degree of governance over your process as the complete process centrally manageable through the blueprint template.

但是，只要您没有这种情况，在没有完整的蓝图开销的情况下就可以了。

But as long as you do not have such a scenario you might be fine without having the complete blueprint overhead.

这篇关于CQ aka AEM |蓝图与实时副本的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！