Skip to Content
Impara: Learn

Impara: How the WWW and websites work

From typing a URL to seeing a page—Internet, WWW, domains, DNS, servers, HTTP, and what Qokit sits on top of.

How the WWW and websites work

La traduzione completa è in corso. Il contenuto seguente è temporaneamente in inglese; per i passaggi concreti apri il manuale utente.

When you type an address into a browser and press Enter, what actually happens?

We use websites every day—search, news, shopping, a company homepage, an office tool. Open a browser, enter something like https://www.example.com, and a full page appears in a few seconds. Keep asking, and the questions get sharper: How does the browser know where the site is? What is a domain? Where does the site live? What are DNS, servers, and HTTP doing? Why is one site fast and another slow?

Those questions are a solid starting point. Before you build with Qokit, it helps to set the tools aside for a moment and ask something simpler: how does a website work?

Are the Internet and the WWW the same thing?

Many people treat them as one idea. They are related, not identical.

The Internet is the global network that connects computers and devices—phones, servers, routers, data centers—through shared protocols. It is infrastructure for far more than websites: email, file transfer, messaging, video calls, games, cloud services, and the Web itself.

The WWW (World Wide Web) is an information system on top of the Internet: pages linked by hyperlinks. The Web runs on the Internet, but the Internet is not only the Web.

The Web sits on the Internet. A website is your public corner of the Web.

Website, web page, and homepage

These three get mixed up often.

A web page is one concrete page—/about, /products, /contact. A website is usually a set of related pages under one domain, with shared navigation. A homepage is the main entry—what you typically see at example.com.

So a homepage is not the whole site. It is one page among others.

Website
├── Home
├── About
├── Products
│   ├── Product A
│   └── Product B
├── Blog
└── Contact

What a browser does

Chrome, Safari, Edge, Firefox, and others are web browsers—the window into the Web. Two jobs matter most. First, they request resources for an address such as https://www.example.com. Second, they turn those resources into a page: parse HTML, CSS, JavaScript, images, fonts, and data, then render them on screen.

The short path is: user → browser → fetch resources → parse → render → page.

What a URL is

A URL (Uniform Resource Locator) is the address of a resource on the Web, for example:

https://www.example.com/products/camera?id=100

Broken down:

PartExampleRole
Protocolhttps://How the connection is made
Domainexample.comWhich site
Path/products/cameraWhich resource
Query?id=100Extra parameters

You do not need every URL rule yet—just this anatomy.

A URL names how to connect, which site, which resource, and any extra parameters.

Domains, IP addresses, and DNS

A domain name such as qokit.com is the memorable name. Machines find each other with IP addresses (for example 203.0.113.10). Remembering numbers is hard, so we use domains.

DNS (Domain Name System) is the Web’s address book: it helps turn qokit.com into the matching network address so the browser can find the right server. Real DNS is more involved; this lesson only needs the idea: domain → DNS → IP.

Servers, requests, and responses

A server is still a computer—usually built to run steadily and serve others. For a site it may return pages, handle APIs, query databases, store files, check login, process orders, accept forms, or return images.

The pattern is simple:

Browser → request → Server → response → Browser

HTTP and HTTPS

HTTP (Hypertext Transfer Protocol) is a shared set of rules for that conversation—“please send the homepage,” “here it is,” often as GET / and 200 OK plus content.

Most public sites use HTTPS: HTTP with transport protection (TLS). Passwords, contact details, forms, and orders should not travel unprotected. For a serious public site, HTTPS is baseline; the lock in the address bar usually signals that secure connection.

HTML, CSS, and JavaScript

Once resources arrive, the browser still needs structure, look, and behavior:

TechnologyRole
HTMLStructure and content
CSSAppearance and layout
JavaScriptInteraction and logic

HTML marks headings, paragraphs, and buttons. CSS sets color, type, spacing, layout, and responsive behavior. JavaScript handles cart counts, menus, forms, and loading more content. Together they are the core of the modern front end.

HTML structures content, CSS styles it, and JavaScript makes it interactive.

What happens after you press Enter

For https://www.example.com, a simplified path is:

  1. You enter the URL\
  2. The browser parses it\
  3. DNS is queried\
  4. The server IP is found\
  5. A connection is established\
  6. An HTTP/HTTPS request is sent\
  7. The server handles it\
  8. An HTTP response returns\
  9. The browser downloads HTML, CSS, JS, images, and more\
  10. The browser parses and renders\
  11. You see the page\

Main line to keep: URL → DNS → Server → HTTP → Resources → Browser → Page.

Main line: URL to DNS to server to HTTP to the browser rendering a page.

Modern stacks add CDN, cache, load balancers, APIs, databases, auth, analytics, and more. You do not need those yet—the spine above is enough for this lesson.

An everyday analogy

One way to hold the whole path in mind is to think of visiting a restaurant:

Web ideaAnalogy
URLRestaurant address
DNSMap / contacts that find the place
ServerThe restaurant
HTTPShared ordering rules
Request“One steak, please”
Backend / kitchenPreparing the order
DatabaseIngredients and order records
ResponseThe dish arriving
BrowserThe table where it is presented

Imperfect, but useful for a first mental model. After this section, we drop the metaphor and stay with the Web terms.

Static and dynamic sites

Static sites mostly serve relatively fixed resources (about.html, contact.html). They are often simple to host, fast to cache, and clear in security boundaries. Modern frameworks can still make rich static or pre-rendered sites.

Dynamic sites change by user or state—/account saying “Welcome, Alex” for one person and “Welcome, David” for another. Commerce, social, SaaS, admin tools, and account areas usually need that.

Most real sites mix both. Treat static and dynamic as a spectrum, not opposites.

Where Qokit fits

Building from scratch can mean design, HTML, CSS, JavaScript, frameworks, CMS, servers, domains, DNS, TLS, deploy, analytics, and ongoing maintenance.

Qokit does not rewrite Web fundamentals. It gathers design, build, publish, manage, and growth into one path—idea → plan → design → build → publish → manage → grow—while the underlying Web still works as above.

Draft, preview, then publish—one simple path from idea to a live page.

Tools help you finish faster. These concepts help you know what you are doing—especially with domains, SEO, publish, performance, security, and site management.

How the pieces connect

ConceptMeaning
InternetGlobal network infrastructure
WWWWeb information system on the Internet
WebsiteA site—usually many pages
Web pageOne page in a site
HomepageThe main entry page
BrowserSoftware that requests and renders Web content
URLAddress of a Web resource
DomainHuman-friendly site name
DNSResolves a domain to a network address
IP addressAddress of a device on the network
ServerSystem that provides site resources or services
HTTPCommon protocol for Web conversation
HTTPSHTTP protected with TLS
HTMLPage structure and content
CSSVisual presentation
JavaScriptInteraction and logic

What matters is how they connect, not memorizing every definition.

Easy to mix up

A website is not one page—a page is part of a site. A domain is closer to an address than to “the website itself”; owning a name is not the same as having a complete site. The server is infrastructure that hosts services, not the site as content. Buying a domain is a start, not the finish: you still need content, pages, hosting, DNS, and related setup. And using Qokit does not mean these ideas stop mattering. The product lowers complexity; the concepts still sharpen judgment on domains, SEO, publish, performance, and security.

Looking ahead

You do not need to write code for this step. Open a site you use often, read the URL, and spot https://, the domain, a path, and any ?query. Click a few pages and watch the URL change—/, /products, /about—and notice how that shape relates to the site’s structure.

When you are ready, continue with What a site needs.

Ultimo aggiornamento il

In questa pagina