learning how to contribute to Drupal

$drush en

is to enable the module

so the bug fixes are always added to the dev branch !!!

the hooks are all saved in the modules folder

$drush <name> to install a particular module

$drush si will give the log in details

so all of the routes for the files are in the routing.yml folder

a controller is a class that will control the request to certain routes and will direct it to certain methods

the form is being built with using different files and classes

the t method is for translating so just add this before the parenthesis and before the arguments are passed in

after clearing the cache the paragraphs collection has been added

there are no patches and so we must create a patch this is the issue that's being resolved

creating a patch with git

so in order to create a patch in git type git diff then add '>' then specify the name of the file you want to create and it will be done.

before you upload a patch you can test it before uploading to Drupal.org

interdiff is showing the difference between two patches

you can upload a patch in the UI and select it in your files and you can also select which env to test it

Drupal has a GitHub functionality when it comes to contrib

there are many different ways to contrib

so for example reporting bugs and opening issues and also write tests too, so you must write down clearly the steps to reproduce the problem, then the next level is to write tests and its a good indicator for example if you write a test that fails. fix it itself

install Drupal extension - dreditor !!