RFC: SectionPage with `ContentType` and `ContentSubType`

[bobaaaaa]

What

Currently, we only have:

ArticlePage.Article.type
ArticlePage.Article.sub_type

I would like to introduce the following addition (naming tbd):

SectionPage.Section.type = 'section'
SectionPage.Section.sub_type = 'news' | 'frontpage' | 'advertorial' | 'themepage'

In paper is already a type section. This makes it much easier for us to calculate standard info/properties/values in some places. We have an interface Page shared between Article- and Section-Pages.

More Examples

• /test-homepage/ could also have the sub_type frontpage.
• /themen/* with sub_type themen for easier cache header
• /authors/ with sub_type author for custom commercial settings
• /newsletter/ with sub_type compliance to disable all commercials (like on the article page)

[thisismana]

I approve this motion!

edit: @bobaaaaa
if there is only one main type section, why do we need subtypes in the first place? maybe promote all suggested subtypes to main types instead?

[bobaaaaa]

That could theoretically also work. The thing is, in paper we have a union (base) type for all pages (section & all articles). That means the typescript compiler would see something like this:

// with type "section" + subtypes
function foo(page: Page) {
  // page.type === 'article' | 'video' | 'gallery' | 'embed' | 'external' | 'author' | 'section'
  if (page.type === 'section') {
    // do something on all sections
  }
}

// with type "frontpage", "advertorial" + no subtypes
function foo(page: Page) {
  // page.type === 'article' | 'video' | 'gallery' | 'embed' | 'external' | 'author' | 'frontpage' | 'advertorial'
  if (page.type === 'frontpage' || page.type === 'advertorial') {
    // do something on all sections
  }
}

That is sometimes also hard for the article pages. There is no "base" identifier for content/detail pages.