Git and GitHub in plain terms — the five commands you need and nothing more.
⬡ What you'll build
GitHub has a reputation as a tool for professional software developers. That reputation makes people who don't write code avoid it entirely.
This is a mistake. GitHub is fundamentally a version-controlled backup system. It saves every version of every file you've ever had, lets you restore anything, and enables deployment automation. You don't need to understand how it works internally — you need to know five commands.
Imagine a folder on your computer with your website's files. Without Git, if you accidentally delete something or a change breaks something, you have no way to go back.
With Git, every time you say "save this checkpoint," Git takes a snapshot of the entire folder. You can always go back to any checkpoint. The folder's entire history is preserved.
Git is the software that does this. It runs on your computer.
GitHub is a website that stores your Git checkpoints in the cloud. Your folder's history lives on your computer AND on GitHub. This means:
This is everything you need:
git init
Turns a regular folder into a Git-tracked folder. Run once, at the beginning.
git add .
Tells Git "include all changed files in the next checkpoint." The . means "everything."
git commit -m "describe what you changed"
Creates the checkpoint (called a "commit"). The message in quotes is your description of what changed.
git push
Sends your local checkpoints to GitHub. This is what triggers Vercel to redeploy.
git pull
Downloads the latest checkpoints from GitHub to your local computer. Use this when you've made changes on GitHub directly or you're working across multiple computers.
For most content and configuration changes, you will run exactly this sequence:
git add .
git commit -m "add post about [topic]"
git push
Three commands. That's it.
Windows: Download from git-scm.com. Use all default settings during installation.
Mac: Open Terminal and type git --version. If Git isn't installed, macOS will prompt you to install developer tools. Click Install. It takes 5 minutes.
Open Terminal (Mac) or Command Prompt/PowerShell (Windows):
git config --global user.name "Your Name"
git config --global user.email "you@yourdomain.com"
This runs once. It's just metadata that appears in your commit history.
Go to github.com. Create a free account. Use your real name or business name — this account is permanent.
Then in your terminal:
git clone https://github.com/yourusername/your-repo.git
cd your-repo
Your repository is now on your computer. Start adding files.
If you have a project folder with files:
cd /path/to/your/project
git init
git add .
git commit -m "initial commit"
Then go to GitHub, create a new empty repository (no README), and connect:
git remote add origin https://github.com/yourusername/your-repo.git
git branch -M main
git push -u origin main
Your files are now on GitHub.
When you push for the first time, GitHub will ask for your credentials. The modern way to authenticate is with a Personal Access Token:
When prompted for password during git push, paste this token instead of your GitHub password.
On Mac, this token gets stored in Keychain after the first use — you won't be asked again. On Windows, it gets stored in the Windows Credential Manager.
.js, .ts, .tsx, .html, .css, .py, etc.)package.json, next.config.mjs, etc.).mdx, .md, .json).env.local file and add that file to .gitignorenode_modules folder — this is automatically excluded by .gitignore in most projectsThe .gitignore file in your project tells Git which files to skip. Most project templates include a sensible .gitignore by default. Check that .env and .env.local are in yours.
When you import a repository into Vercel:
main branch, Vercel automatically rebuilds and deploys your siteThis means the deployment workflow is:
Edit files → git add . → git commit → git push → site updates automatically
No manual deployment steps. No FTP. No server management.
Your commit history is a running record of what changed and when. Get into the habit of writing commit messages that describe the business action, not the technical change:
Good commit messages:
add guide on keyword research for beginnersupdate pricing table — Hostinger raised Business plan pricefix broken internal link on homepageadd featured image to 5 unpublished postsUseless commit messages:
updatefixchangesasdfghYou will search your commit history eventually. Make it searchable.
GitHub isn't just for code. You can use it to version-control:
.mdx files).md files)If you're running a WordPress site and not using version control: at minimum, keep your content templates, Claude prompt files, and any custom configurations in a GitHub repository. You don't need your WordPress theme in Git — but your workflows and templates should be.
ℹGitHub Desktop if you prefer visual tools
GitHub Desktop (desktop.github.com) is a free GUI application that wraps the git commands in a visual interface. It's legitimate and reliable. However, learning the five commands above is worth the investment — they work everywhere (remote servers, cloud environments, Claude Code terminal) while GitHub Desktop only works on your local machine.
⚠Don't commit secrets
The most common mistake beginners make with GitHub is accidentally pushing API keys, passwords, or .env files to a public (or even private) repository. If you do this, consider those credentials compromised and rotate them immediately. Git history preserves deleted files — you cannot simply delete the file and push again. The secret is still in the history. The fix is key rotation, not deletion.
Implementation Checkpoint