← Lesson library CLASSROOMOS / COMPUTER SCIENCE / GITHUB Home

Learning paths / Ideas to Internet / GitHub

Founded 2008 · Version control for human collaboration

Ideas become shared.

Git remembers every useful change. GitHub gives that history a meeting place. Together, they let people prototype websites, document inventions, review one another’s work, and publish ideas to the world.

01
Start with a questionREADME.md · “Could a site help our club share events?”
02
Make the smallest versionindex.html · one page, one audience, one job
03
Invite a useful reviewpull request · explain the change, test the link
04
Publish and learnGitHub Pages · prototype live, history preserved
00 / ORIENT

One platform, three powers

This is not simply cloud storage. GitHub combines a project home, a detailed memory of change, and a structured conversation about what should happen next.

Remember

Explain how a commit preserves a meaningful checkpoint instead of replacing the past.

Collaborate

Use a branch, pull request, review, and merge to improve work without everyone editing the same copy.

Launch

Choose an idea that fits GitHub, organize its repository, and publish a safe static prototype with Pages.

2008

A social layer for software

GitHub launched in 2008 as a place to host Git repositories and collaborate on code. Its big idea was human: make change visible, discussable, reviewable, and reusable. Today the same workflow can support a science dashboard, club website, game prototype, hardware documentation, art portfolio, research notebook, or almost any idea that benefits from files plus a clear history.

01 / MODEL

Git is the memory. GitHub is the meeting place.

Keep these two ideas separate and the rest of the system becomes much easier to understand.

Git

A version-control system that tracks snapshots of files. It can work locally on one computer without GitHub.

≠

GitHub

An online platform that hosts Git repositories and adds accounts, issues, pull requests, reviews, project tools, and Pages hosting.

Repository

The project folder, its files, and the history of those files.

Commit

A named checkpoint: what changed, who changed it, and when.

Branch

A safe line of work where an idea can grow without disturbing the main version.

Issue

A focused conversation about a task, question, proposal, or problem.

Pull request

A request to compare, discuss, test, and possibly merge one branch into another.

Merge

The act of bringing approved changes together into the shared line of work.

02 / PRACTICE

Work inside a real-feeling repository

You are joining lunar-field-guide, a student Pages project built with public-domain NASA science imagery. Inspect its files, commit a focused change on a branch, open a pull request, pass review, merge, and watch the published site update.

orbital-classroom /lunar-field-guidePublic
2 commits ahead of main · safe place to work
Files2 commits
lunar-field-guide / README.mdPreview

Lunar Field Guide

A small, accessible atlas that compares worlds using spacecraft observations and clearly credited public-domain media.

1 changed file is ready to commit.

Recent commits
8bd14e2Start lunar atlas
a42e61cAdd Earth and Moon facts
Next: commit the Sun card on the feature branch.
https://orbital-classroom.github.io/lunar-field-guide/
PAGES · MAIN BRANCH

Lunar Field Guide

Published version: Moon and Earth. Merge the pull request to deploy the new Sun comparison.

Published lunar guide preview showing the LRO Moon mosaic
Published lunar guide preview showing the LRO Moon mosaic

Authentic media: NASA Scientific Visualization Studio. Its visualizations are public domain unless otherwise noted. This lesson reuses existing local copies and keeps source, mission, and alt-text information beside the files.

03 / COLLABORATE

The GitHub flow is a conversation with evidence

Each step reduces a different risk: unclear work, accidental breakage, invisible decisions, or untested changes.

ISSUEName the need

What is wrong or worth making? Define “done.”

BRANCHProtect main

Create a separate place to try the change.

COMMITSShow progress

Save small, understandable checkpoints.

PULL REQUESTAsk for review

Compare the branch, explain choices, and test.

MERGEShare the result

Bring the approved work into the main branch.

Mini review: what would help the author most?

The pull request says “Improve home page.” The change adds a button:

+ <button style="color:lightgray">Learn more</button>

Choose the review that names evidence and a useful next step.

04 / PLAN

Give your idea a platform

A repository is strongest when it has one clear purpose, a small first version, and a README that helps another human understand what they found.

campus-garden-map

Strong GitHub fit
campus-garden-map/
├── README.md
├── index.html
├── style.css
├── script.js
└── assets/
  • Write the audience and purpose in README.md.
  • Build the six-plant map in index.html.
  • Test every label and link on a phone.
The “platform” is more than the published page. Your repository can hold the prototype, design decisions, a task list, evidence, feedback, and every revision. That makes the thinking visible—not only the final product.
05 / SHIP

Publish a first website with GitHub Pages

This browser-only route avoids the command line. GitHub’s labels can change over time, so use the linked official guide if the interface differs.

1

Create your account safely

Students must meet GitHub’s age requirement (13+ in the U.S.; local minimum ages may differ). Use a unique password, enable two-factor authentication, and do not put private information in the username or profile.

2

Create a repository

Select + → New repository. Use a short lowercase name such as cloud-guide. For free Pages, choose Public. Turn on Add a README, then create it.

3

Add the home page

Select Add file → Create new file. Name it exactly index.html. Add your HTML, preview it, and commit with a message that describes the change.

4

Turn on Pages

Open Settings → Pages. Under Build and deployment, choose Deploy from a branch, then main and /(root). Save.

5

Open and test the URL

Your project site normally appears at https://USERNAME.github.io/REPOSITORY/. Publishing can take a few minutes. Test navigation, mobile layout, keyboard use, and image paths.

6

Improve through branches

Create an issue for one improvement, make a branch, commit the change, open a pull request, ask for a focused review, then merge after testing.

Pre-publish gate

0 of 4 release checks complete.

06 / DECIDE

Know what belongs on GitHub—and what does not

GitHub Pages hosts static files. Anything committed to a public repository can be copied, even if you delete it later. Treat every public commit as permanent.

Before an account or a publish

  • Under 13? Do the planner and simulations without an account; use a teacher-approved school platform instead.
  • Public means public. Use project names, not personal details. Never publish class lists, private photos, precise schedules, or student locations.
  • Secrets never go in code. API keys, passwords, database credentials, and private tokens do not belong in HTML or a public repository.
  • Credit creators. A file being online does not mean you may reuse it. Check its license and add attribution.
Great fit

Static websites, portfolios, browser games, public data stories, documentation, design prototypes, open-source code, and project planning.

Needs another service

Logins, live databases, payments, private forms, or server-side code. GitHub can store the code, but Pages alone cannot safely run the backend.

Do not publish

Passwords, secret keys, private student data, copyrighted uploads without permission, harmful code, or anything that exposes someone’s safety.

07 / PROVE

Can you think like a collaborator?

Choose the best answer for each real project decision.

1. Your teammate wants to try a new navigation system without breaking the published site. What should they create?
2. What makes “Improve the page” a weak commit message?
3. A weather site needs a secret paid API key. Where should the key go?

SOURCE / CONTINUE

Use the live documentation

These official sources support the lesson and are the best place to check current labels, requirements, and workflows.