GitHub comes with a lot of terminology.
Most of it is unnecessary for what you’re trying to do.
You do not need to learn Git.
You do not need to understand version control theory.
You only need a handful of concepts.
REPOSITORY = YOUR PROJECT
A repository (or “repo”) is just a folder.
That’s it.
It’s:
Your app
Your website
Your notes
Your experiment
If it lives on GitHub, it lives inside a repository.
You can think of it as:
“This is the container for my thing.”
FILES = THE ACTUAL CONTENT
Inside your repository are files.
These could be:
Code files (.js, .html, .py)
Text files (.md)
Images
Anything else your project needs
You don’t need to understand all of them.
You just need to know:
This is the stuff that makes your project work.
COMMIT = SAVING YOUR PROGRESS
This is the most important concept in this entire blog.
A commit is a save point.
Every time you make a commit, you are saying:
“This version works”
“This is where I want to come back to”
“I might try something risky next, but I can return here”
If you remember nothing else, remember this:
Commits are your safety net.
README = YOUR PROJECT’S FRONT PAGE
The README is the first thing people see when they open your repo.
It’s just a text file.
But it acts like:
A homepage
A description
A guide to what your project is
For now, you don’t need to perfect it.
Just understand:
It’s where you explain what your project is.
THAT’S ENOUGH
At this point, you already understand enough to use GitHub effectively.
Everything else—branches, pull requests, forks—can wait.
Or never matter at all.