Diff: reference/news-release-standards
From 1d66573 to 1d66573
+0 / −0 lines
| Before | After |
|---|---|
| --- | --- |
| schema: foundry-doc-v1 | schema: foundry-doc-v1 |
| type: topic | type: topic |
| slug: news-release-standards | slug: news-release-standards |
| short_description: "Enforces strict formatting rules for corporate news syndication: left alignment, title case discipline, geographic precision, and standardized header and dateline structures ensuring institutional authority across physical and digital mediums." | short_description: "Enforces strict formatting rules for corporate news syndication: left alignment, title case discipline, geographic precision, and standardized header and dateline structures ensuring institutional authority across physical and digital mediums." |
| title: "News release typography and layout standards" | title: "News release typography and layout standards" |
| audience: vendor-public | audience: vendor-public |
| bcsc_class: current-fact | bcsc_class: current-fact |
| language: en | language: en |
| paired_with: news-release-standards.es.md | paired_with: news-release-standards.es.md |
| category: reference | category: reference |
| --- | --- |
| The platform enforces strict formatting rules for corporate news syndication to ensure absolute clarity and institutional authority. By adhering to ISO 24495-1 Plain Language principles, the system guarantees that [[disclosure-substrate|disclosures]] are accessible and professional across both digital and physical mediums. | The platform enforces strict formatting rules for corporate news syndication to ensure absolute clarity and institutional authority. By adhering to ISO 24495-1 Plain Language principles, the system guarantees that [[disclosure-substrate|disclosures]] are accessible and professional across both digital and physical mediums. |
| ## 1. Universal Layout Requirements | ## 1. Universal Layout Requirements |
| To maintain accessible visual tracking and institutional consistency, all news releases must adhere to these baseline rules: | To maintain accessible visual tracking and institutional consistency, all news releases must adhere to these baseline rules: |
| * **Left Alignment (Ragged Right):** All text must be left-aligned. Justified text is prohibited to prevent erratic spacing that disrupts reading flow. | * **Left Alignment (Ragged Right):** All text must be left-aligned. Justified text is prohibited to prevent erratic spacing that disrupts reading flow. |
| * **Case Sensitivity:** Title Case is mandatory for headlines and corporate entities. The use of all-caps blocks for names or locations is prohibited. | * **Case Sensitivity:** Title Case is mandatory for headlines and corporate entities. The use of all-caps blocks for names or locations is prohibited. |
| * **Geographic Precision:** Provinces and states must be spelled out in full (e.g., "British Columbia" instead of "BC"). This prevents international jurisdictional ambiguity. | * **Geographic Precision:** Provinces and states must be spelled out in full (e.g., "British Columbia" instead of "BC"). This prevents international jurisdictional ambiguity. |
| ## 2. Institutional Print Standards | ## 2. Institutional Print Standards |
| Physical news releases are intended to project institutional trust through a standardized "White Paper" aesthetic: | Physical news releases are intended to project institutional trust through a standardized "White Paper" aesthetic: |
| * **Header:** Bold, Title Case. | * **Header:** Bold, Title Case. |
| * **Dateline:** Separated from the narrative by an en-dash (–) or em-dash (—). | * **Dateline:** Separated from the narrative by an en-dash (–) or em-dash (—). |
| * **Mandatory Structure:** | * **Mandatory Structure:** |
| **For Immediate Release** | **For Immediate Release** |
| **[Headline in Title Case]** | **[Headline in Title Case]** |
| **Vancouver, British Columbia – [Date] –** [Narrative body copy...] | **Vancouver, British Columbia – [Date] –** [Narrative body copy...] |
| ## 3. Digital Presentation Standards | ## 3. Digital Presentation Standards |
| Web-based releases use specific semantic tags and separators to ensure high-density readability: | Web-based releases use specific semantic tags and separators to ensure high-density readability: |
| * **Semantic Hierarchy:** Use H2 for the release category (e.g., "Operational Update") and H1 for the headline. | * **Semantic Hierarchy:** Use H2 for the release category (e.g., "Operational Update") and H1 for the headline. |
| * **Metadata Pipe:** Use a pipe symbol (|) to separate dateline elements on a dedicated metadata line. | * **Metadata Pipe:** Use a pipe symbol (|) to separate dateline elements on a dedicated metadata line. |
| * **Structure:** | * **Structure:** |
| **[Corporate Entity] — [Release Category]** | **[Corporate Entity] — [Release Category]** |
| **[Headline Title Case]** | **[Headline Title Case]** |
| **For immediate release | Vancouver, British Columbia | [Date]** | **For immediate release | Vancouver, British Columbia | [Date]** |
| These standards ensure that every platform disclosure maintains a consistent [[editorial-language-registers|voice of authority]], whether viewed on a high-DPI display or a physical printed page. | These standards ensure that every platform disclosure maintains a consistent [[editorial-language-registers|voice of authority]], whether viewed on a high-DPI display or a physical printed page. |
| ## See also | ## See also |
| - [[brand-typography]] | - [[brand-typography]] |
| - [[brand-family-swatch]] | - [[brand-family-swatch]] |