Here is a draft video script for your comment and ideas.
Merge request process is still work in progress to write in full sentence.
Fork a project (in plain English, copy project)
If you make your first contribution and you do not have write access for the repository you want to contribute to, you need to fork a project.
A fork is a personal copy of the repository, which you create in your namespace. A namespace provides one place to organize your personal or group projects. Press fork redirects you to ‘Fork project’ where you create a new fork. Your personal namespace is your user name. Go to Project URL and select your namespace on drop-down menu.
Launch Web IDE
On the project landing page, press . (dot) to launch Web IDE. Alternatively, Web IDE button is visible to click away. Getting started walk-throughs help you familiar with key features.
Navigate project directory in left pane of Web IDE. Click through modules/ROOT/pages directory path and select a file to edit. Start editing file with defined markup syntax.
You can see which files will be changed underneath the commit & push button. It works like git status and git diff commands. Press source control button (branching icon) and click changes to track changes with side-by-side view.
One-click commit and push
After you complete editing document, click source control button (branching icon) on left pane.
You will be prompted to enter commit message. Click commit & push.
If you click Yes, create a new branch with a specific name for the branch to commit that fixes issue. If no, select current branch to continue editing the file.
Merge request (in plain English, review and approve changes)
Merge request promotes collaboration between writers and reviewers.
Quality check before pushing changes to website
Once merge request pipeline passed, click view app to see rendered pages for quality check.
Beta user feedback
If you want to share feedback (suggestions for new features or unexpected behavior), head over to GitLab issue board specific to Web IDE beta.