Problem/Motivation

The accessibility tools recipe is pinned at 2.2, which is functionally end-of-life.

Version 3.x has now reached RC1 and will tag a full release in a couple days. It's a better out of the box experience for any non-english site -- v2 was only ever translated into German; v3 ships with 16 languages. There are also a lot more tests.

Proposed resolution

Bump the composer requirement to ^3.0.

User interface changes

Tips have been rewritten to hopefully be a bit clearer, CSV exports have moved to a submodule, the dashboard Views allow for filters against live node data, and the optional CSA submodule has various features for developers and content governance.

Configuration changes

There should not be any needed, but we should keep an eye on progress in Canvas and the Admin theme.

Issue fork drupal_cms-3586147

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

  • 2.x Comparecompare
  • 2.1.x Comparecompare
About issue forks

Comments

itmaybejj created an issue. See original summary.

phenaproxima’s picture

phenaproxima
he/him
Primary language English
Location Massachusetts
commented
Status: Active » Postponed

This has to be postponed until editoria11y is stable, not RC. For a few (very good) release management reasons, Drupal CMS cannot include non-stable dependencies.

But if Editoria11y tags a stable 3.0 release and the product lead approves, this should be fine.

itmaybejj’s picture

itmaybejj commented

That makes perfect sense. I'll be tagging a stable release later this week.

As someone new to CMS merge requests...which branch(es) should I be proposing changes to in this fork? The View yml needs a rewrite too.

...or should I just leave that commit link there for people who know what they are doing and back away slowly?

phenaproxima’s picture

phenaproxima
he/him
Primary language English
Location Massachusetts
commented

Post your MR against the 2.x branch. :)