[docs] Create Developer quick start and Contribute pages

- Created /general/development/gettingstarted. It contains links to help
developers to start coding Moodle.
- Renamed Policies navbar to Coding. Moved Tools from navbar to new Coding
section too.
- Created /general/community/contribute page. It contains a few of the
ways developers can contribute Moodle and also a link to the FAQ in
moodle.com where other options are explained too.
- Removed old gettingstarted pages in docs, as they finally won't be
required there (they have been moved to general).

Author: sarjona

config/navbar.js

@@ -32,29 +32,24 @@ const navbar = {
     items: [
         {
             type: 'doc',
-            docId: 'gettingstarted/quickstart',
+            docId: 'apis',
             position: 'left',
             label: 'Guides',
         },
         {
-            to: '/general/community',
+            to: '/general/community/contribute',
             label: 'Community',
-            position: 'left'
-        },
-        {
-            to: '/general/development/process',
-            label: 'Process',
-            position: 'left'
+            position: 'left',
         },
         {
-            to: '/general/development/policies/codingstyle',
-            label: 'Policies',
-            position: 'left'
+            to: '/general/development/gettingstarted',
+            label: 'Coding',
+            position: 'left',
         },
         {
-            to: '/general/development/tools',
-            label: 'Tools',
-            position: 'left'
+            to: '/general/development/process',
+            label: 'Process',
+            position: 'left',
         },
 
         // Right.

data/migratedPages.yml

@@ -1225,6 +1225,9 @@ Security:Unauthorised_access:
 Sending_custom_Push_Notifications_to_the_Moodle_App:
 - filePath: "/docs/moodleapp/development/custom-push-notifications.md"
   slug: "/docs/moodleapp/development/custom-push-notifications"
+Setting_up_development_environment:
+- filePath: "general/development/gettingstarted.md"
+  slug: "general/development/gettingstarted"
 Setting_up_your_development_environment_for_the_Moodle_App:
 - filePath: "/docs/moodleapp/development/setup/index.md"
   slug: "/docs/moodleapp/development/setup"

docs/gettingstarted/quickstart.md

@@ -10,7 +10,7 @@ tags:
 
 In order to run tests that carry out automated functionality testing for the Moodle App, you can write [Acceptance tests](https://docs.moodle.org/dev/Acceptance_testing). This can be useful if you want to test plugins that are compatible with the app, or you're contributing to the app core. Behat tests for the app work the same way as tests for Moodle core, but they are not run as part of a normal Behat execution and there are some differences that we'll go through in this page.
 
-A key point is that these tests are run using the Moodle Behat infrastructure, and don't depend only on the app codebase. Therefore, you will need a Moodle development setup as described in [Setting up development environment](https://docs.moodle.org/dev/Setting_up_development_environment).
+A key point is that these tests are run using the Moodle Behat infrastructure, and don't depend only on the app codebase. Therefore, you will need a Moodle development setup as described in [Setting up development environment](/general/development/gettingstarted).
 
 The main advantages of this approach are:
 
@@ -30,7 +30,7 @@ Nevertheless, if you still have to run the projects in your local machine, you c
 
 ### Configuring the Moodle site
 
-You can learn how to run a Moodle site locally in [Setting up development environment](https://docs.moodle.org/dev/Setting_up_development_environment).
+You can learn how to run a Moodle site locally in [Setting up development environment](/general/development/gettingstarted).
 
 Remember to install the [local_moodlemobileapp](https://github.com/moodlehq/moodle-local_moodlemobileapp/) plugin with the same version that you're using for the mobile app.
 

docs/moodleapp/development/testing/acceptance-testing.md

@@ -0,0 +1,28 @@
+---
+title: Contributing
+tags:
+  - Core development
+  - Processes
+  - Community
+---
+
+If you want to contribute to Moodle, you can start looking at the following:
+
+- **Found a bug?** [Report an issue](/general/development/tracker#reporting-an-issue) in our bug tracker.
+- **Want to learn and extend your Moodle development skills**? Sign up to free self-paced courses in our [Moodle Academy Developer Learning Pathway](https://learn.moodle.org/).
+- **Ready to help coding**? Check the [getting started](/general/development/gettingstarted) page.
+- **Share your plugins** in the [Plugins directory](https://moodle.org/plugins).
+- **Adopt an existing plugin**. Look at the [list of plugins seeking a new maintainer](https://moodle.org/plugins/browse.php?list=set&id=61) and read the [Plugins adoption programme](https://moodle.org/mod/forum/discuss.php?d=260354).
+- **Assist with the translation** of Moodle. See [Translation](/general/development/process/translation) page.
+- **Get involved in the developer resources**, [contributing](/general/documentation/contributing) for fixing typos and errors, migrating pages, expanding the content, etc.
+
+:::tip Searching for other ways to contribute?
+
+You'll find them in the [How do I contribute to Moodle?](https://moodle.com/faq/how-do-i-contribute-to-moodle/) page.
+
+:::
+
+### See also
+
+- [Releases](/general/releases) - versions of Moodle that have already been released
+- [Process](/general/development/process)

general/community/contribute.md

@@ -0,0 +1,79 @@
+---
+title: Getting started
+tags:
+  - Core development
+  - Processes
+---
+
+:::info Ready to code?
+
+- [Set up your development environment](#a-quick-start-to-moodle-development)
+- See the [list of relatively easy Moodle bugs](https://tracker.moodle.org/issues/?jql=project%20%3D%20MDL%20AND%20type%20in%20(bug)%20AND%20status%20%3D%20open%20AND%20Difficulty%20%3D%20Easy%20AND%20labels%20not%20in%20(patch)%20ORDER%20BY%20created%20DESC)
+- [Prepare a patch](https://docs.moodle.org/dev/Git_for_developers#Preparing_a_patch)
+- Read the [Coding style](/general/development/policies/codingstyle) policy
+- Send your patch to [peer review](/general/development/process/peer-review) and learn more about the [Moodle processes](/general/development/process).
+- Create your custom plugins looking at the information in the [Plugin contribution](https://docs.moodle.org/dev/Plugin_contribution) page.
+
+:::
+
+<!-- cspell:ignore adminer -->
+
+## A quick start to Moodle development
+
+1. Create an account on [Moodle.org](https://moodle.org/). You will need this to access the [Moodle General Developer forum](https://moodle.org/mod/forum/view.php?f=33) and download [Moodle plugins](https://moodle.org/plugins). You can also sign up to free self-paced courses in our [Moodle Academy Developer Learning Pathway](https://learn.moodle.org/)
+1. Create an account on [GitHub](https://github.com/) and [install Git on your computer](https://docs.moodle.org/dev/Git_for_developers). This is the source code version control repository tool of choice for Moodle development.
+1. [Install Moodle on your machine](https://docs.moodle.org/en/Installing_Moodle) or use a container environment like [moodle-docker](https://github.com/moodlehq/moodle-docker). You can also use [Moodle Development Kit (MDK)](/general/development/tools/mdk).
+
+  :::tip
+
+  We highly recommend that you use a database administration tool such as [adminer](https://www.adminer.org/) to help you manage your development databases.
+
+  :::
+
+1. Set-up Moodle for development:
+
+- Enable the [Moodle Debugger](https://docs.moodle.org/en/Debugging).
+
+  :::tip
+
+  When developing in Moodle, it's recommended to turn debugging on. Only turn it off for demonstration purposes as it does have a considerable impact on the performance of your Moodle website.
+
+  :::
+
+  :::danger Attention
+
+  Always resolve all errors and warnings that show up with **Moodle debugging turned on**. Errors and warnings imply that something isn't working as it is supposed to which means your code isn't doing what you intended it to, or may be fragile and could break in the future.
+
+  :::
+
+- Install the [Moodle PHP CodeSniffer](/general/development/tools/phpcs). This will be used to test your plugin for conformance with Moodle coding standards. Use this to develop good coding skills.
+- Install the Moodle [PHPdoc check plugin](https://moodle.org/plugins/local_moodlecheck). This will be used to test your source code documentation. This will also help improve your coding skills.
+
+  :::info Advanced
+
+  You can use Xdebug to enable step-by-step debugging in PHP. Integrations are built into many popular editors.
+  [Learn more](https://docs.moodle.org/dev/Profiling_PHP#Xdebug)
+
+  :::
+
+And finally remember these wise words from [Michael Milette](https://moodle.org/user/view.php?id=1615960&course=5) in the [General developer forum](https://moodle.org/mod/forum/discuss.php?d=355789):
+
+> Learning how to code in Moodle involves a lot of learning by example and reading other people's source code including Moodle core code. If you have a particular type of plugin in mind that you would like to create, it's recommended that you start by finding a plugin which provides similar functionality and use the process outlined above to clone it. Then customize it to suit your needs. You can even do this with 3rd party plugins found on the [plugins directory](https://moodle.org/plugins). That's just one of the many advantages of developing with open source. Just always remember to give credit to the original author for his/her original hard work. [...]
+>
+> Learning all of Moodle and its database takes time - maybe even years. In fact you may never come across parts of it and that's OK. Take it one step at a time and don't be afraid to ask for help when you get stuck. The only expectation by the worldwide community is that you will have tried to figure things out on your own before asking a question. Google is your friend. Just start your query with the word "moodle".
+
+## Communication
+
+If you have any question or want to share your ideas, there are several channels you can use to communicate with other developers:
+
+- [Moodle community forums](https://moodle.org/course/), available in different languages.
+- [A Matrix room](https://matrix.to/#/%23moodledev:moodle.com) available for real-time communication. Read the [chat policies](https://docs.moodle.org/dev/Chat) before joining.
+- [Developer meetings](/general/community/meetings), organised periodically and open to anyone interested in Moodle development.
+
+## See also
+
+- [Releases](/general/releases) - versions of Moodle that have already been released
+- [Process](/general/development/process)
+- [API guides](/docs/apis)
+- [Contributing](/general/community/contribute)
+- [A (july 2017) forum thread](https://moodle.org/mod/forum/discuss.php?d=355789) about Getting Started with Moodle Development.

general/development/gettingstarted.md

@@ -102,7 +102,7 @@ For changing to a theme named "yay" add **?theme=yay** to the url.
 
 ## Notes
 
-- If the issue requires an Oracle or MSSQL installation for testing, and you don't have one, [docker](/docs/gettingstarted/quickstart#docker) may help you.
+- If the issue requires an Oracle or MSSQL installation for testing, and you don't have one, docker may help you.
 - Any update should be added as a comment on the tracker issue being tested.
 - If testers pass or fail an issue by mistake, then please request the integration team to reopen it for testing.
 - Testers should not be involved in the bug fixing or review process.

general/development/process/testing/integrated-issues.md

@@ -47,6 +47,7 @@ TODO
 Triaged
 Untriaged
 WCAG
+Xdebug
 XMLDB
 XMPPHP
 accessallgroups

project-words.txt

@@ -23,11 +23,8 @@ const sidebars = {
         'introduction',
         {
             label: 'Getting started',
-            type: 'category',
-            items: [
-                'gettingstarted/quickstart',
-                'gettingstarted/requirements',
-            ],
+            type: 'link',
+            href: '/general/development/gettingstarted',
         },
         {
             label: 'Developer guides',

sidebars/docs.js

@@ -26,6 +26,7 @@ const sidebars = {
     community: [
         'community/intro',
         'community/mission',
+        'community/contribute',
         'community/roadmap',
         'community/channels',
         {
@@ -143,7 +144,12 @@ const sidebars = {
         },
     ],
 
-    policies: [
+    coding: [
+        {
+            label: 'Getting started',
+            type: 'doc',
+            id: 'development/gettingstarted',
+        },
         {
             label: 'Policies',
             type: 'category',
@@ -154,16 +160,6 @@ const sidebars = {
                 },
             ],
         },
-    ],
-
-    documentation: [
-        'documentation/index',
-        'documentation/contributing',
-        'documentation/code-of-conduct',
-        'documentation/style-guides',
-    ],
-
-    tools: [
         {
             label: 'Tools',
             type: 'category',
@@ -179,6 +175,13 @@ const sidebars = {
         },
     ],
 
+    documentation: [
+        'documentation/index',
+        'documentation/contributing',
+        'documentation/code-of-conduct',
+        'documentation/style-guides',
+    ],
+
     releaseNotes: [
         getReleaseNotes(),
     ],

sidebars/general.js

@@ -24,7 +24,7 @@ import Link from '@docusaurus/Link';
 
 const FeatureList = [
     {
-        link: '/docs/gettingstarted/quickstart',
+        link: '/general/development/gettingstarted',
         title: 'Quick start',
         Svg: require('@site/static/img/undraw_docusaurus_mountain.svg').default,
         description: (

src/components/HomepageFeatures/index.js

@@ -33,7 +33,7 @@ function HomepageHeader() {
                 <div className={styles.buttons}>
                     <Link
                         className="button button--secondary button--lg"
-                        to="/docs/gettingstarted/quickstart"
+                        to="/general/development/gettingstarted"
                     >
                         Quick start - 5min ⏱️
                     </Link>