API Consumption Project

API Consumption Project

Build a GitHub User Search app that fetches data from the GitHub API.

Features

• Search by GitHub username
• Display avatar, name, bio, repositories
• Loading spinner while fetching
• Error handling (user not found, rate limit)
• Cache recent searches in localStorage

What You Will Learn

1. HTTP requests — GET, POST with fetch()
2. Async/await — handling asynchronous operations
3. JSON — parsing and formatting
4. Error handling — try/catch, HTTP status codes
5. Environment variables — protecting API keys

Project Architecture

Before writing any code, let's understand what files we need and where they go. Think of this like a blueprint for a house — you don't start building without a plan.

The File Tree

Every project needs a folder structure. Here is ours:

├── index.html
├── css/styles.css
├── js/weather.js
├── js/ui.js
├── js/config.js
├── .env

What Each File Does

Let me explain each file like you're 5 years old:

index.html — Weather app interface

Search bar, current weather card, 5-day forecast, error messages.

css/styles.css — Weather-themed styling

Dynamic backgrounds based on weather conditions.

js/weather.js — API calls and data handling

Fetches data from OpenWeatherMap, parses JSON, handles errors.

js/ui.js — DOM updates

Takes weather data and renders it to the page.

js/config.js — API configuration

Stores API key and base URL (use env vars in production).

.env — Secret API key

Never commit this file — contains your private API key.

Why This Structure?

You might wonder: why use folders at all? Why not put everything in one place?

Because as projects grow, you might have:

• Multiple CSS files
• Many JavaScript files
• Images, fonts, and other assets

If they're all in one folder, it's chaos. Folders keep things organized.

// BAD — everything in one folder
index.html
styles.css
main.css
dark.css
app.js
utils.js
helper.js

// GOOD — organized in folders
index.html
css/
  styles.css
  main.css
js/
  app.js
  utils.js

The Golden Rule

When you start a project, ALWAYS:

1. Create the folder structure FIRST
2. Then fill in the files one by one
3. Never write everything in one giant file

This is how professional developers work. Always.

Setting Up the Project

We are going to create an empty project from scratch. This is the exact process professional developers use every single day.

Open Your Terminal

Your terminal (also called "command line" or "console") is where you type commands to talk to your computer.

• Mac: Open "Terminal" app
• Windows: Open "PowerShell" or "Command Prompt"
• VS Code: Press Ctrl+` (backtick) to open the built-in terminal

Step-by-Step Commands

Type each of these commands, one at a time, pressing Enter after each:

mkdir weather-app && cd weather-app && git init && npm init -y && mkdir css js && touch index.html css/styles.css js/weather.js js/ui.js js/config.js .env .env.example .gitignore README.md

What Just Happened?

Let me explain each command like you're 5:

mkdir [folder] — "Make a new box." This creates a folder on your computer.

cd [folder] — "Go inside the box." Now when you type commands, they happen inside this folder.

git init — "Start keeping a diary." Git will now track every change you make. If you break something, you can go back in time.

npm init -y — "Create an ID card for this project." It creates package.json with default settings. The -y means "yes to all questions."

touch [file] — "Create an empty file." Think of it as a blank piece of paper.

Verify It Worked

Type this command to see your files:

ls -la

The .gitignore File

Open .gitignore and add this:

node_modules/
.DS_Store
*.log
.env

Why? Because node_modules can be HUGE — thousands of files. We don't want to save all of them in Git. We can always recreate them with npm install.

Your First Git Commit

Now save everything to Git:

git add .
git commit -m "Initial project setup"

Congratulations! You just set up a project like a real developer.

Building the Application

Now let's build the application step by step. Follow each step in order.

Build Steps

1. Sign up for OpenWeatherMap API key
2. Create .env with API_KEY and .env.example without it
3. Build HTML: search form, weather card, forecast grid
4. Style with dynamic backgrounds (sunny=blue, rainy=gray)
5. Write fetchWeather(city) using fetch() API
6. Handle API errors (city not found, network failure)
7. Parse JSON response and extract needed fields
8. Write renderWeather(data) to update DOM
9. Write renderForecast(data) for 5-day cards
10. Add loading states and error messages
11. Test with different cities and error cases
12. Commit, deploy (hide API key for production)

How Each Step Works

Step 1 — Create the entry point

Every application starts with an entry file. This is the file that runs first when someone opens your app.

Think of it like the front door of a house. Everything starts when you walk through it.

Step 2 — Set up the structure

Before writing features, we set up the basic layout. This is like putting up the walls before painting them.

Step 3 — Add the main functionality

Now we add what makes the app actually DO something. This is the "brain" of the application.

Step 4 — Connect everything

We wire the pieces together. The HTML connects to CSS. The JavaScript connects to HTML. Everything talks to each other.

Step 5 — Test and fix

We try everything, find bugs, and fix them. Real developers spend 30% of their time testing.

Save and Test

After each step, save your files and refresh the browser. If something breaks, check the browser console (F12 → Console tab).

Commit after each major step:

git add .
git commit -m "Describe what you just built"

Pro Tip

Build in small steps. Don't write 100 lines and then test. Write 10 lines, test, fix, then write 10 more. This catches errors early when they're easy to fix.

Making HTTP Requests

Fetch GET

async function fetchUser(username) {
  const response = await fetch(`https://api.github.com/users/${username}`);
  if (!response.ok) throw new Error(`HTTP ${response.status}`);
  return await response.json();
}

