Related to #102

This should prevent additional use of the following characters:

• “
• ”
• ‘
• ’

These will be converted to either " or ' as appropriate.

This migrates the https://docs.moodle.org/dev/Moodle_and_PHP page to devdocs/general/development/php and, given php80 support has been officially announced for 3.11 and 4.0, amend the release notes of those versions to tell so.

Then, register it as migrated page.

And finally, fix all the links to the old page (yarn mdfix-all).

Let's see if everything is in place (yarn build said ok), yay!

Ciao :-)

What do we need to do?

We're currently trying to acquire https://moodle.dev, which is currently squatted. This may take some time.

In the mean time, it would be good to have some more identity that github.io. I have a few suggestions, all of which are currently available for a reasonable cost:

• learnmoodle.dev
• learnmoodle.io
• moodledev.io
• moodledev.info
• moodle.sh
• moodle.how
• moodle.fyi
• moodledev.how
• moodledev.fyi
• moodle.wiki

Any thoughts?

I've been skimming through the new dev docs and I like them a lot. I noticed that the typography is used differently and it would be maybe a good thing to use the ’ or ' consistently. But I'm maybe too picky.

What is the URL of the page where you experience the error?

All

What is the issue with this page?

I am trying to report an issue with the system, but it is insisting I input a specific page URL, and then say what is wrong on that page. This just gets in the way.

Are you able to provide a patch for this?

No (Default)

In the future, perhaps it would be better to just note the planned release date when drafting the new release notes for the next minors. People should be able to determine the actual release status of the version from the indicated release date, right?

As requested in #298.

This issue introduces a new React component:

<ReleaseNoteIntro releaseName="4.0.2" />

This will display the:

• release date
• link to the tracker

I've also updated the page description for the meta tag because the import statement and React tags mess with it.

What is the URL of the page where you experience the error?

All

What is the issue with this page?

What is the poitn of the link to https://github.com/moodle/moodle at the top of every page?

Combine that with the fact that is is non-obvious how to edit the current docs page (unlike on the old wiki), I suggest movign the 'Edit this page' link from the bottom to this slot.

(Discusssion just now in dev chat confirms that several people haev found that link in its current place.)

Are you able to provide a patch for this?

No response

Migrated from: https://docs.moodle.org/dev/Custom_Moodle_Apps https://docs.moodle.org/dev/Moodle_App_Accessibility https://docs.moodle.org/dev/Moodle_App_Translation https://docs.moodle.org/dev/Moodle_App_Development_Process https://docs.moodle.org/dev/Moodle_App_Docker_Images https://docs.moodle.org/dev/Moodle_App_Release_Process https://docs.moodle.org/dev/Moodle_App_Remote_Themes_Upgrade_Guide https://docs.moodle.org/dev/Debugging_network_requests_in_the_Moodle_App https://docs.moodle.org/dev/Setting_up_your_development_environment_for_the_Moodle_App https://docs.moodle.org/dev/Moodle_App_Overview https://docs.moodle.org/dev/Using_the_Moodle_App_in_a_browser https://docs.moodle.org/dev/Acceptance_testing_for_the_Moodle_App https://docs.moodle.org/dev/Unit_testing_for_the_Moodle_App https://docs.moodle.org/dev/Moodle_App_Deep_Linking https://docs.moodle.org/dev/Moodle_App_Scripts:_gulp_push https://docs.moodle.org/dev/Sending_custom_Push_Notifications_to_the_Moodle_App

I've started migrating Testing pages, like https://docs.moodle.org/dev/Testing and https://docs.moodle.org/dev/Testing_of_integrated_issues.

While working on this patch, I've also updated the content of these pages:

• I've removed references to Wednesday (as testing day) in the Testing integrated issues, because we're not following this approach anymore.
• I've added a reference and link to Behat on the Testing page.

QUESTION 1: Can a page have no sidebar assigned? I can put the "Testing integrated issues" into the "Testing" section, but that's something we might face on other pages. How should we deal with them?

QUESTION 2: Apart from that, how many category levels we'll support/have?

We should work with Jess Gramp (@jgramp) and Rajneel to work out how best to link from the Developer resources to the development courses in the Moodle Academy.

From a User Experience perspective it would be good to have:

• [ ] A navbar element
• [ ] A landing page explaining that courses are available and linking to a landing page on the Academy

This change includes:

• a new libraries tool
• a command on the tool (fetch) which will parse the thirdpartylibs.xml files located in the .moodle directory and then generate a libraries.json file from this
• a command on the tool (generate) which will take the libraries.json file and a legacy-libraries.json file, and then generate a static markdown file
• a GitHub action to run these commands once per week

Fixes #93

This PR should be merged once https://tracker.moodle.org/browse/MDL-76691 will be integrated (this is the issue to upgrade both H5P libraries, core and editor) :-)

What do we need to do?

Now that the docs folder is versioned, @timhunt has suggested in the "Moodle Developer Resources" room if it's possible to automate the copy of migrated pages between branches.

What do we need to do?

A suggestion from Eloy re version dropdown selector:

Does the drop down need some label? Maybe not, but right now it looks like (to me, this is a 100% subjective feeling) it's floating in the middle of nowhere.