无头CMS如何提供页面管理/构建器功能？
我们正在使用传统的CMS，它也提供API（REST＆amp; GraphQl）在页面构建器功能之上暴露内容，我想了解：
- 如何知道我的传统CMS是否也是真正的无头CMS？
- 无头CM可以提供页面管理功能，还是只能 创建可以标记的内容件＆amp;通过API暴露于 多个频道？
- 如果是这种情况，那么我的前端逻辑不是 在渲染页面了解哪个 内容将首先＆amp;最后一个？
- 这不会在CMS和amp之间产生紧密的耦合；前端（BE 它以分类法的形式）？
- 当我的无头CM中，内容作者是否有真正的优势 相信他们会失去阻力＆amp;常见的Drop / Wyswyg功能 在传统的CMS中？
谢谢
We are using a traditional CMS that also offers API (Rest & GraphQL) to expose content on top of page builder capabilities, I want to understand:
- How to know if my traditional CMS is also a true Headless CMS?
- Can a headless CMS offer Page management capability or it can only
create the content pieces that can be tagged & exposed via API to
multiple channels?- If that is the case, then doesn't my front-end logic needs to take
care of a lot of things while rendering the page to understand which
content will go first & which one last? - Wouldn't this create a tight coupling between CMS & Front End (be
it in the form of taxonomy)?
- If that is the case, then doesn't my front-end logic needs to take
- Is there any real advantage for Content authors in headless CMS as I
believe they will lose the drag & drop / WYSWYG features that is common
in traditional CMS?
Thanks
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
只有在内容与显示的上下文完全分开时，您的CMS才真正无头，也就是说，您应该能够更改内容的到达目的地，并让您的前端确定何处，何处，布局内容。如果您的CMS控制或完全拥有 ，它不再是无头。如果您使用的是内容，则可以通过以非常结构化的顺序产生的JSON响应来更容易。在这种情况下，您将提供一些某些上下文，但它与依赖关系无处不在。 API的这些响应是可编辑的。因此，您可以轻松地更改此内容的内容。
是的，可以，无头CMS提供足够的元数据（ID的slugs等），以便您在Web应用程序上创建可变路由。 Contentful还具有将SEO信息与新内容类型相加的能力。请记住，A 页面 可以是具有其他内容类型的内容类型。从这个意义上讲，您的页面应该能够接受通用组件对象，这将为每个对象提供特定的布局。然后，该布局将带有内容的内容。
就首先了解的理解而言，这可以通过来自满足或其他无头CMS的结构化JSON响应来推断。因此，正确布置事物的顺序并不多。这是他们文档的一个例子。如果您的条目是包含其他类型的内容的单个条目，则它们以它们出现在无头CM中的顺序，这意味着编辑人员可以在选择时向上和向下移动。
https://www.contentful.com/developers/docs/references/content-delivery-api/#/reference/entries/entry/entry/get-a-a-single-endry-console/console
“ 是的。您必须在前端进行大量工作以适应这一点，但是长期有好处。最终，一旦拥有一套内容类型和布局，编辑人员就可以变得自治。
Your CMS is truly headless only if the content is completely separated from the context it is displayed in, that is, you should be able to change the destination of where the content goes, and have your front end determine where and how to layout the content. If your CMS controls or entirely owns this, it is no longer headless. If you're using contentful, this can be made easier by their JSON responses that come in a very structured order. In this case you are providing some context, but it is not anywhere near a dependency. These responses from the API are editable. So you can easily change this dependent on the destination of the content.
Yes it can, Headless CMS's provide enough metadata (ID's Slugs etc.) for you to create variable routing on your web application. Contentful also has the capability to attach SEO information with new content types. Keep in mind, a Page can be a content type that holds other content types. In this sense, your pages should be able to accept generic component objects, which will render a specific layout for each. Then that layout is backed with content from contentful.
As far as understanding which goes first, this can be inferred by the structured JSON response that comes from contentful or other headless CMS's. So it isn't much work to layout the order of things correctly. Here is an example from their docs. If your entry is a single entry that contains other types of content, they come in the order that they appear within the headless CMS, which means editors can shift things up and down as they choose.
https://www.contentful.com/developers/docs/references/content-delivery-api/#/reference/entries/entry/get-a-single-entry/console
to put it shortly, yes. You have to do a larger amount of work on the front end to accommodate this, but there are benefits long term. Once you have a suite of content types and layouts, eventually, the editors can become autonomous.