Async/Await Pattern

async function searchUser() {
  const username = document.getElementById('search-input').value;
  const container = document.getElementById('result');
  container.innerHTML = '<div class="spinner">Loading...</div>';
  try {
    const user = await fetchUser(username);
    displayUser(user);
  } catch (error) {
    container.innerHTML = `<div class="error">${error.message}</div>`;
  }
}

POST Request

const response = await fetch(url, {
  method: 'POST',
  headers: { 'Content-Type': 'application/json' },
  body: JSON.stringify(data)
});

Handling Errors Gracefully

Error Types

Error	Cause	Handling
Network error	No internet	Show retry button
404	Not found	Show "not found"
403	Rate limit	Show warning
500	Server error	Show generic error

Loading States

async function fetchData() {
  container.innerHTML = '<div class="spinner">Searching...</div>';
  try {
    const response = await fetch(url);
    if (!response.ok) throw new Error('User not found');
    const data = await response.json();
    container.innerHTML = renderResult(data);
  } catch (error) {
    container.innerHTML = `<div class="error">${error.message}</div>`;
  }
}

localStorage Caching

function cacheUser(username, data) {
  localStorage.setItem(`user_${username}`, JSON.stringify({
    data, timestamp: Date.now()
  }));
}

Mistakes Everyone Makes

Every developer makes these mistakes. Knowing them ahead of time saves hours of debugging.

Mistake 1: Forgetting to Connect Files

<!-- WRONG — CSS is not linked, page looks ugly -->
<link rel="stylesheet" href="style.css">

<!-- RIGHT — file path matches actual location -->
<link rel="stylesheet" href="css/styles.css">

How to check: Right-click the page → Inspect → Network tab → look for red (failed) resources.

Mistake 2: JavaScript Before HTML

<!-- WRONG — JavaScript runs before HTML exists -->
<script src="app.js"></script>
<body>...</body>

<!-- RIGHT — JavaScript runs after HTML loads -->
<body>...</body>
<script src="app.js"></script>

Mistake 3: Not Using preventDefault()

// WRONG — page reloads when you submit
form.addEventListener('submit', () => {
  // This code runs, but then the page reloads!
});

// RIGHT — preventDefault stops the reload
form.addEventListener('submit', (e) => {
  e.preventDefault(); // Now the page doesn't reload
});

Mistake 4: Modifying State Without Re-rendering

// WRONG — changes data but screen stays the same
todos.push(newTodo);

// RIGHT — always update the screen after changing data
todos.push(newTodo);
render(); // Now the screen shows the new todo

Mistake 5: Not Handling Empty Input

// WRONG — adds empty tasks
addTodo(""); // Adds a blank todo

// RIGHT — check for empty input
if (text.trim()) {
  addTodo(text);
}

Mistake 6: Ignoring Errors

How to check for errors:

1. Press F12 in your browser
2. Click "Console" tab
3. Look for red text
4. Click on it to see what went wrong

If you see red text, DON'T IGNORE IT. That's the computer telling you something is broken.

