Curriculum
Course: WordPress and Client Websites
Login

Curriculum

WordPress and Client Websites

Text lesson

How a Website Actually Works

Learning objectives

  • Explain in your own words what a domain, hosting, files and a database each do for a website.
  • Describe what happens, step by step, between typing an address and seeing a page.
  • Distinguish a static site from a dynamic one and say what a content management system adds.
  • Name three common reasons a site is slow or goes down.
  • Draw a labelled diagram of how a website works for a business you know.

Introduction

Kemi Adeyemi graduated last year and now wants to build websites for small businesses in Lagos. At her first meeting, a restaurant owner asks, “If I pay you, where will my website actually live? On your laptop?” Kemi realises she cannot answer clearly. She has used websites every day, but never explained one.

You do not need code to understand how a website works. You need a good picture in your head, because every later decision in this course makes sense once you have it.

In the first ten minutes of this lesson you will do something practical: draw a diagram of a website for a business you know. By the end you will be able to explain to a client, in plain words, where their website lives and who looks after what.

Detailed explanation

A website is like a shop

Imagine a small shop in a busy market. Customers find it by its address. The shop stands on a plot of land that someone rents. Inside there are shelves, a counter and a back room with a filing cabinet that holds the records. A shopkeeper answers customers and fetches what they ask for.

A website has the same parts.

  • The domain is the address, for example example.com. It is a name people can remember and type. You normally pay to register one, and it is registered in someone’s name. That person or business is the owner.
  • Hosting is the plot of land and the building. It is a computer, called a server, that is switched on all the time and connected to the internet. Your website’s files live on it. Many sites share a server, like stalls in one market building.
  • The files are the shelves and the goods in the shop: the pages, pictures, the design, and the software that runs the site.
  • The database is the filing cabinet in the back room. It stores things that change or that must be looked up: the text of your pages, the list of blog posts, user accounts, settings, and in a shop, the orders.
  • The browser is the customer walking in. Chrome, Safari and Firefox are examples of browsers; you may use a different one on your phone.
  • The server software is the shopkeeper. It receives the request, fetches what is needed from the shelves and the filing cabinet, and hands it over.

Domain = address. Hosting = plot and building. Files = shelves and goods. Database = filing cabinet. Browser = customer.

What happens when you open a page

Suppose a customer types example.com into a phone browser.

  1. The browser needs to find the building. It asks a kind of internet phone book, which links the domain name to the server that holds the site. You will hear this called DNS. Think of it as someone looking up your shop’s address and giving directions.
  2. The browser sends a request to that server: “Please give me the home page.”
  3. The server software gets the request. If the page is ready-made, it simply hands it over.
  4. If the page must be put together, the server fetches the text from the database, combines it with the design from the files, and builds the page on the spot.
  5. The server sends the finished page back. The browser draws it on the screen.

All of this usually takes a moment. Two machines are involved, so slowness can come from either side, from the connection, or from the work the server must do.

Static and dynamic sites

A static site is like a printed menu pinned to the wall. Every page was prepared in advance and is handed over exactly as it is. Changing anything means preparing the page again by hand.

A dynamic site is like a cook who prepares each order fresh. When a visitor asks for a page, the server builds it from pieces: text from the database, layout from the files. This is why you can edit a sentence in a screen on a Tuesday and see it on the public site a moment later, without touching any file.

Neither is better in every case. A one-page leaflet site may be happy as static. A business that updates prices, adds news and wants a contact form usually benefits from a dynamic one.

What a content management system does

A content management system, or CMS, is ready-made software that builds pages from a database, stores users, protects logins and lets non-experts edit text. It gives the site owner a private screen (often called the dashboard or admin area) where they can add pages, change text and upload pictures without writing code.

In shop terms, a CMS is a shop-fitting system with a back office. WordPress is one such system, and the next lesson looks at it properly. The front of the site is what visitors see; the back is the private area where the owner works.

Why sites get slow or go down

  • A slow shopkeeper (the server). A crowded or weak server takes longer to answer.
  • Heavy goods (large files). A photo straight from a phone camera can be far bigger than the page needs. Big pictures take longer to travel, especially on mobile data.
  • Too much extra equipment. Every added tool, embedded video or widget gives the server or the browser more to do.
  • Out-of-date software. Software that is not kept up to date can break or be attacked.
  • A lapsed renewal. If the domain or the hosting is not renewed, the address or the shop stops working.
  • The visitor’s side. A weak phone signal or a power cut at the visitor’s end can look like “your site is down” when it is not.

Check the site from a different device or network before assuming it is broken.

Who owns what

Domain registration, the hosting account, the content and the design software are separate, and each can belong to a different person. A healthy arrangement is that the client owns the domain and the hosting account, and the builder is a named helper. A builder who holds everything in their own name can leave the business stuck.

A note on terms

WordPress.org is the home of the free, open-source WordPress software. Hosted WordPress services are separate companies that run WordPress for you and may offer different features and limits. When you meet a service, check what it includes before relying on it.

