Skip to content
Tutorials Center
My learning

Topics

Lesson 35 of 37 ยท Projects and Practice

Project: A Small Business Website

Plan and build a five-page business site in Joomla: structure, categories, menus, contact form, template style, SEO basics, access control and a quality checklist.

The best way to cement what you have learned is to build something complete. In this project you plan and set up a website for an imaginary neighborhood bakery, Corner Loaf: a home page, an about page, a menu of products, a news section and a contact page. It is the typical Joomla job, and every step uses features from earlier lessons.

Joomla cannot run on this site, so this project is a guided build: exact menu paths and settings to follow on your own installation (local or staging), plus a JavaScript stand-in that checks your site plan before you click anything. Planning on paper first saves hours of rework.

Step 1: Define goals and structure

Write down, in a sentence each: who visits, what they want to do, and what the business wants them to do. For Corner Loaf: visitors want opening hours, products and a way to order or ask; the bakery wants phone calls and email enquiries.

Then sketch the structure (the sitemap). Keep it shallow: two levels at most.

flowchart TD
    H["Home /"] --> A["About /about"]
    H --> P["Products /products"]
    P --> P1["Bread /products/bread"]
    P --> P2["Pastries /products/pastries"]
    H --> N["News /news"]
    H --> C["Contact /contact"]

The sitemap, which becomes the main menu.

Decide content types. Pages like About are single articles. Products and News are categories whose articles are listed (Category Blog or List). Contact uses the Contacts component with its form.

Step 2: Prepare the system

On staging, do these once (details in earlier lessons):

  1. System > Global Configuration: set the site name and a default meta description; set SEF URLs and URL rewriting on once your server supports it (SEO-Friendly URLs and Metadata).
  2. Configure mail and send a test mail.
  3. Enable the Content - Responsive Images and Media Action - Resize plugins if you want automatic image sizes (Images, Assets and Core Web Vitals).
  4. In Users, create an editor account for the owner in the Editor or Author group, and enable multi-factor authentication for yourself.

Step 3: Categories and articles

Under Content > Categories create Products with two children (Bread, Pastries) and News. Under Content > Articles write:

  • About us (category Uncategorised or a Pages category).
  • Three or four product articles with an intro image, short intro text and a read-more break.
  • Two news posts.

For each article set the alias, a meta description of 120 to 160 characters, and alt text on the image. Keep the Access level at Public for these.

Step 4: Menus

Create a Main Menu (Menus > Manage > New) and add items:

Item Menu item type Points to
Home Featured Articles (or a single article) marked as Default Home
About Articles > Single Article the About article
Products Articles > Category List or Blog Products category, subcategories shown
News Articles > Category Blog News category
Contact Contacts > Single Contact the contact record

Give each item a clean alias, set Browser Page Title and Meta Description in its tabs, and check the URLs match the sitemap. Create a Menu module showing Main Menu in the menu position.

Step 5: Contact form and modules

Create a Contact (Components > Contacts > New): name, email to receive messages, phone, address. Enable the Contact form and enable a captcha plugin to cut spam (Registration, Login and Privacy explains captcha options). Send yourself a test message.

Add modules in positions:

  • Custom module with opening hours and phone number in sidebar-right or the footer.
  • Latest Articles module showing news, in sidebar-right or bottom-a.
  • A Breadcrumbs module in breadcrumbs.
  • A Footer or Custom module with the address and a privacy policy link.

Step 6: Design

Open System > Site Template Styles, duplicate Cassiopeia - Default, set the logo, the site title, and brand colors; create a user.css for small changes (Cassiopeia and Template Styles). Check contrast of brand colors. If you need a changed layout for the product pages, create a child template and an alternative layout (Template Overrides and Child Templates) instead of editing core files.

Step 7: Check your plan

Before building, check the plan for obvious errors. This stand-in validates a site plan: unique aliases in the same parent, limited depth, and descriptions of the right length.

JS Validate a site plan

Press Run (or Ctrl + Enter) to see the console output here.

No output.

The two "Bread" items would produce the same URL, and the About description is far too short. The checker finds those mistakes in seconds, which is easier than discovering them as 404 errors later.

Step 8: Content quality checklist

JS Checklist progress tracker

Press Run (or Ctrl + Enter) to see the console output here.

No output.

Step 9: Access and handover

Extensions to this project

  • Add a second language following Multilingual Sites.
  • Add structured data for a local business using the Schema.org plugin.
  • Speed it up: Caching and Compression.
  • Replace a request for a plugin with a custom field on products (price, allergens).

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. Why plan the sitemap before building?

    Menu structure creates URLs; planning avoids restructuring and redirects.
  2. 2. Which menu item type fits a news section that lists articles?

    A Category Blog or Category List shows the articles of a category.
  3. 3. Which group suits a business owner who edits content?

    Give the least rights needed; Author or Editor can manage articles without system access.
  4. 4. What is a sensible length for a meta description?

    That range usually fits a search snippet and says something useful.

Summary

  • Start from goals and a shallow sitemap; the menu and URLs follow it.
  • Use categories for lists of articles, single articles for static pages and the Contacts component for the form.
  • Style with a duplicated template style, user.css and, if needed, a child template.
  • Give the owner a limited role, then back up, document and hand over.
  • Validate your plan before and your checklist after building.

Next: Project: A Members-Only Resource Site