From 808f2559fb8cc5bea2295052216a25a32af41b69 Mon Sep 17 00:00:00 2001 From: Joachim Valdemar Yde <joachim.valdemar.yde@cern.ch> Date: Tue, 25 Mar 2025 13:36:20 +0000 Subject: [PATCH] Apply 1 suggestion(s) to 1 file(s) Co-authored-by: Carina Antunes <carina.oliveira.antunes@cern.ch> --- docs/docs/1-Getting Started/1-a-landing.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/docs/1-Getting Started/1-a-landing.md b/docs/docs/1-Getting Started/1-a-landing.md index c527fd6..cabd74f 100644 --- a/docs/docs/1-Getting Started/1-a-landing.md +++ b/docs/docs/1-Getting Started/1-a-landing.md @@ -31,7 +31,7 @@ Starting July, automated migrations to WordPress of conformant Drupal websites w Customised Drupal websites are encouraged to strip away customisation in order to qualify for, and benefit from, the automated migration. Websites not immediately suited for automated migration will be contacted on a case-by-case basis, outlining the necessary steps for compliance. -This effort is led by the Web Team and will continue throughout the rest of the year before concluding in February 2026. +This is a joint effort led by the Web Team and the IT Drupal/WordPress Infrastructure team and will continue throughout the rest of the year before concluding in early 2026. This means that, as of today, if you have a Drupal website, you should prepare your Drupal website for automated migration by stripping away any customisation. If you are unsure how this is done, please get in touch. -- GitLab