Skip to content
Artwork for Talking Drupal
Talking Drupal · Thursday · 1 hr 7 min

Talking Drupal #573 - Off The Cuff #13

Today we are talking about Drupalcon Rotterdam, Canvas and evaluating modules. We'll also cover Revision Graph as our module of the week. For show notes visit: https://www.talkingDrupal.com/573 Topics DrupalCon Rotterdam recap AI summits and training FrankenPHP app servers Driesnote highlights Advocacy and WordPress Rosetta Sprint and MCP Canvas multilingual and headless 3Frameworks And Voiceover Canvas And SDCs Headless And Signage Drupal 12 Beta Testing Rector And Deprecations PHP 8.5 Requirements Rethinking Module Evaluation AI And Commit Scale Module Discoverability 0Distributions Versus Recipes Resources Wordpal Core metrics Hosts Nic Laflin - nLighteneddevelopment.com nicxvan Martin Anderson-Clutz - mandclu.com mandclu Tim Sharp - tea-sharp MOTW Correspondent Martin Anderson-Clutz - mandclu.com mandclu Brief description: Have you ever wanted to see a node's revision history drawn like a Git graph, with each translation as its own branch? There's a module for that. Module name/project name: Revision Graph Brief history How old: created in Sep 2019 by Shibin Das (D34dMan) of Factorial Versions available: 4.0.0, which works with Drupal 11 and 12, and 3.1.1 for Drupal 10 and 11 Maintainership Actively maintained, 4.0.0 landed in mid-August after two alphas the same week Security coverage Test coverage Documentation: a solid README plus in-depth technical and revision-model docs in the repo Number of open issues: zero open issues Usage stats: 242 sites Module features and usage With the module installed, every node gets a Revision Graph tab, right next to the core Revisions tab One row per revision, one lane per language, so you can see when a translation branched off and how it's evolved since Each dot tells you two things: a solid ring means that revision was live at some point, a dashed ring means it's a draft that never was, and a filled center means it's what that language is serving right now It works with Content Moderation if you have it, showing your workflow states as text badges with whatever names your site uses, and adapts cleanly when you don't Reverts, and edits made from the published version while a draft is pending, show up as forks instead of a straight line Under the hood: Drupal doesn't actually store which revision a new one was derived from, so the module adds a small base field that records it at presave Older revisions don't get backfilled, on purpose, since reconstructing that would mean guessing. Those edges are inferred, and the graph draws inferred edges differently from recorded ones, so it never implies more precision than it has So on an existing site, make sure you run drush updb after enabling it Ships a distinct color for all 95 language codes Drupal knows, so it looks good out of the box, but you can override a lane's color or the fallback palette in config The graph loads in pages as you scroll, so long histories render quickly, and it's keyboard navigable, ARIA-labelled, and works in forced-colors mode Great for editorial teams on multilingual sites, and handy for compliance or auditing when you need to answer "what was live, and when?" Caveats: it's nodes only, and for obvious reasons a user will need the "view all revisions" permission to see the graph

0:00-1:07:32

transcript

No transcript — this publisher did not publish one.

show notes

Today we are talking about Drupalcon Rotterdam, Canvas and evaluating modules. We'll also cover Revision Graph as our module of the week.

For show notes visit: https://www.talkingDrupal.com/573

Topics
  • DrupalCon Rotterdam recap
  • AI summits and training
  • FrankenPHP app servers
  • Driesnote highlights
  • Advocacy and WordPress
  • Rosetta Sprint and MCP
  • Canvas multilingual and headless
  • 3Frameworks And Voiceover
  • Canvas And SDCs
  • Headless And Signage
  • Drupal 12 Beta Testing
  • Rector And Deprecations
  • PHP 8.5 Requirements
  • Rethinking Module Evaluation
  • AI And Commit Scale
  • Module Discoverability
  • 0Distributions Versus Recipes
Resources Hosts

Nic Laflin - nLighteneddevelopment.com nicxvan Martin Anderson-Clutz - mandclu.com mandclu Tim Sharp - tea-sharp

MOTW Correspondent

Martin Anderson-Clutz - mandclu.com mandclu

  • Brief description:
    • Have you ever wanted to see a node's revision history drawn like a Git graph, with each translation as its own branch? There's a module for that.
  • Module name/project name:
  • Brief history
    • How old: created in Sep 2019 by Shibin Das (D34dMan) of Factorial
    • Versions available: 4.0.0, which works with Drupal 11 and 12, and 3.1.1 for Drupal 10 and 11
  • Maintainership
    • Actively maintained, 4.0.0 landed in mid-August after two alphas the same week
    • Security coverage
    • Test coverage
    • Documentation: a solid README plus in-depth technical and revision-model docs in the repo
    • Number of open issues: zero open issues
  • Usage stats:
    • 242 sites
  • Module features and usage
    • With the module installed, every node gets a Revision Graph tab, right next to the core Revisions tab
    • One row per revision, one lane per language, so you can see when a translation branched off and how it's evolved since
    • Each dot tells you two things: a solid ring means that revision was live at some point, a dashed ring means it's a draft that never was, and a filled center means it's what that language is serving right now
    • It works with Content Moderation if you have it, showing your workflow states as text badges with whatever names your site uses, and adapts cleanly when you don't
    • Reverts, and edits made from the published version while a draft is pending, show up as forks instead of a straight line
    • Under the hood: Drupal doesn't actually store which revision a new one was derived from, so the module adds a small base field that records it at presave
    • Older revisions don't get backfilled, on purpose, since reconstructing that would mean guessing. Those edges are inferred, and the graph draws inferred edges differently from recorded ones, so it never implies more precision than it has
    • So on an existing site, make sure you run drush updb after enabling it
    • Ships a distinct color for all 95 language codes Drupal knows, so it looks good out of the box, but you can override a lane's color or the fallback palette in config
    • The graph loads in pages as you scroll, so long histories render quickly, and it's keyboard navigable, ARIA-labelled, and works in forced-colors mode
    • Great for editorial teams on multilingual sites, and handy for compliance or auditing when you need to answer "what was live, and when?"
    • Caveats: it's nodes only, and for obvious reasons a user will need the "view all revisions" permission to see the graph

links9

more episodes

All episodes