Why a GitHub course with no code in it
GitHub long ago stopped being just a programmers' tool. Company handbooks live there. Government laws are published there. This very course is hosted there, free. If your team ships anything with engineers - or you simply want the world's best system for working on documents together without emailing final_v3_FINAL.docx - GitHub is worth 6 browser-only sessions. By Session 5 your own handbook is a live website; today you get the map and the keys.
What GitHub actually is 5 min live
Underneath: a system that remembers every version of every file, forever, with a name on every change. On top: the world's largest collaboration site. The version-control engine is called git (tech track's business); everything you need lives in the web layer above it.
LiveThe three superpowers, in office terms3 min▶
- Perfect memory. Every save ("commit") keeps the old version and records who changed what, when, and why. Nothing is ever lost to "whoops, I saved over it". The Word version of this is track-changes that never expires and never bloats.
- Proposals, not overwrites. Nobody edits the master document directly. You propose a change, colleagues see exactly what would change, discuss it, then accept. That flow (the "pull request", Session 4) is the single best idea GitHub exports to non-tech work.
- Work in the open. Public repos mean anyone can read, learn from, and build on your work - which is why 100M+ people and most of the world's software companies are here, and why a good GitHub presence has become a public portfolio.
Germany's federal laws are mirrored on GitHub (the "gesetze" repos): citizens can see every amendment as a tracked change, diffed line by line, with history back through time. No code anywhere - just the three superpowers applied to legislation. If it works for a legal code, it works for your team handbook.
Self-studyGit vs GitHub: the one distinction people mix up2 min read▶
git (lowercase) is the version-control engine - a command-line tool from 2005 that developers run on their machines. GitHub is a company and website (2008) that hosts git repositories and adds everything friendly on top: the web interface, issues, pull requests, profiles, Pages websites.
- You can use git without GitHub (some companies host elsewhere: GitLab, Bitbucket).
- You can use GitHub without ever touching git - that is this entire track. The web UI covers creating, editing, proposing and publishing.
- When a developer says "clone", "push" or "pull", they are speaking git. Session 6 gives you the phrasebook; the tech track teaches the driving.
The mental map 5 min live
Every GitHub URL decodes the same way: github.com / who / what. The "who" is a personal account or an organization; the "what" is a repository - one project's home. Learn to read that address bar and you can never get lost.
LiveRepository = one project's home3 min▶
A repository ("repo") holds one project's files plus everything about the work: its history, its task list, its proposals in flight. Think of it as a shared folder that grew up - the folder plus the track-changes, the todo list, and the review process, all in one address.
- Public repo: anyone on the internet can read (only invited people can change). This is how open source, handbooks and portfolios work.
- Private repo: invisible except to people you invite. Default for internal work.
- One project, one repo. Resist the mega-repo-for-everything instinct; addresses stay meaningful when scope stays tight.
Self-studyThe five tabs of every repo2 min read▶
| Tab | What it holds | Your session |
|---|---|---|
| Code | the files themselves + the README front door | Session 2 |
| Issues | the task list: bugs, ideas, todos, questions | Session 3 |
| Pull requests | proposed changes under discussion | Session 4 |
| Projects | kanban boards built from issues | Session 3 |
| Settings | visibility, collaborators, Pages publishing | Session 5 |
("Actions", "Wiki", "Insights" and friends exist too - Session 6 gives you the literacy-level tour.)
Set up your account like you mean it ★ 8 min · everyone signs up
Go to github.com and create your account (or sign in). Username advice: close to your real or professional name - it appears in every URL you will ever share. Skip all paid upsells; everything in this course is free.
Settings → Profile: add a photo and a one-line bio saying what you do ("Data PM at ...", "Ops lead, building the team handbook"). Two fields, disproportionate signal.
Visit one famous repo as a tourist: github.com/github/docs (GitHub's own documentation - largely prose, heavily contributed to by non-engineers). Find: the README, the star count, the Issues tab, the last-updated time.
Star it. Congratulations - your library has its first book, and you have read your first repo.
Where does this live? ★ 7 min · everyone sorts
Six things you will meet this course. Place each in its GitHub home - this is the map check.
Claim your profile README ★ 7 min · everyone publishes
Top-right + button → New repository. Name it EXACTLY your username. GitHub reveals the easter egg: "You found a secret! This repository's README.md will appear on your public profile."
Keep it Public, tick Add a README file, click Create repository. That is your first repo - made entirely in the browser.
Click the pencil ✏️ on the README, replace the contents with two lines about yourself, press Commit changes. That green button just made your first commit - a save with your name and a note on it.
Visit github.com/yourusername - your words are on your profile, live on the internet. Session 2 teaches the markdown to make it beautiful.
Browse a few profile READMEs for inspiration afterwards (search "awesome profile README"). Some are resumes, some are dashboards, some are art. Yours starts as two honest lines - that already beats blank.
This week ◐ 20 min total
- Tourist visits: open three repos from your world (a tool your team uses, a template you might want, anything trending). For each, find README, stars, last update, open issues count. Two minutes each - the reading gets automatic fast.
- Star five repos worth keeping. Your stars page is now a library.
- Finish your profile: photo, bio, profile README with 3-5 lines. Pin the repo.
- Optional deep end: the official Skills course Introduction to GitHub (github.com/skills/introduction-to-github) - 30 min, hands-on, covers today plus a preview of Session 4's flow.
Three questions before you go 🎯 ◐ 90 seconds
1 · A colleague sends you github.com/centience/client-site. What do you know before clicking?
github.com/who/what - centience is the owner (an org, in this case), client-site is the repo. The address bar is the map.
2 · What is a "commit", in office terms?
Every commit preserves what came before and records who, when and why. Perfect memory is superpower number one.
3 · The secret to putting a personal intro on top of your profile page is...
The username-repo README is a free easter egg - you built it in Apply-along 3. Session 2's markdown makes it shine.
Official GitHub Skills coverage
This course maps to GitHub's own free Skills exercises - each session tells you honestly what is covered here and what the official course adds.
Profiles, stars and reading the room 5 min live
GitHub is also a social network - the professional kind that shows work instead of talking about it. Three verbs run it: star (bookmark + applause), follow (see what a person is up to), watch (get notified about a repo). Your profile is the landing page recruiters and collaborators actually check.
LiveStars, follows, and what a good profile signals3 min▶
The handbook company: GitLab (yes, a competitor) famously runs its entire 2,000-person company on a public handbook - policies, salaries formula, processes - maintained exactly the way you will maintain yours: proposals, reviews, versions. Non-tech staff make most of the edits. The pattern you are learning this course IS a real operating model.
Self-studyExplore and trending: finding good stuff2 min read▶
github.com/explore and github.com/trending surface what the world is starring right now. Two non-tech uses: