Introduction to GitHub

GitHub is a web-based platform that developers use to store, manage, and share their code. To understand what makes GitHub so powerful, it helps to first understand the technology it is built on: Git. Git is a version control system — a tool that tracks every change you make to your files over time. Think of it like a detailed undo history for your entire project. Every time you save a snapshot of your work (called a commit), Git records exactly what changed, when it changed, and who made the change. GitHub takes this system and moves it to the cloud, giving you a place to store those snapshots online so that your code is accessible from any computer, anywhere in the world.

GitHub is not a niche tool — it is the industry standard. Millions of developers, companies, and open-source projects rely on it every day. Major software products you use regularly, from operating systems to mobile apps, have their code managed on GitHub. Because of this, familiarity with GitHub is a genuine professional skill, and building a presence there early in your studies gives you a head start. In this course, every project you build will be stored on GitHub, creating a living portfolio that you can share with instructors, peers, and eventually potential employers.

There are several practical reasons why developers choose GitHub over simply saving files on their computer:

• Full change history: GitHub keeps a complete record of every version of your project. If you add a feature and it breaks everything, you can roll back to the last working version without losing all your other progress. This safety net makes it much less stressful to experiment and try new things.
• Access from anywhere: Because your code lives on GitHub's servers, you can work on your project from your laptop at home, a computer at school, or any other device with internet access. You are never locked to a single machine.
• Collaboration without conflict: GitHub allows multiple people to work on the same project at the same time. Its tools are designed to merge contributions from different people intelligently, so team members do not accidentally overwrite each other's work.
• Portfolio and visibility: Your GitHub profile is a public record of what you have built. Sharing a link to a working project is far more compelling than describing it on a résumé.

The first practical step is creating your own GitHub account. Open a browser and go to github.com. You will see a prominent Sign up button on the homepage. Click it to begin the registration process. GitHub will walk you through several steps: you will enter a valid email address, create a username, and set a secure password. You may also be asked to verify your account through a short puzzle and a confirmation email. The free tier of GitHub gives you everything you need for this course, so there is no need to select a paid plan.

One decision during sign-up deserves careful thought: your username. This is not just a login name — it becomes a permanent part of your public identity on the platform. Your username will appear directly in the web address of your GitHub profile (github.com/yourusername) and, critically, in the address of the live website you will publish later in this module (yourusername.github.io). Because that URL is what you will share with others as part of your portfolio, it is worth choosing something professional and easy to remember. Here are the rules and recommendations:

• Usernames may contain letters, numbers, and hyphens ( - ).
• Usernames cannot contain spaces, underscores, or other special characters.
• Usernames are not case-sensitive, but the casing you choose is displayed on your profile.
• Choose something that reflects you professionally — your name, initials, or a consistent online handle works well. Avoid usernames that are overly casual, hard to spell, or likely to feel embarrassing in a professional context.
• You can change your username after the fact, but doing so will break any existing links to your profile and repositories, including the GitHub Pages URL you share with others. It is much easier to choose a good name from the start than to update all those references later.

For example, if your name is Jordan Rivera, a username like jordan-rivera or jrivera-dev is clean, professional, and results in a readable GitHub Pages URL such as jordan-rivera.github.io. A username like coolguy2009 is harder to take seriously in a professional portfolio context.

Once your account is created and your email is verified, you should spend a few minutes configuring your profile. Click the avatar icon in the top-right corner of any GitHub page and choose Your profile, then Edit profile. There are a few fields worth filling in right away:

• Profile photo: Upload a clear, professional-looking photo or a recognizable avatar. Profiles with photos feel more credible and are easier for collaborators and instructors to identify. You can use any image file from your computer.
• Bio: Write a short sentence or two describing who you are — for example, "Web development student building my first projects." This short description appears right on your public profile page and gives visitors immediate context about you.
• Name: GitHub lets you display your real name separately from your username. Filling this in makes your profile more human and searchable.

Your public profile page is more than just a settings screen — it is the front door to your portfolio. It displays all of your public repositories, a contribution graph showing how actively you have been working, and any profile information you have provided. As you complete projects throughout this course, each one will appear here, gradually building into a record of your growth as a developer. Keeping your profile complete and up to date from the beginning is a small habit with a meaningful long-term payoff.