Browsing the web - MDN
This MDN primer is a beginner-facing web-literacy page about the ordinary things people touch before they ever write code: browsers, web pages, websites, web servers, web services, search engines, and the basic request-response loop that makes a page appear. Its main purpose is not technical depth. It is vocabulary cleanup. The source assumes that many newcomers use these words interchangeably, then shows why the distinctions matter if you want to understand what the web is actually doing.
Core Distinctions
The page's first job is to separate commonly confused things. A web browser is the software that retrieves and displays content. A web page is a single document. A website is a collection of related pages under one domain. A web server is the machine that hosts and serves those files. A web service responds to requests over the internet to perform a function or provide data. A search engine is a web service that helps you discover other pages. The source uses a library analogy to make the distinction concrete: the library is the server, each section is like a site, the books are pages, and the catalog is the search engine.
That distinction matters because beginner confusion usually starts at the interface layer. Someone opens Chrome, sees Google, and concludes that the browser and the search engine are the same thing. The source insists that they are not. One is software; the other is a service being accessed through that software. It also pushes a second cleanup that matters later: a website is not identical to the server that hosts it, and not every useful web-facing system is just a page someone reads. Some are services that resize images, return weather data, or handle logins.
The embedded screenshots make this distinction more memorable than the prose alone. One image isolates a full page URL in the browser bar, another isolates the shared domain/homepage view of a website, and a third shows Firefox opening directly to a Google search page. Together they visually separate page, site, and search engine instead of leaving those as abstract definitions.
How A Page Appears
The source then gives the simplest useful account of what happens when someone enters a URL. The browser sends a request to the server using HTTP, the server replies with the requested resource, and the browser may then discover more resources it also needs such as images, style sheets, or scripts. Only after those pieces arrive does the browser parse and render the result.
This is a stripped-down model, but it is a good first map because it replaces the vague idea that "the website loads" with a small sequence of actions. The page is especially useful here because it treats web literacy as a chain of ordinary events rather than as hidden magic. One request often becomes many requests: the first HTML file arrives, then the browser discovers that it also needs stylesheets, scripts, images, or other assets before it can finish the page.
Searching For Information
The last third of the source turns from web mechanics to search habits. The advice is practical: start with specialized documentation when you know the domain, widen to general search when needed, search with the programming language or exact error message when solving coding problems, and treat AI-generated answers as accelerants rather than authorities.
The source also lists specific search operators that most major engines support: "phrase in quotes" to require an exact string, term -exclusion to drop unwanted results, term1 OR term2 to broaden a search to either word, and intitle:word to require the word in the page title. These narrow abstract advice into actual syntax you can type. The source points to the documentation pages for Google, DuckDuckGo, and Microsoft Bing for the full operator sets.
Its caution about AI is straightforward and still important. AI can compress the search process, but it can also present outdated or subtly wrong answers with a lot of confidence. The source's real lesson is that search quality is part of judgment. You still need to know what you are asking, what kind of answer would count, and how to verify what comes back. That is why the page pairs ordinary browser literacy with search habits instead of treating them as separate skills.
Worth coming back to: this is one of those beginner pages whose real value is not the facts alone but the cleanup of false equivalences. Once browser, website, search engine, and server stop collapsing into one blur, later technical learning has a firmer floor.
Sources
raw/Browsing the web - MDN (ingested).md