Skip to Content
Aprender: Learn

Aprender: From www to how websites work

Learn the basics of the web—www, domains, pages, browsers, and publishing—so later site decisions make sense.

How the web and websites work

A tradução completa está em andamento. O conteúdo abaixo está em inglês por enquanto; para passos concretos, abra o manual do usuário.

Let’s align on what “website” means before anyone builds one.

People often talk past each other. One person means a domain on a card. Another means a homepage that looks finished on a laptop. Someone else has a review link open and treats that as live. Without a shared map, you get a domain that goes nowhere useful, a draft that should not have been public, or a team debating whether the site “is out” when only a few people can open the link.

You do not need to become a developer for this. You only need the pieces visitors actually use—so briefs, previews, and publishing use the same words.

A simple map

Think of three layers.

The internet is the network that connects devices. The World Wide Web (the “www” people say out loud) is how most of us use that network: linked pages in a browser. A website is your public corner of it—the pages under a name like example.com where visitors learn who you are, decide whether to trust you, and take a next step.

Same infrastructure, different roles. Mixing them up is how teams buy a domain and assume the work is done, or ship something unfinished because it looked fine in one browser.

A website is the inner layer. A domain name alone is not a finished site.

Domains, URLs, and HTTPS

Visitors remember the domain—example.com on ads, search results, and email signatures—not a long technical string. The www in www.example.com is optional; many sites work without it.

A URL is the full address of one page: usually https://, the domain, and a path such as /services or /contact. One domain can hold many pages.

HTTPS encrypts the connection. Modern browsers expect it. Without it they warn visitors, and trust drops before anyone reads a headline. That warning is often the first impression.

Browsers, pages, and screens

A browser requests a page and displays it. A page is one URL of content. A site is those pages plus shared navigation.

Most first visits happen on a phone. If the claim, contact path, and primary action only work on a large screen, the visit ends early—even when the desktop version looks polished. Visitors decide quickly: What is this for? Does it feel credible? Can I take the next step on this screen? Those questions return later in briefs and in Creator.

Draft, preview, and publish

This split prevents more rework than most design debates.

A preview link is for review. Only publish makes the address public.
MeaningWho can see it
DraftStill changingUsually private
PreviewA review link for you or the teamPeople with the link
PublishThe real public addressAnyone who can open it

Confusion here is expensive: treating a preview as live, buying a domain before anything is public, or sharing the wrong link and wondering why customers find nothing.

In traditional workflows, domains, hosting, and design often lived in separate tools. Even when a product unifies the path, the ideas still matter: the domain is the address, hosting is where the site lives and responds, pages are what people read, and publish is opening for business.

In Qokit

Qokit follows one main path: start from a brief, generate, edit in Creator, confirm with preview, then publish—and manage the site afterward. Editing, preview, and publish stay separate so you can keep refining, share a review link, and go public only when ready.

You do not need to bind a domain or click publish in this lesson. Get the vocabulary straight first. When you turn this into a real project, write the business brief, then use the manuals for the steps:

Next: What a site needs.

Última atualização

Nesta página