有什么我不应该使页面变糊状的原因吗 [英] Is there any reason I shouldn't make pages folderish

问题描述

我发现最难向Plone最终用户解释的是必须制作一个文件夹，一个页面并将该文件夹的默认视图设置为页面以便具有嵌套页面的概念.有什么理由不应该在我的产品中包含页面内容类型的折叠式版本吗?

解决方案

现有产品提供的折叠式类型的行为几乎类似于最终用户的页面

例如产品.Richdocument和raptus.article.

我个人更喜欢raptus.article，因为它是组件的概念.编辑者可以激活轮播或图像库，并定义其中包含的图像显示在哪个组件中. 在许多项目中，我还定义了自定义组件，例如，如果编辑器打开该组件，则会在文章文本下显示addthis集成.

乌尔里希·施瓦茨(Ulrich Schwarz)的评论是正确的，即在版本控制中，使用像文件夹一样的内容类型作为页面会带来额外的复杂性. cmfeditions版本控制中的问题可以通过使用attributetorage代替原型字段的注释存储来解决. (请参见 https://dev.plone.org/ticket/11887 )

I find the hardest thing to explain to Plone end users is the concept of having to make a folder, a page and set the folder's default view to a page in order to have nested pages. Is there any reason I shouldn't include a folderish version of a page content type in my product?

解决方案

there are existing products that provide folderish types that almost behave like pages for the end-user

eg. Products.Richdocument and raptus.article.

personally i prefere raptus.article because of it's concept of components. editors can activate carousels, or image galleries and define which of the contained images are displayed in which component. in many project i also define custom components eg one for showing addthis integration under the article text if editors turn on the component.

Ulrich Schwarz is right when commenting that using folderish content types as pages brings in extra complexity when it comes to versioning. the problems in versioning with cmfeditions could most likle be solved by using attributestorage instead of annotationstorage for archetypes fields. (see https://dev.plone.org/ticket/11887)

这篇关于有什么我不应该使页面变糊状的原因吗的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！