How to Edit This Site

A step-by-step guide for adding pages, updating content, and publishing changes. No coding knowledge required.

The only three things you need to know

  1. Content lives in the content/ folder — each page is a single text file
  2. You edit those files in any text editor — even Notes or TextEdit works
  3. You publish by running three commands in Terminal

That’s it. Everything below is the detail.


Your content folder

Open the project folder and look inside content/. Every file you see is a page on the site:

content/
├── _index.md          ← Homepage
├── agent-ready.md     ← "Agent-Ready Architecture" page
├── booking.md         ← "Calendar Demo" page
├── contact.md         ← "Forms Demo" page
├── stack.md           ← "The Stack" page
└── why.md             ← "Why This Matters" page

The filename becomes the URL. stack.md becomes yoursite.com/stack/. agent-ready.md becomes yoursite.com/agent-ready/.


How a content file works

Open any .md file. You’ll see two parts:

Part 1 — The header (between the --- lines)

---
title: "How to Edit This Site"
subtitle: "A step-by-step guide for adding pages."
---

This sets the page title and subtitle. Change the text between the quotes. Don’t remove the --- lines.

Part 2 — The body (everything after the header)

This is your content, written in Markdown — a simple way to format text:

What you type What you get
## Section Heading A section heading
### Smaller Heading A smaller heading
**bold text** bold text
*italic text* italic text
[link text](https://url.com) A clickable link
- item one A bullet point
1. item one A numbered list
--- A horizontal line

That’s the full set of formatting you’ll need for most pages. Write naturally, add headings to break up sections, and Markdown handles the rest.


Adding a new page

Step 1 — Create the file

In the content/ folder, create a new file. Name it with lowercase letters and hyphens, ending in .md:

  • our-team.md → will become yoursite.com/our-team/
  • case-study.md → will become yoursite.com/case-study/
  • pricing.md → will become yoursite.com/pricing/

Step 2 — Add the header

Every page needs this at the top:

---
title: "Your Page Title"
subtitle: "A short description of what this page covers."
---

Step 3 — Write your content

Below the header, write your content using the Markdown formatting above. For example:

---
title: "About Our Team"
subtitle: "The people behind the work."
---

## Who we are

We are a small team based in Johannesburg, focused on
helping businesses adopt AI practically and responsibly.

## What we do

- AI literacy workshops and training
- Workflow automation and implementation
- Strategic AI advisory for leadership teams

Step 4 — Add it to the navigation (optional)

If you want the page to appear in the top menu, open hugo.toml and add an entry under [menu]:

[[menu.main]]
  name = "About"
  url = "/our-team/"
  weight = 7

The weight number controls the order — lower numbers appear first. Look at the existing entries to see the pattern.

Step 5 — Publish

Open Terminal, navigate to your project folder, and run:

cd ~/Projects/imbila-studio-demo
git add .
git commit -m "Add about page"
git push

The site rebuilds automatically. Your new page will be live within 60 seconds.


Editing an existing page

Step 1 — Find the file

Look in the content/ folder. The filename matches the URL:

  • Want to edit the homepage? Open _index.md
  • Want to edit the stack page? Open stack.md
  • Want to edit the booking page? Open booking.md

Step 2 — Make your changes

Open the file in any text editor. Change the text you want to change. Save the file.

Step 3 — Publish

Same three commands:

git add .
git commit -m "Update stack page"
git push

Write a short description of what you changed in the commit message — this creates a log of every change, which is useful if you ever need to undo something.


Previewing before you publish

If you have Hugo installed locally, you can see your changes before pushing them live:

cd ~/Projects/imbila-studio-demo
hugo server

Open http://localhost:1313 in your browser. The preview updates live as you edit files — you don’t even need to refresh.

When you’re happy with how it looks, publish with the three-command sequence above.

If you don’t have Hugo installed, you can install it with:

brew install hugo

Common tasks — quick reference

Change the site title

Open hugo.toml, find the title line, change the text.

Change a page title or subtitle

Open the page’s .md file, edit the title or subtitle in the header between the --- lines.

Check out the [Agent-Ready Architecture](/agent-ready/) page.
Visit [Imbila.AI](https://imbila.ai) for more information.

Add an image

Place the image file in the static/images/ folder, then reference it in your content:

![Description of image](/images/my-photo.jpg)

Remove a page

Delete the .md file from the content/ folder. If it’s in the navigation, also remove its entry from hugo.toml. Then publish.

Reorder the navigation

Open hugo.toml and change the weight numbers. Lower numbers appear first.


The publish sequence — commit it to memory

Every time you make any change, the process is the same:

git add .
git commit -m "Describe what you changed"
git push

That’s three commands. The site rebuilds automatically on Cloudflare. Changes go live in about 60 seconds.

If you make a mistake, you can undo your last change:

git revert HEAD
git push

This creates a new commit that reverses your previous one — safe and traceable.


What the files do — if you’re curious

File/Folder Purpose
content/ All page content (Markdown files)
content/_index.md Homepage content
hugo.toml Site config — title, navigation, settings
layouts/ HTML templates that control page structure
static/css/style.css Visual styling
static/images/ Image files

As a content editor, you’ll spend 95% of your time in content/ and occasionally hugo.toml for navigation changes. The layouts/ and static/ folders only need touching if you’re changing the site’s design or structure.


This page was written to prove the point: you just read a full guide, and the file that created it is a single text file called how-to-edit.md in the content folder.