Types Planning

Prerequisites: Logical Breakdown

Objective

Define the project's content Types and identify which BlocTypes each Type can use. This planning structures content organization in the back-office.

What is a Type?

  1. Allowed BlocTypes: Which blocks can be added
  2. A route: Which controller/action will display the content
A Type is a page template that associates:

Type vs BlocType Difference

BlocType: Data structure (input fields) Type: Page template (BlocType combination + controller)

Types to Create

Type 1: Home

Usage: FR/EN home pages

Route: cms/home

  1. Hero (H1)
  2. Feature (H3)
  3. Cta
Allowed BlocTypes:

  1. Hero for main header with image and 2 CTAs
  2. Features to present functionalities in 3-column grid
  3. Cta for final conversion
Justification:

Article allowed: Checked

Type 2: Documentation

Usage: Technical documentation articles

Route: cms/documentation

  1. Hero (H1)
  2. Title (H2 - H4)
  3. Content
  4. Code
  5. Info
  6. Feature (H3)
  7. Cta
  8. Card
Allowed BlocTypes:

  1. Hero for page header
  2. Title to structure content (H2, H3, H4)
  3. Content for paragraphs
  4. Code for examples
  5. Info for alerts
  6. Optional Feature for highlights
  7. Cta for navigation
  8. Optional Card for insets
Justification:

Article allowed: Checked

Type 3: Contact

Usage: FR/EN contact pages

Route: cms/contact

  1. Hero (H1)
  2. Card
  3. Info
  4. Contact
Allowed BlocTypes:

  1. Hero for header
  2. Card for contact info in sidebar
  3. Info for potential alerts
  4. Contact to configure form
Justification:

Article allowed: Checked

Type 4: Redirect Language

Usage: Root node for language detection

Route: cms/redirect-language

Allowed BlocTypes: None

  1. This Type contains no content
  2. It automatically redirects to /fr or /en based on browser language
Justification:

Article allowed: Not checked

Type 5: Redirect First Composite

Usage: Container nodes (Guide, About)

Route: cms/redirect-first-composite

Allowed BlocTypes: None

  1. This Type contains no content
  2. It automatically redirects to first active Composite of Node
Justification:

Article allowed: Not checked

Allowed BlocTypes by Type

Type Home

  1. Hero
  2. Feature
  3. Cta

Type Documentation

  1. Hero
  2. Feature
  3. Title
  4. Content
  5. Code
  6. Info
  7. Cta
  8. Card

Type Contact

  1. Hero
  2. Card
  3. Info
  4. Contact

Type Redirect Language

No BlocType

Type Redirect First Composite

No BlocType

Restriction Logic

Types with Limited Content

  1. Voluntary limitation to keep homogeneous format
  2. No rich content to stay on presentation page
Home: Only Hero + Features + Cta

  1. Fixed structure: form + info sidebar
  2. No rich content as utility page
Contact: Only Hero + Cards + Info + Contact

Types with Rich Content

  1. Maximum flexibility to create varied technical content
  2. Code support, alerts, advanced formatting
Documentation: Almost all BlocTypes

Types without Content

  1. Purely technical, no editorial content
  2. Only automatic redirects
Redirect Language and Redirect First Composite: No BlocType

Validation

Before continuing, verify:

  1. Home (3 BlocTypes)
  2. Documentation (8 BlocTypes)
  3. Contact (4 BlocTypes)
  4. Redirect Language (0 BlocType)
  5. Redirect First Composite (0 BlocType)
Defined types:

Total: 5 Types

Complete matrix: Each Type has its allowed BlocTypes clearly identified