Content Type Article - NCIOCPL/cgov-digital-platform GitHub Wiki

Items to Discuss/ Recommendations

  1. Change Syndication default to be unchecked (syndicating content should be a conscious decision, not a default). Migration Rule: Content that is currently syndicated should migrate into Drupal with this option checked so it continues to be syndicated.
  2. Remove fancy styling from the Stories of Discovery, and never have a key call out at the top of an article page
    • Intro text essentially is styled like body text (consistently across all articles), and appears above On This Page
    • Blogs keep intro text and its purple styling.
  3. If Stories of Discovery must keep their fancy styling, then:
    • Option 1: Create a key message field on Articles that have the blog purple styling, and would appear above intro text and OTP
      • We would replace the intro text field on blog posts, with the new key message field
    • Option 2: Turn the key message field into a new WYSIWYG Call out style to be inserted via a fancy button (in this case, for articles, the key message is added to the intro text field to get the purple styling at the top of the page ).
      • If we go with this option, we could deprecate the intro text field on blog posts, and blog content editors would use the fancy button to insert their key message in the body field so that it appears at the top of the content.

Naming

  • Display Name: Article
  • Machine-readable Name: cgov_article

Description

An information-rich content page that supports some structured information, like On This Page, citations, and inline feature cards. This content is likely to be useful to other websites/parties.

Fields

Common Fields

Unique Fields to This Content Type

Article Body*

  • Field Name: field_article_body
  • Label: Body
  • Type: Paragraphs
    • Allowed Types: Body Section
  • Required: No
  • Max characters: N/A
  • Tooltip Text: TBD
  • Cardinality: Multiple
  • Translatable: Yes
  • Uses paragraphs_asymmetric_translation_widgets for edit widget. (Important in order to allow translatable)

Body Section (Paragraph Type)

Heading
  • Field Name: field_body_section_heading
  • Label: Heading
  • Type: Text (plain)
  • Required: No
  • Max characters: 255
  • Tooltip Text: TBD
  • Cardinality: 1
  • Translatable: Yes
Content
  • Field Name: field_body_section_content
  • Label: Content
  • Type: Text (Formatted, Long)
  • Required: No
  • Max characters: N/A
  • Tooltip Text: TBD
  • Cardinality: 1
  • Translatable: Yes
  • Should use basic HTML format, when it becomes selectable

Meta Data

Common Metadata

Local Metadata

TBD

Form Display Order

How the fields should display on the form

  • Site Section
  • Pretty URL
  • Page Title
  • Browser Title
  • Card Title
  • Meta Description
  • List Description
  • Feature Card Description
  • Intro Text
  • Body
  • Lead Image
  • Promotional Image
  • Dates (Posted, Updated, Reviewed)
  • Date Display Mode
  • Related Resources
  • Citations
  • Public Use Text
  • Syndicate
  • Syndication Keywords
  • Search Engine Restrictions

Example URLs:

On this page

This will auto-generate using the Article Body Field with repeating sections

  • Sometimes the first heading on the page is an H3 (H2 font size was "too big"). Example: all Cancer Causing Substances We should not have to accommodate this, if you want an accordion on mobile, it must be an H2
  • Sometimes OTP shows both H2 and H3 (with H2s collapsing on mobile) Example: https://www.cancer.gov/about-cancer/coping/caregiver-support. This needs to be a conversation with Lynn and content owners to remove those H3s (following the pattern of PDQ where we only show H2s in the OTP). Analysis shows there are only 10 pages with this pattern
  • 45 pages have on this page code that doesn't collapse into accordion. These would need to be cleaned up to use our current code to become accordions on mobile, and then eventually be moved into the new version (post go-live).
  • If there is no heading provided for the section (i.e. no H2), no bullet is drawn in OTP. For the mobile accordion, the content will not be swallowed into the accordion.
  • Future requirement: Heading is not required, however if a heading is missing on any section other than the first section, the user cannot save.

Page Display

https://hzgfzw.axshare.com/#g=1&p=article

⚠️ **GitHub.com Fallback** ⚠️