Document how to deploy a Drupal update to production server with Composer and Drush

I've made a few suggestions on that documentation page's Discussion page. TL;DR: That documentation page is just terrible. It neeed to be scrapped and rewritten from scratch. Just to mention a few problems:

1. It conflates updating/deployment with carrying out development task (bad computer science).
2. It gives the reader the idea that updating Drupal "manually" is feasible (with Drupal 10, it is not).
3. Its target audience is Drupal developers. We need to provide documentation for site owners that are not developers (those are the ones who are currently struggling with updates).

Yes, even if you're not a developer, but more of a site builder, it's best practice to use Composer, Drush, and Git, and we should document the very basic steps for site owners on how to deploy code changes to production.

I am removing the ", with correct parameters, such as --no-dev" part to focus on getting the basic steps and commands documented.

Maybe it's easiest to try to reach a great text here, and when it's ready, add it to the documentation page?

Thanks @gisle, many great points. I went ahead and rewrote the page, to be about updating Drupal, and not development, removed any references to manual update, and simplified the steps, to accommodate site owners, i.e. non-developers.

After that, I added a separate section for the basic steps for deployment of a new feature. It could get its own page, or stay here?

Feel free to move back but seems this is related to drupal.org pages so seems this project may be more the right spot.

Yes, thanks @smustgrave, this is the right place for this issue.

I read the new page and the changes read well to me and are correct. There is a question asked in #6 but, even with that, I think the intent of the issue summary has been fulfilled.

Thanks for reviewing the page @quietone, it's great to hear that the page works as intended, and may help users looking for help with deploying an update.