Some of our pages on moodle.org have been developed in a way that doesn't allow non-developers to update the content. Long term this is going to cause us problems, so we are going to re-develop these as editable pages using Moodle blocks and css to apply the backgrounds.

We will stick as closely as possible to the original designs.

The pages on moodle.org that are not editable are:

• https://moodle.org/ux
• https://moodle.org/uxresearchreports
• https://moodle.org/experiencelab 
• https://moodle.org/productvision
• https://moodle.org/paglmscommunity

rajneel.totaram@moodle.com has already gone through this conversion process for Moodle.Academy's homepage and I believe aya.saad was involved in the development of the https://moodle.org/getinvolved page (which is editable), so we have some knowledge on how to do this already.

alvaro.perezblanco@moodle.com may be able to assist with the CSS side of things to apply the backgrounds and other styling.

Development Documentation:

https://moodlesuccess.atlassian.net/wiki/spaces/CS/pages/2759983186/Community+editable+pages+using+HTML+blocks

 Note on Development and Deployment to Staging and Production

To ensure a seamless update for users, the deployment should be carried out in two phases:

1. Phase 1: Add the editing functionality for internal pages (e.g., theme/moodleorg/uxresearchreports.php). This will allow us to replicate the content and test it in each environment without affecting the current links.

1. Phase 2: Link the internal pages containing the updated content to their corresponding public URLs (e.g., moodle.org/uxresearchreports). During this phase, we can also remove the old pages that will no longer be in use

Enginx modifications needed:
https://git.in.moodle.com/ict/community-docker/-/commit/ad1413e0eb66e196ed926466013b8b068b062672

 Note After publish to Production

The clean necessary process:

1. Remove layouts in theme config.php file
2. Remove the old layout files.
3. Remove main files (experiencelab.php, ...)
4. Filter SCSS