Update frontpage and add WordPress information

docs/docs/1-Getting Started/1-a-landing.md

@@ -6,22 +6,57 @@ slug: /
 
 Welcome to **drupal.docs.cern.ch**, your one-stop Drupal resource at CERN.
 
+:::info WordPress is coming!
+![The Webservices Portal frontpage.](/assets/img/wordpress_screenshot.png)
+
+**CERN is migrating from Drupal to WordPress**, leveraging a modern ecosystem offering improved accessibility, responsiveness, and workflow efficiency. The decision to adopt WordPress as CERN's future content management system follows an extensive review of both Drupal and several other alternative systems: a process requested and overseen by the Web Governance Board initially motivated by the increasing complexity and maintenance demands of supporting the status quo. You can find more information about WordPress and the process leading to its adoption [here](https://wordpress.docs.cern.ch/background/background/).
+
+WordPress presents a unique opportunity to modernise our extensive digital presence, leveraging the rich WordPress ecosystem to address the many shortcomings and difficulties inherent to Drupal. With the Web Governance Board's endorsement, WordPress will be the foundation for CERN's web presence in the years to come.
+
+**WordPress is officially coming to CERN in 2025.**
+
+<small>
+
+See [https://wordpress.docs.cern.ch/](https://wordpress.docs.cern.ch/) for more information and [https://governance.web.cern.ch/](https://governance.web.cern.ch/) for information about Web Governance at CERN.
+</small>
+:::
+
 ## News
 
-### September 2024: Update to timeline and plans, WordPress Lite and much more
+### March 2025: The Path to WordPress
 
-Please check the dedicated section to the [Roadmap to WordPress](/roadmap-wordpress) to see the updates to the plans and timelines.
+WordPress is coming to CERN with a scheduled production release in May 2025.
+The official release of WordPress at CERN also marks the beginning of the end of Drupal as an official service at CERN.
+Starting July, automated migrations to WordPress of conformant Drupal websites will begin.
 
-We'll go over these details in the [Community Meeting](https://indico.cern.ch/event/1457632/) of 26th September via zoom. 
+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 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 via [ticket](https://cern.service-now.com/service-portal?id=service_element&name=Drupal-Service).
+Migrations will be automated and done in coordination with website owners. A preview will be created on WordPress and you will be given time to validate it.
+Until the migration is complete, your Drupal website will continue to remain operational and will receive all incoming traffic.
+Once your WordPress websites becomes your primary website, the Drupal website will stick around behind CERN SSO for a period of time before eventually being decommisioned.
 
-### April 2024: The road from Drupal to WordPress 🎉
+More information can be found at https://wordpress.docs.cern.ch/.
 
-We write this news to share that the presentation at the Enlarged Directorate, on March 5th, on the topic of _“Web presence, Governance and Drupal to WordPress migration”_ was very well received.
+<details>
+<summary><h3>September 2024: Update to timeline and plans, WordPress Lite and much more</h3></summary>
+
+Please check the dedicated section to the [Roadmap to WordPress](/roadmap-wordpress) to see the updates to the plans and timelines.
+
+We'll go over these details in the [Community Meeting](https://indico.cern.ch/event/1457632/) of 26th September via Zoom.
+</details>
+
+<details>
+<summary><h3>April 2024: The road from Drupal to WordPress 🎉</h3></summary>
+
+We write this news to share that the presentation at the Enlarged Directorate, on March 5th, on the topic of _"Web presence, Governance and Drupal to WordPress migration"_ was very well received.
 **A decision to move from Drupal to WordPress, followed by decommissioning Drupal at CERN, has been approved.** 
 Given the additional resources required for this project, in order to develop the infrastructure in-house and support the migration for all CERN Websites, new resources will be requested (Q3/Q4 onwards).
 However, work is already starting on the preparations of the new infrastructure and the subsequent migration to WordPress.
-A strategy for customised websites is still being defined. 
+A strategy for customised websites is still being defined.
 It will be shared as soon as possible.
 If you have feedback or concerns at this stage, please contact your Web Representative directly.
 
@@ -45,48 +80,41 @@ Work is ongoing to review the custom module utilisation and support the most use
 However, preliminary analysis shows a wide-ranging distribution of custom module usage (more than 300 unique modules over 200 customised websites).
 ** Therefore, we recommended all Drupal users to assess and uninstall non-essential custom modules from their websites, in order to prepare for the upcoming move to WordPress.**
 
-- Given that the current offering on WordPress comes with limited support, we recommend experienced Drupal users to keep using Drupal, if there’s a need for a new website.
+- Given that the current offering on WordPress comes with limited support, we recommend experienced Drupal users to keep using Drupal, if there's a need for a new website.
 
 - The preliminary plan is to freeze the Drupal infrastructure as much as possible, in order to save resources for the upcoming migration (both for users and ourselves).
 
 Thank you for all the input and support!
+</details>
 
-## Roadmap
-
-### Drupal Infrastructure 
-The Drupal service follows as close as possible the Drupal release cycle and support at most two versions at the same time.
-Once a Drupal release becomes end-of-life (EOL), it will no longer be supported at CERN as well.
-Accordingly, users must ensure their website is running the supported Drupal version to receive centralised support.
-
-All updates and upgrades are communicated to the users via the [Notifications service](cern.ch/n-91d) and/or via a [Service Status Board](https://cern.service-now.com/service-portal?id=service_status_board) announcement. 
-
-**The only supported version currently is Drupal 10.** Drupal 10 is expected to be supported at CERN until February of 2026. Drupal 10 is expected to be the last release offered at CERN.
+## Service and Support
 
-Drupal 9 is EOL since November 2023.
+Drupal is a service centrally provided by the IT department in close collaboration with the Web Team.
 
-### Drupal to WordPress
+:::warning maintenance mode
+No expertise or support is provided regarding website development. 
+**Support is limited to the infrastructure maintenance or website malfunction.**
+It is thus strongly recommended to not exceed what is offered centrally in the CERN Drupal Distribution as this introcue additional complexity and maintenance which would be the responsibility of the website owner(s).
 
-See the updated [roadmap](/roadmap).
+In order to **prepare for WordPress**, users are recommended to uninstall non-essential custom modules from their websites.
+:::
 
-** All Drupal users are recommended to uninstall non-essential custom modules from their websites, in order to prepare for the upcoming move to WordPress.**
+The Drupal service follows as close as possible the Drupal release cycle and support at most two versions at the same time.
+Once a Drupal release becomes end-of-life (EOL), it will no longer be supported at CERN as well.
+Accordingly, users must ensure their website is running the supported Drupal version to receive centralised support.
+All updates and upgrades are communicated to the users via the [Notifications service](cern.ch/n-91d) and / or via a [Service Status Board](https://cern.service-now.com/service-portal?id=service_status_board) announcement.
 
-Due to this change, the Drupal infrastructure is in maintenance mode, in order to save resources for the upcoming migration (both for users and ourselves), therefore no active development is planned.
+**The only supported Drupal version at CERN is Drupal 10.**
 
-## Service level
+Drupal 10 is expected to be supported at CERN until February of 2026. Drupal 10 is expected to be the last release offered at CERN.
+Drupal 9 has been EOL since November 2023.
+Security patches will continue to be applied throughout the lifetime of Drupal 10 in accordance with best practices and Computer Security recommendations.
 
-Drupal is a service centrally provided by the IT department in close collaboration with the Web Team (IR-ECO).
+### Your Responsibility
 
-:::info Website development
-No expertise or support is provided regarding website development. 
-**Support is limited to the infrastructure maintenance or website malfunction.**
-It is thus strongly recommended to not exceed what is offered centrally in the CERN Drupal Distribution as this introcue additional complexity and maintenance which would be the responsibility of the website owner(s).
-For guidance regarding Drupal development or theming, please consider reaching other community experts via the means listed under [#Support](#support).
-:::
-
-### User responsibility
 A Drupal website is by default publicly accessible.
-Accordingly, as with any IT offering, it must adhere to CERN's rules, regulations and guidelines on subjects such as design, accessibility, and security. 
-Additionally, in order to ensure CERN's Digital Identity, any website must adhere to the CERN Web Presence Guidelines. 
+Accordingly, as with any IT offering, it must adhere to CERN's rules, regulations and guidelines on subjects such as design, accessibility, and security.
+Additionally, in order to ensure CERN's Digital Identity, any website must adhere to the CERN Web Presence Guidelines.
 
 In this way, all users must adhere to all guidelines indicated thought out the documentation or risk having their website blocked without prior notice. Additionally, make sure you follow all the guidelines under [Data Privacy](#data-privacy).
 This is particularly important if additional, custom modules are installed which collect or otherwise aggregate user data.
@@ -104,7 +132,8 @@ If you find yourself in this situation, please do not hesitate reaching out for
 
 :::warning Customisation disclaimer
 Please note that installing and using custom modules requires:
-- (a) continuous maintenance; 
+
+- (a) continuous maintenance;
 - (b) continuous attention to updates, security patches, and new feature releases;
 - (c) ensuring compatibility with the supported Drupal version; and
 - (d) manual work for the webmaster who will have to carefully check that everything works as expected on their side everytime any central upgrade is available.
@@ -120,32 +149,15 @@ If you require a set-and-forget solution, please do not exceed what is offered i
 By using this service with custom modules, you agree to take active part in the upgrades process, allowing us to follow the upstream release cycles in due time.
 :::
 
-In the event that the modules provided via the CERN Drupal Distribution are not sufficient for your needs, we recommend you either:
-- post on the CERN Drupal Community Forums/Mattermost to see whether others have already achieved what you are looking for; 
-- submit a request to the Drupal Team to evaluate whether the feature(s) you require can be accommodated by adding a new module to the CERN Drupal Distribution, benefiting all CERN websites.
-
-## Data privacy
+## Data Privacy
 
 Please refer to the information in the CERN's Data Privacy Office website and make sure that you read and agree with the [Drupal Service Data Privacy Police](https://cern.service-now.com/service-portal?id=privacy_policy&se=Drupal-Service&notice=drupal-service) before using the service. 
 
 ## Support
 
-We strive to make these docs your go-to place for anything Drupal.
-We are continuously expanding the website with guides and tutorials for most use-cases.
-
-There are various ways to get in touch, depending on your needs:
+Since the Drupal Service at CERN has officially entered maintenance mode, support is limited to maintenance tasks.
+This documentation reamins your go-to place for anything Drupal, and we remain available via the following channels in case of any issues:
 
 - Mattermost channel [Drupal Infra](https://mattermost.web.cern.ch/it-dep/channels/drupal) is a place for informal, technical exchange with the community and with the service managers.
 - [Drupal Community Forum](https://drupal-community.web.cern.ch) is a place for informal, technical exchange with advanced users from the community.
 - For any questions or concerns regarding the service or your website, please open a [ticket](https://cern.service-now.com/service-portal?id=service_element&name=Drupal-Service).
-
-
-## How can I help?
-
-This documentation is open and accessible by everyone with a CERN account.
-If you spot an error, a typo, or would like to propose changes, please click _Edit this page_ at the bottom of any page.
-Clicking this link takes you to the below screen directly on our Gitlab page (https://gitlab.cern.ch/drupal/paas/drupal-documentation/).
-On here, you can submit your proposed changes.
-We will then review your submissions and update the documentation accordingly.
-
-We intend for this documentation to be living and breathing.

docs/docs/5-Development/Fetching-custom-modules.md → docs/docs/5-Development/6-3-fetching-custom-modules.md

+---
+slug: /development/fetching-custom-modules
+---
+
+# [LEGACY] Fetching Custom Modules
+
+In order to fetch and see which custom modules you have installed on your website, please:
+
 1. Access the Website via Cyberduck (WebDAV)
-- Use Cyberduck to connect to WebDAV.
+
+- Use Cyberduck to connect to WebDAV
 - Guide on how to connect using Cyberduck: [Cyberduck - WebDAV](https://drupal.docs.cern.ch/development/webdav-client)
 - Guide for retrieving the WebDAV password: [WebDAV Password Retrieval](https://drupal.docs.cern.ch/development/access-via-webdav)
 
-2. Navigating to Custom Modules
-- Once connected via WebDAV, navigate to the modules folder.
-- In the modules folder, look for the custom modules sub-folder. 
-- If no sub-folder exists, custom modules are within the main modules folder.
+2. Navigate to `Custom Modules`
+
+- Once connected via WebDAV, navigate to the `modules` folder
+- In the modules folder, look for the `custom` modules sub-folder
+- If no sub-folder exists, custom modules are within the main modules folder
 
 ![Modules folder](/assets/img/5-development/Modules_folder-cyberduck.png)
 
 ![Custom module](/assets/img/5-development/Custom-module.png)
 
-3. Removing Custom Modules
-- You can remove the custom directly from Cyberduck by deleting the desired module.
-
-Summary
-To fetch custom modules, connect to the website via Cyberduck using WebDAV. Navigate to the modules folder to locate custom modules, then remove them directly through Cyberduck.
-

docs/docusaurus.config.js

@@ -16,8 +16,8 @@ module.exports = {
     announcementBar: {
         id: 'customisation_block',
         content:
-          'As of April 10th 2024, installing custom modules in **new** websites is not supported. All documentation in reference to this is marked as legacy.',
-        backgroundColor: '#f3a07a',
+          'WordPress is coming to CERN in May 2025! <a href="https://wordpress.docs.cern.ch/">Click here for more information!</a>',
+        backgroundColor: '#0073aa',
         textColor: '#fff',
         isCloseable: false,
       },
@@ -94,8 +94,7 @@ module.exports = {
           sidebarPath: require.resolve("./sidebars.js"),
           editUrl: ({ docPath }) =>
             `https://gitlab.cern.ch/drupal/paas/drupal-documentation/edit/master/docs/docs/${docPath}`,
-          //path: 'docs',
-          routeBasePath: "/", // Serve the docs at the site's root
+          routeBasePath: "/",
           breadcrumbs: true,
           showLastUpdateAuthor: true,
           showLastUpdateTime: true,
@@ -108,21 +107,14 @@ module.exports = {
   ],
   // from https://github.com/easyops-cn/docusaurus-search-local
   themes: [
-    // ... Your other themes.
     [
       require.resolve("@easyops-cn/docusaurus-search-local"),
       {
-        // ... Your options.
         // `hashed` is recommended as long-term-cache of index file is possible.
         hashed: true,
         highlightSearchTermsOnTargetPage: true,
-	indexDocs: true, // Default is true, but let's force it
-	indexPages: true,
-
-        // For Docs using Chinese, The `language` is recommended to set to:
-        // ```
-        // language: ["en", "zh"],
-        // ```
+        indexDocs: true,
+        indexPages: true,
       },
     ],
   ],