How Websites Actually Work & Types of Websites

What a Website Actually Is

A website is a set of files that live on a computer connected to the internet, and that anyone with a browser can ask to see. Nothing more mysterious than that. The computer holding those files is called a server, and it stays on day and night so that the files are always available.

Before we go any further, three words need to be separated, because they are used loosely in everyday conversation and precisely in this phase.

A web page is one single screen — the home page, the about page, the contact page. A website is the collection of those pages, joined together by the menu, living under one name. So when someone says “visit our website”, they mean the whole thing; when they say “the pricing page”, they mean one screen inside it.

A web app is different in purpose, not in technology. A website is built mostly to be read and looked at; a web app is built to be used — to log in, save information, perform a task and come back. A restaurant's page that lists its menu is a website. The same restaurant's staff dashboard where orders come in is a web app. Both run in a browser; only one expects you to do something.

This distinction matters because it decides what a business should build first. A business that only needs to explain itself and take enquiries does not need a web app. A business whose customers need accounts, saved data and repeat tasks eventually does.

Every page has an address, called a URL. It looks like this: https://www.example.com/pricing. Read it from left to right and it tells you four things. The https tells you the connection is secure. The www.example.com is the domain name — the part you buy and own, which we cover in full later in this phase. The /pricing is the path, which points to one specific page inside the site. And everything after a question mark would be extra detail the page needs, like a search term.

Understanding the URL is the first practical skill of this phase, because almost every problem you will ever have with a website — a page that will not load, a link that goes to the wrong place, a domain that is not connected — is visible in the address bar if you know how to read it.

What Happens When You Open a Website

This is the part almost nobody sees, and it is the part that explains everything else — why a site can be fast or slow, why it can suddenly go down, and what hosting and domains are actually doing for you.

It happens in five steps, and the whole thing usually takes under two seconds.

You type a web address and press enter. Your browser — Chrome, Safari, Edge — takes that address and sends a request across the internet. In plain language, the request is saying: “please send me the files for this page.”

The browser does not know where those files are yet. It only knows the name you typed. So before anything else, it has to find out which computer on the internet holds them.

Every computer connected to the internet has a numeric address, called an IP address — something like 102.130.14.7. People cannot remember numbers, so the internet uses names instead. DNS, the Domain Name System, is the phone book that translates one into the other: you give it the name, it gives back the number.

This is why a domain name has to be connected properly before a website works. Buying the name is only half of it; you must also tell DNS which server to point it at. When people say “the domain is still propagating”, they mean this translation is still being updated around the world.

Now that the browser knows the address, it asks that server for the page. The server — the computer where the site's files live — finds them and sends them back. This is the moment we call hosting: hosting is simply the business of keeping your files on a server that is always on and always reachable.

What comes back is not one file but several: an HTML file that holds the content and structure, a CSS file that holds the styling, and a JavaScript file that holds the behaviour. If the site is a web app, the server may also send back data — prices, products, the user's own account details.

The browser receives those files and assembles them into the page you see. HTML lays out the content, CSS makes it look right, JavaScript makes it respond when you click. This is called rendering, and it is happening on your device, not on the server — which is why a heavy website feels slow on an old phone even when the internet is fast.

This is also why the same website can look different on a phone and a laptop. The files are the same; the screen doing the rendering is different. Good websites are built to adapt, which is what responsive design means.

The first load is not the end of the conversation. The moment you search, filter, log in or pay, the page sends another request and the server answers — usually without reloading the whole page. This is how a live chat, a search box and a payment confirmation all work instantly.

So a website is not a document you downloaded. It is an ongoing conversation between your browser and a server, and every button you press is a new sentence in it.

Frontend, Backend and the Database

Every website, however simple or complex, is split into two halves that do different jobs. The line between them is one of the most useful things you can learn in this phase, because it tells you what is easy to change, what is expensive to build, and where things go wrong.

The frontend is everything that happens on the visitor's device: the layout, the colours, the text, the buttons, the images, the animations, the forms. It is what you can see and touch. Frontend work is judged by how it looks, how quickly it appears and how easily a person can find what they came for.

Because it runs on the visitor's device, the frontend can be inspected by anyone. That is why a business must never put a password, a secret key or private customer information anywhere the frontend can reach it.

The backend runs on the server. It is where accounts are created, payments are verified, emails are triggered, and rules are enforced. When a customer pays, the backend is what confirms with the payment gateway that the money truly arrived before granting access.

The backend is the business logic — the part that decides what is allowed to happen. A visitor can never see it or change it directly, which is exactly the point: anything a customer must not be able to tamper with belongs here.

The database is where information is stored: customers, orders, payments, products, messages, progress. Without it, a website would forget every visitor the moment they closed the tab. With it, the business can greet a returning customer by name and know exactly what they bought last time.

Data is stored in an organised way — tables of records, each record with fields, much like a well-kept ledger. Good database design is what makes it possible to answer questions like “how many customers renewed this month” in an instant instead of counting by hand.

Put simply: the frontend asks, the backend decides, and the database remembers. When you tap “buy”, the frontend sends the order, the backend checks it and takes the payment, and the database stores the result so it is still there tomorrow.

In this program we build all three with Base44. You design the screens, and the platform gives you the backend, the database and the connections — which is exactly why you can build a working business system without writing code.

Static and Dynamic Websites

One more distinction before we look at the types, because it explains why two websites of the same kind can behave very differently.

Types of Websites

Websites are not one thing. Each type is built to do a different job, and choosing the wrong one wastes money. Here are the ten you will meet most often, with a real example of each.

Which Type Does a Business Actually Need?

Knowing the ten types is only useful if you can choose between them. The mistake almost every beginner makes is choosing by appearance — “I want something like that one” — instead of by the job the site has to do.

Ask one question first: what must this website do for the business right now? If the answer is “explain what we do and let people contact us”, that is a business website. If the answer is “convince strangers from an ad to buy one thing”, that is a landing page. If the answer is “let customers log in and manage their own orders”, only a web app will do.

Answer that honestly and the type chooses itself. Choosing by looks first is how businesses end up paying for a large, complicated site that does not do the one thing they actually needed.

Build up the ladder only as far as the business needs, and no further. A landing page comes first: it is cheap, fast, and proves whether people want what you are selling. Once demand is proven, a fuller website builds credibility and gives the business a proper home. A web app comes last, when customers genuinely need accounts, saved data and repeat tasks.

Climbing too fast is the expensive mistake. Building a full web app before anyone has paid for the offer means months of work and money spent on an idea nobody wanted.

Founders Asset did not begin as a platform. It began as a landing page: one offer, explained plainly, with a way to pay. That single page answered the only question that mattered at the time — would founders pay for funding opportunities gathered in one place?

Only after people paid did it grow into a membership website with accounts and a member area behind it. The type changed because the job changed — not because the design needed refreshing.

Practical

Worked Sample