Key concepts

  • domain: the memorable web address, such as example.com, registered in an owner’s name.
  • hosting: space rented on an always-on server where the site lives.
  • browser: the app on the visitor’s device that asks for pages and displays them.
  • database: the organised store of text, settings, users and orders that a dynamic site reads from.
  • static site: a site whose pages are prepared in advance and delivered unchanged.
  • dynamic site: a site whose pages are put together on request from files and a database.
  • content management system (CMS): software that lets people create and edit a site through a private screen without coding.

Examples

Example 1: The journey of one page

A friend opens a tailor’s website in Ibadan on her phone. The domain points to a server running a CMS, which pulls the opening hours from the database, merges them with the design and sends the page. If the tailor edits the hours tomorrow, the next visitor sees the new ones.

Example 2: Which part is the problem?

A baker in Port Harcourt says, “My website is down.” Kemi asks three questions. Does it open on another phone with different data? If so, the first phone was the problem. If it fails everywhere, did the domain or hosting renewal lapse? If both are fine, did anyone update or install something just before it broke? She works through the shop part by part rather than guessing.

Example 3: A simple diagram

Screen description (yours may look different): a sheet of paper with a phone on the left labelled “Visitor’s browser”, an arrow to a box “Domain, the address”, then an arrow to a larger box “Hosting: the server” containing “Files” and “Database”. An arrow returns to the phone labelled “Finished page”. A figure labelled “Owner” has a dotted arrow to the server marked “Dashboard (private)”.

Guided exercise

This is your ten-minute quick win. You need paper and a pen, or the notes app on your phone.

  1. Choose a business you know: a salon, a pharmacy, a school, a church shop, a relative’s stall.
  2. Draw a box on the left for the visitor’s phone and write one thing a customer might want to do there, such as “find opening hours”.
  3. Draw boxes for the domain, the server, the files and the database. Label each with the shop analogy word too, for example “address” or “filing cabinet”.
  4. Add an owner figure and a dotted arrow showing the private dashboard.
  5. Under the diagram write two sentences: one on what is stored in the database for this business, and one on what could make the site slow.
  6. Expected result: a simple diagram with at least six labelled parts and arrows that show a request going out and a page coming back. It does not need to be neat.

Phone alternative: type the labels as a list in a notes app. Do not enter real passwords or private details.

Independent practice

Without looking back, write about 120 words for a client who has never used a website builder, answering “Where does my website live, and who looks after what?” Use at least three analogies. Then list three things that might make a site slow and the first thing you would check for each.

Self-check: your explanation should mention the domain, hosting and the owner’s private dashboard, and it should say who owns the domain and the hosting account. Your list should include at least one cause on the visitor’s side.

Common mistakes

  • Thinking the website lives on the builder’s laptop. It lives on a server.
  • Mixing up the domain and hosting, which are bought separately and can be with different companies.
  • Forgetting that domains and hosting must be renewed, and that someone must be responsible for it.
  • Treating the builder as the owner of everything instead of the client.

Troubleshooting

  • Symptom: the site opens on your phone but not on your friend’s. Likely cause: a problem on one connection or device. Fix: try a different network or device and ask the friend to try again later.
  • Symptom: the site fails for everyone and shows a message about the address. Likely cause: the domain is not renewed or is pointed wrongly. Fix: check the domain account and renewal date, then ask the domain company’s support.
  • Symptom: a page takes a long time to appear on mobile data. Likely cause: very large pictures or heavy embedded content. Fix: replace large images with smaller ones and remove anything not needed.

Knowledge check

  1. In the shop analogy, what does the domain represent, and what does hosting represent?
  2. What does a database hold on a dynamic site?
  3. Give one difference between a static site and a dynamic site.
  4. Why should you test a “down” site from another device before deciding it is broken?
  5. What does a content management system let a business owner do without coding?

Answers:

  1. The domain is the address people type; hosting is the plot of land and building where the site’s files and database are kept.
  2. The things that change or are looked up, such as the text of pages, posts, users, settings and, for a shop, orders.
  3. A static site delivers pages prepared in advance; a dynamic site builds each page when requested from files and the database.
  4. The problem may be on the visitor’s device or connection, such as weak signal, rather than on the server.
  5. Add pages, edit text and upload pictures through a private dashboard.

Summary

A website is like a shop: the domain is the address, hosting is the plot and building, the files are the shelves and goods, the database is the filing cabinet, and the browser is the customer. When someone opens a page, their browser looks up the address, asks the server for the page, and the server fetches and builds it. Static sites are prepared in advance; dynamic ones are built on request, and a CMS lets owners manage them without code. Slow or missing sites usually come from heavy files, extra tools, old software, lapsed renewals or the visitor’s own connection. The client should own the domain and the hosting account.

Additional resources

  • WordPress.org – https://wordpress.org – home of the free, open-source WordPress software; official site, link only, do not copy its text.
  • Learn WordPress – https://learn.wordpress.org – official free learning material; link only, check its current licence before reusing anything.
  • Wikipedia – https://www.wikipedia.org – search for “web hosting service”, “domain name” and “content management system”; licensed CC BY-SA 4.0, so attribution and share-alike apply.