Take nested-paragraph type to CMS Collab Cycle for review and next steps

[wesrowe]

Description

User story

AS A PO/PM I WANT CMS COllab Cycle to review the nested-para-with-header PoC SO THAT implementation will be reusable across multiple products as desired.

Engineering notes / background

Analytics considerations

Quality / testing notes

Acceptance criteria

• [x] Scheduled CMS Collab Cycle meeting - set for 6/1
• [x] Met
• [x] Ticketed next steps

[davidmpickett]

^^ @laflannery

[wesrowe]

Notes from collab cycle meeting (will edit live):

• "Level 1" is confusing, too similar to "h1". – MUST
• Validation timing – on save is MUST
• Extensibility – how decide on going down to 3rd level only? – CC to determine max depth
• Extension beyond LRTF – SHOULD avoid tech debt that would prevent iteration post-MVP
• DaveP: there used to be an intro paragraph at the start of the section
  • CT: removed for some reason
  • (Wes: can we have multiple top-level paras or just one?)
• What is CC design overview next step – how CMS team monitor design, how documented?
  • Mike: asks Blake, can we apply evolving CC requirements here? Blake to document steps we would prefer to follow, and are they followed or deferred

Next steps:

• Wes to schedule design follow-up: Blake, Jordan, Christia, DaveP, Laura, Mike
• Christia to collaborate with CMS engineers – how will we get the engineering feedback, from whom? How will we define "done" in terms of extensibility, tech debt (in all its vagueness)?