Versioned blocks prototyping

[thibaudcolas]

Problem statement

Part of GSoC project - versioning friction

Proposed solution

Prototype those two options in one PR:

• VersionNoteBlock
  • Option 1: new specific block type specifically for this, with two fields:
    • Version number (select dropdown)
      • Type of change (added/changed/removed)
      • Content (rich text)
    • Option 2: new generic block type with support for versioning
      • Same fields but using block settings / BlockGroup
  • wagtail_version field for images
    • Interesting to do this to help with content management but want to find a way that doesn’t require complex integration
    • Next step: Thibaud refinement requirement for image versioning

Alternative solutions

No response

Additional context

No response

Working on this

Assigning to @Raghaddahi

[thibaudcolas]

Notes from #449:

• UI / design: keep the smaller more subtle style, with inline text. The "alert block" style is too distracting. Designing for 4-5 "version added" block highlights per page.
• Backend: make all new block fields optional. So you can more easily toggle a block to have or not have a version highlight
• Report on blocks usage (see StreamField block type usage report). "Which pages have versioned blocks that I should consider updating / removing"

Nice to have / future:

• UI filter to hide content when wanting to look at docs for an older release
• Content design: we need more guidance on how and when to create "version changed" highlights, and how and when to remove them
• Warning message to reduce the risk of people looking at very outdated docs / comparing "latest" docs for a very old version