What “the web” is, in one paragraph
Browsers ask servers for resources using HTTP(S). HTML describes structure, CSS handles presentation, and JavaScript adds behavior. Everything else (frameworks, build tools, databases) sits on top of those three.
HTML: semantics beats div soup
Use headings (h1–h6) as an outline, lists for actual lists, nav/main/footer to landmark a page. Alt text on images is both accessibility and good craft. Forms need labels and meaningful control names.
CSS: layout for real screens
Practice flexbox and grid with a mobile-first mindset. Understand specificity enough to debug “why won’t my style rule win?”—then reach for consistent naming instead of !important everywhere. Use relative units where your rubric expects responsive behavior.
JavaScript in the browser
The DOM is a tree you query and update. Events (click, input, keydown) should be handled without blocking the main thread on big work. Fetch data carefully: handle errors, show loading states, and never trust client-side validation alone for security.
Accessibility and performance (professional habits)
Keyboard navigation, focus styles, and color contrast are not extras—they are baseline quality. Compress images, lazy-load heavy media when appropriate, and measure with devtools rather than guessing.
How to build projects that score well
Start with a clear user flow on paper. Version control small commits. Write README notes: how to install, how to run, what browser you tested. Even beginner projects read as “real” when error messages are handled politely.
Quick review checklist
Run this on paper the night before an assessment—short answers, no peeking.
- Vocabulary: Five terms, defined in your own words.
- One strong example: Problem, diagram, quote+context, or map label your rubric would accept.
- Classic trap: What mistake shows up on every test—and what rule stops it?
- Connection: One sentence linking this topic to another unit from the same course.