Debugging Checklist

When something doesn't work:

1. Check the console — F12 → Console (red text = error)
2. Check the Network — F12 → Network (red lines = failed requests)
3. Check file paths — Are CSS/JS files in the right folder?
4. Check spelling — Typos in IDs, class names, function names
5. Check the basics — Is the server running? Is the URL correct?

The 5-Minute Rule

If you've been stuck for 5 minutes:

1. Stop
2. Re-read the error message
3. Search the error on Google/Stack Overflow
4. If still stuck, ask for help

Don't waste hours on something that might be a simple typo.

Testing Your App

A real developer NEVER assumes code works. They TEST it.

Why Test?

• Users will find every bug you missed
• Bugs found later cost 10x more to fix
• Testing gives you confidence to make changes

Manual Testing Checklist

Go through this checklist for EVERY feature:

□ Page loads without errors (check browser console — F12)
□ All buttons work when clicked
□ All forms submit correctly
□ Input validation works (empty, special characters)
□ Data saves and loads correctly
□ Responsive on mobile (resize browser)
□ No console errors
□ All links work
□ Loading states appear during API calls
□ Error messages show when things fail

How to Check for Errors

Press F12 in your browser. Click the "Console" tab.

• Empty = Good! No errors.
• Red text = Bad. Click it to see what went wrong.

Edge Cases to Test

Real users do weird things. Test these:

1. Empty input — What happens if you submit nothing?
2. Very long input — Paste a 1000-character string
3. Special characters — Type < > & " ' / 4. Rapid clicking — Click a button 10 times fast
4. No internet — Turn off WiFi and try
5. Refresh mid-action — Reload while something is happening

Browser Testing Tools

Tool	How to Open	What It Shows
Console	F12 → Console	JavaScript errors and logs
Network	F12 → Network	API requests and responses
Elements	F12 → Elements	Live HTML and CSS
Device Mode	Ctrl+Shift+M	Mobile screen simulation

Git Commit

After testing, commit your work:

git add .
git commit -m "Complete [project name] with testing"

Summary — Skills You Now Have

Technical Skills

1. Project Structure — You know how to organize files in folders
2. Git — You can initialize, add, commit, and push
3. Version Control — You can track changes and go back in time
4. HTML/CSS/JavaScript — You can build interactive web pages
5. DOM Manipulation — You can change what's on screen with code
6. Event Handling — You can respond to clicks, inputs, and other actions
7. State Management — You can track and update application data
8. Debugging — You can find and fix errors using browser tools
9. Testing — You can verify your app works correctly

Thinking Skills

1. Architecture — You planned the project BEFORE writing code
2. Problem Solving — You broke a big problem into small steps
3. Debugging — You systematically found and fixed errors
4. Documentation — You wrote notes for future you (and other developers)

The Pattern

Every frontend application follows this pattern:

State (data) → Render (draw) → Event (respond) → Update State → Render again

React, Vue, Angular, Svelte — they ALL do this. You just learned the fundamental pattern that powers the entire web.

What's Next?

Look at the next project in the roadmap. Each new project builds on what you learned here. The skills compound — every project makes you a better developer.

Remember: every expert was once a beginner who didn't give up.

Quick Reference

File Overview

• index.html: Weather app interface
• css/styles.css: Weather-themed styling
• js/weather.js: API calls and data handling
• js/ui.js: DOM updates
• js/config.js: API configuration
• .env: Secret API key

Setup Commands

mkdir weather-app && cd weather-app && git init && npm init -y && mkdir css js && touch index.html css/styles.css js/weather.js js/ui.js js/config.js .env .env.example .gitignore README.md

Common Patterns

// Select an element
const el = document.getElementById('myId');

// Add event listener
el.addEventListener('click', (e) => {
  e.preventDefault();
});

// Update the DOM
el.innerHTML = '<p>New content</p>';
el.textContent = 'Text only';

Debugging

F12 → Console     → Check for errors
F12 → Network     → Check API requests
F12 → Elements    → Inspect HTML/CSS
Ctrl+Shift+M      → Mobile view

Git Commands

git init                  # Start a repo
git add .                 # Stage all changes
git commit -m "message"   # Save changes
git push                  # Upload to GitHub