What happens when someone opens a website
You don't need to code to sell websites and apps well. You do need a clear picture of the parts and how they fit together, so you can ask the right questions, understand the developers and explain things simply to clients. This course gives you that picture.
The journey of a web page
When someone types a web address into their phone, or taps a link, a lot happens in a second or two:
- The address. The person asks for a page such as www.example.com/prices. The "example.com" part is the domain name.
- Finding the server. Computers find each other by numeric addresses called IP addresses, not by names. So the browser asks the Domain Name System (DNS), a global directory, which IP address belongs to example.com.
- Connecting securely. The browser connects to that address. If the site uses HTTPS, the browser and the server set up an encrypted connection, and the browser checks the site's certificate.
- The request. The browser asks the server for the page.
- The response. The server, a computer usually run by a hosting company, sends the page back. It might send a ready-made file, or build the page on the spot using data from a database.
- Building the page. The browser reads the code it received (HTML for structure and content, CSS for appearance, JavaScript for behaviour), fetches the images and fonts, and draws the page on screen.
The later lessons in this section and the next zoom in on these steps.
The main parts, in one table
| Part | What it is | An everyday comparison |
|---|---|---|
| Domain | The name people type, such as example.com | The business's name on its sign |
| DNS | The system that turns names into server addresses | A directory that tells you which street a business is on |
| Hosting | The computers that store and serve the site | The building the shop rents |
| HTTPS | Encryption between the visitor and the site | A sealed envelope instead of a postcard |
| Front end | What runs in the visitor's browser | The shop floor customers see |
| Back end | What runs on the server: rules, data, accounts | The stockroom and the office behind it |
| Database | Where information is stored and organised | The filing cabinet |
Why sellers need this
- Better discovery calls. "Who manages your domain?" and "Where is your site hosted?" are questions that save the developers days later.
- Fewer surprises. You'll understand why moving a website can affect a client's email, and why a customer login adds cost.
- More trust. Clients relax when you explain things plainly instead of hiding behind jargon.
- Honest limits. You'll know when to say "That's a good question for the developers" rather than guessing.
The rule that doesn't change
This course helps you understand and explain. It doesn't make you the person who decides how something is built. As in all our work, the developers confirm the scope, the timeline and the price. If you're not sure, say you'll check.
How this course works
There are four sections: how the web works; what we build; time, cost and care; and proposals and scoping. Each lesson ends with an exercise. The final project has you scope a website project from discovery call notes, which our staff review. The course pairs well with "Selling tech services: the 15-day intern training".
Exercise
Explain out loud, in under two minutes, what happens when someone opens a website, using the everyday comparisons from the table. Then try it on a friend who doesn't work in tech, and note which part they found confusing.
This is a free preview. Enroll to open every lesson and track your progress.
Log in to enroll