Find knowledge. Improve knowledge.
This time you are not creating a new article. You are locating an existing classroom Knowledge Article, identifying a specific improvement, and proposing that change through GitHub.
Improve the existing no-display Knowledge Article by making one troubleshooting decision point more explicit.
Start at the Knowledge Base index.
Open the classroom Knowledge Base. Under Worked Example, open EXAMPLE — Workstation Powers On but No Display.
Open classroom Knowledge Base ↗The index is the front door for accepted classroom knowledge.
Read the official classroom copy first.
The page you opened is the official classroom repository on the main branch. This is the copy students read. Do not edit this copy directly.
At the top of GitHub, the branch selector should say main. The path should show CIT-205-classroom / knowledge / examples / KA-EXAMPLE-No-Display.md. That tells you that you are reading the current classroom version of this article.
The article asks whether the monitor can display its own menu, but the troubleshooting steps never tell the technician what to do with that result.
Use the monitor controls to open its on-screen menu. If the menu does not appear, stop workstation-side troubleshooting and escalate the display or power issue. If the menu appears, continue.
You needed to inspect the accepted classroom version before deciding what should change. Reading happens here. Editing will happen in your personal fork.
Leave the classroom copy and open your fork.
You are currently looking at the shared classroom repository. Your edits belong in your personal fork, the copy you created in the first guided mission.
Tap your profile picture in the upper-right corner of GitHub. Open your repositories and choose CIT-205-classroom.
On the front page of your copy, GitHub should show Forked from student-operated-technology-ecosystem/CIT-205-classroom. That line confirms you are in your personal fork instead of the official classroom repository.
Classroom repository: read the accepted version.
Your fork: build and propose the revision.
Make sure your fork is current.
Stay on the front page of your personal fork with the branch selector set to main.
Look below the branch selector for the box that compares your fork with student-operated-technology-ecosystem/CIT-205-classroom:main.
If GitHub says This branch is ... commits behind, tap Sync fork. If GitHub asks you to confirm, choose the option to update your branch. Wait for GitHub to finish.
If GitHub already says This branch is up to date with student-operated-technology-ecosystem/CIT-205-classroom:main, do not press anything. You are ready for the next step.
Do not continue until the status box says your main branch is up to date with the classroom repository.
The classroom article may have changed since you created your fork. Syncing updates your fork's main so the revision starts from the current accepted version.
Create the revision branch.
Your fork's main is current. Now give this proposed improvement its own branch.
Find the branch button just above the file list. It currently says main. Tap it.
If GitHub shows a search field, tap inside it. If it shows View all branches first, open that.
Replace YOUR-GITHUB-USERNAME with your actual GitHub username. Example: if your username is jrivera, type revision/jrivera-no-display-menu. Then choose the option GitHub offers to Create branch or Create branch from main.
After GitHub creates it, the branch button on the repository page should begin with revision/.
If the branch button still says main, stop and select the revision branch before editing anything.
Edit the existing file.
Now you will make one specific improvement to the existing article. You are not rewriting the whole document.
Open knowledge/examples/KA-EXAMPLE-No-Display.md in your fork while your revision/... branch is selected.
On mobile, use the file toolbar ••• menu and choose the edit option.
Scroll to the section headed ## Troubleshooting Steps. Find the first step:
1. Confirm that the monitor has power and observe its power indicator.
Paste this exact text as the new Step 2:
2. Use the monitor controls to open its on-screen menu. If the menu does not appear, stop workstation-side troubleshooting and escalate the display or power issue. If the menu appears, continue.
The old Step 2 becomes Step 3, the old Step 3 becomes Step 4, and so on. Do not change the wording of the other troubleshooting steps.
Use Preview and confirm the new decision step appears immediately after the monitor-power check and before the input/cable checks.
Your article should now contain the new monitor-menu decision point and no unrelated edits.
Choose Commit changes…. Leave the confirmation window open and return to this guide for the next step.
Record the revision.
Use Add monitor-menu decision point to no-display article as the commit message. Commit directly to your revision/... branch.
After the commit, the rendered article should contain the new decision step.
Inspect the change before opening the pull request.
This is where GitHub shows you exactly what your revision changes compared with the classroom version.
- Return to the front of your fork.
- Open Contribute → Open pull request.
- Confirm the direction is your revision branch → classroom main.
Open Files changed. In the header for the Markdown file, look on the right side for GitHub's rich diff / rendered diff control, shown as a small file-style icon. Tap it to switch from raw Markdown to the rendered document comparison. Added and removed prose will be highlighted in context.
Rendered diff = understand the article change.
If you need to comment on an exact sentence or line, switch back to the normal source/code diff. GitHub attaches review comments to specific changed lines there.
Source diff = comment on the exact line.
The comparison should modify the existing KA-EXAMPLE-No-Display.md file. It should not create a second copy of the article or change unrelated files.
- Title it
Improve no-display article — monitor menu decision point. - Explain that the change turns an existing question into an actionable branch without claiming a specific hardware failure.
- Ask reviewers to check whether the new branch point is clear, safe, and placed in the right sequence.
- Create the pull request.
You proposed an improvement to existing knowledge.
If the revision is reviewed and merged, the existing classroom article changes on main, while GitHub preserves the prior version in history.
Accepted articles are not frozen. Clear, reviewable improvements can keep classroom knowledge accurate and useful over time.