GHOST CMS - Channels

Channels

If you want something more flexible than taxonomies, but less rigid than collections, then channels might be for you.

A channel is a custom stream of paginated content matching a specific filter. This allows you to create subsets and supersets of content by combining or dividing existing posts into content hubs.

Unlike collections, channels have no influence over a post‘s URL or location within the site, so posts can belong to any number of channels.

The best way to think of channels is as a set of permanent search results. It‘s a filtered slice of content from across your site, without modifying the content itself.

Creating a channel

Channels are defined as a custom route, with a custom controller property called channel, and a filter to determine which posts to return.

routes:
  /apple-news/:
    controller: channel
    filter: tag:[iphone,ipad,mac]
  /editors-column/:
    controller: channel
    filter: tag:column+primary_author:cameron

In this example there are two channels. The first is a channel which will return any posts tagged iPhone, iPad or Mac on a custom route of site.com/apple-news/.

The second is a special Editor‘s Column area, which will return any posts tagged with Column, but only if they‘re explicitly authored by Cameron.

These are two small examples of how you can use channels to include and exclude groups of posts from appearing together on a custom paginated route, with full automatic RSS feeds included as standard. Just add /rss/ to any channel URL to get the feed.

When to use channels vs collections

Collections and channels share a lot of similarities, because they‘re both methods of filtering a set of posts and returning them on a custom URL.

So how do you know when to use which?

You should generally use a collection when...

There‘s a need to define permanent site structure and information architecture

  • You‘re sorting different types/formats of content
    eg. posts are blog posts OR podcasts
  • You‘re filtering incompatible content
    eg. posts are either in English OR German
  • You want the parent filter to influence the post‘s URL
    eg. an index page called /news/ and posts like /news/my-story/

You might be better off with a channel if...

All you need is a computed view of a subsection of existing content

  • You‘re combining/grouping different pieces of content
    eg. posts tagged with news AND featured
  • You‘re dividing existing streams of content with multiple properties
    eg. posts tagged with news but NOT authored by steve
  • You want to be able to update/change properties without affecting post URLs
    eg. quickly creating/destroying new sections of a site without any risk

If you‘re still not sure which is the best fit for you, drop by the Ghost Forums and share what structure you‘re hoping to accomplish. There‘s a large community of Ghost developers around to help.

原文地址：https://www.cnblogs.com/QDuck/p/12081553.html

时间： 2024-08-01 01:02:40

GHOST CMS - Channels的相关文章

GHOST CMS - Properties

Properties This is a full list of all the available properties that can be used within your routes.yaml config file to manipulate your URL structure Index of all available properties Property Description template Determines which Handlebars template

GHOST CMS - 创建自定义主页 Creating a custom home page

创建自定义主页 Creating a custom home page 为你的网站创建一个自定义的主页是一个让你从人群中脱颖而出的好方法,并把你自己独特的印记存放在你的网上.本教程向您展示了如何在Ghost中自定义和开发自己的自定义主页. Creating a custom home page for your site is a great way to set yourself apart from the crowd and put your own unique stamp on you

GHOST CMS - 配置 Config

Config For self-hosted Ghost users, a custom configuration file can be used to override Ghost's default behaviour. This provides you with a range of options to configure your publication to suit your needs. 对于自承载的Ghost用户,可以使用自定义配置文件覆盖Ghost的默认行为.这为您提供

GHOST CMS -上下文概述 Context Overview

Context Overview上下文概述 Each page in a Ghost theme belongs to a context, which determines which template is used, what data will be available and what content is output by the {{body_class}} helper. Ghost主题中的每个页面都属于一个上下文,它决定使用哪个模板.哪些数据可用以及{{body_class}

GHOST CMS - 索引Index

Index Use: {{#is "index"}}{{/is}} to detect this context. 使用:{{#is "index"}}{{/is}}来检测这个上下文. Description描述 index is the name for the main post list in your Ghost site, the index context includes the home page and subsequent pages of th

GHOST CMS - Data Helpers

Data Helpers Data helpers are used to output data from your site. Use this reference list to discover what each handlebars helper can do when building a custom Ghost theme. Available data helpers @config @site navigation post url title img_url excerp

GHOST CMS - Content Taxonomies

Content Taxonomies Taxonomies are groupings of posts based on a common relation. In Ghost, this is always defined by the post's author or tag Using taxonomies, Ghost will automatically generate post archives for tags and authors like /tag/getting-sta

GHOST CMS - Responsive Images 图片显示

Responsive Images Optimise the performance of your site by outputting images at different sizes depending on where they appear Overview So you upload glorious 2000px feature images to all your posts to appear in the giant hero/header on individual ar

GHOST CMS - Content Collections

Content Collections Collections are the backbone of how posts on a Ghost site are organised, as well as what URLs they live on. You can think of collections as major sections of a site which represent distinct and separate types of content, for examp