Have you tried Web IDE beta in GitLab?
I have been pondering about making video tutorial for new contributors working on Fedora projects (repo) in GitLab. My ideas are much influenced by @py0xc3 @pboy @darknao , and Web IDE beta release in December 2022.
I wrote a rough segment sketch before I make video script and screen recording.
See Snippet here.
design team, or to anyone who has creative mind and passion, I appreciate your feedback.
Thatās a great idea!
Concerning the points you noted in GitLab:
Restructure the casual contributor guide in sequential order
...
Shorten the sequence, if possible
I guess we can exploit synergies here. Generally, the guide should be in sequential order. If this is not the case at some point, we should definitely change this and adjust the guide to make it sequential again. Maybe we broke the sequences in the recent updates?
The same for shortening the sequence: unfortunately, the changes in GitLab have forced us to expand the guide, but I would love to make it ā7 stepsā again some day (or at least get closer to 7 than now).
If there would be a video tutorial, we could add it in a TIP box to the beginning of the guide.
What I mean by putting the guide in sequential order is my way of reverse-engineering and breaking things down (like dismantling test sample).
Iām not saying the guide is in wrong order, but some of step is not in equal section level (H2, H3).
Some of āclicksā is a step on its own right whereas some H2 section is blended in a paragraph. Not all āclickā is a process step.
We will have to wait for next releases until May and reiterate the process on every release.
Shortening the sequence is reiteration process to make the story telling concise in visual content.
Sure, Iām looking for synergies on content reuse and update.
Ah, now I got it 
Concerning the levels (H2, H3), I guess you mean that the second section is only H2 and all following sections H3. In the original version, that was intended. But with your comment in mind, I have to admit that this no longer fits the guide and can confuse people who read/write in the asciidoc source: I have aligned all H2 and H3 to H2 with Commit 30efc2ac. Thanks for making me aware of the issue!
Four process groups are created;
Here is a draft video script for your comment and ideas.
Merge request process is still work in progress to write in full sentence.
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.
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.
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 promotes collaboration between writers and reviewers.
Once merge request pipeline passed, click view app to see rendered pages for quality check.
If you want to share feedback (suggestions for new features or unexpected behavior), head over to GitLab issue board specific to Web IDE beta.
I canāt contribute much to the Web Interface, because I prefer the local authoring environment. But 2 comments
Web IDE workflow is another way to contribute. So for me, the tool is not an āeither orā question.
I use local environment when I need to render document in my web browser (example: link changed, nav.adoc changed, style/header change applied, complete rewrite of documents).
Web IDE is to fix minor issues where I donāt need preview. Web IDE workflow makes forking process approachable to non-developers. The advantage of using Web IDE is I can work with any computers or tablets as long as I have a web browser. The new Web IDE is a great tool as a bridge to remote development. We need to give paths for growth to contributors, who are aspiring or pro developers as well as non-developers.
It will be short, so splitting down it to a few pieces and interlace them around existing pages will be cumbersome to maintain. So no.
Videos are complementary tutorials to express flow of actions much better than screen shots.
Voice over, transcript/video caption will be added so it can be presented standalone, not interlaced with existing pages.
The reason why I started with video script is maintenance of video tutorials/version control.
Maybe we should expand this to a tools overview page (menu item ācontribution toolsā?
I would leave the decision to a later stage once we get enough traction and interest in this thread.
There are three unused links in the menu item and they appear overcrowded already, which do not give clear signpost to contributors (existing and new alike). Expanding the menu item will cause decision paralysis.
About tasks required for screen recording and moderation for content, Iām looking forward to feedback from Web IDE users or someone who is interested to give it a try.
I learn as I go along, so I get hands-on with Kdenlive (screen grab) for recording and editing.
Any feedback about screen recording and tutorial process will be appreciated.
Please let me know for doing early trials.
Early trials equal to beta? Could you elaborate what you mean by that?
Whatever workflow I settled in for writing and reviewing docs, I aim to:
Of your scripts / videos.
If you want feedback from a non-developer.
Here is some update on contribution guide using GitLab tools (Web IDE and live preview during MR). The new page went live 22 March. 
Please let me know what you think and give it a try yourself. All you need is your GitLab account linked to Fedora account and your web browser.
I will work on video version of GitLab user guide for docs contributions, using screen grabbing with Kdenlive. Maybe Iāll experiment voice over and caption.
Hi, I need to work on scripts over next weeks after my PTO (27-31 March).
Hi folks!
Issue created to track progress.
Here are steps to create video tutorial.
Hi Folks,
Iām sharing screen recording - Fedora Docs team contributor tutorial video Part 1.
Video is for preview and your feedback. Unedited. No sound or fancy effects.
Duration: 4m 40s
== Part 1. How to fix inactive link and navigate to Fedora Docs editing tool
Go to User Documentation on the lower right corner from the new Fedora Website - Fedora Start | The Fedora Project
Click system upgrade on the left pane
Read the docs and check if the link works correctly
Example: Automatic upgrade using dnf system upgrade
Link: Upgrading Your Current System :: Fedora Docs
If the link does not open the page, check the URL and file name
Press the āEdit this Pageā button on top-right corner to go to GitLab
Note: To simplify the content, this video skipped GitLab authentication process.
== Part 2. How to use Web IDE
Click the blue āWeb IDEā button
Create a new fork and a branch
Create a new branch and switch to it. See status bar
To create a branch from the current branch in the Web IDE Beta:
Are you sure you want to checkout ābranch-sequenceā? Any unsaved changes will be lost.
You will see the following message.
āReady to merge by members who can write to the target branchā.
Thanks for your contribution.
Software used for recording
Repost by a GitLab developer
