CAAT Design System · User Guide

Updating the Navigation UX Prototype

How to make changes to the prototype without the original author — using ChatGPT (or any AI assistant) to edit the files. No coding experience required.

Questions? Contact Russell Vance. For anything bigger than quick text edits, it's usually best to wait for Russell — see section 6.

1What this is

The prototype is a self-contained clickable website used for the navigation usability test. It's just a set of plain HTML files plus an assets folder (styles, scripts, fonts, images). There's nothing to install and no internet needed — a web browser opens it directly.

You have it as CAAT-navigation-prototype.zip. Unzip it anywhere, then double-click index.html to open it in your browser.

Because every page is a normal HTML file, you can change almost anything by editing the text of a file — and ChatGPT is very good at doing that for you.

2Before you start

3Finding the right file

Each page is one HTML file in the main folder. The file name is the page title in lowercase with dashes instead of spaces.

PageFile to edit
Home pageindex.html
Members landingmembers.html
Contact uscontact-us.html
Estimate your pension (+ the DBprime/DBplus tool)estimate-your-pension.html
Attend a learning session (webinars)attend-a-learning-session.html
Your pension payments (deposit dates)your-pension-payments.html
Understand inflation protectionunderstand-inflation-protection.html
Pension Solutionspension-solutions.html
any other pagesame naming pattern

Not sure which file? Open the page in your browser and look at the address bar — the file name is at the end of the web address.

4Making a change with ChatGPT

  1. Find the file for the page you want to change (section 3).
  2. Give the file to ChatGPT. Easiest way: click the paperclip / “+” in ChatGPT and upload the .html file. (Or open it in Notepad / VS Code, copy all the text, and paste it in.)
  3. Say what to change. Be specific and quote the exact words. Ask for “the complete updated file back.” (Template in section 7.)
  4. Save ChatGPT's result back into the file, keeping the .html extension.
  5. Test: double-click index.html, go to that page, and check it looks right.
  6. When you're happy, re-zip the folder (section 8) and share it.

Tip: Uploading the file and asking for “the full updated file back” avoids copy/paste mistakes.

5Common changes

Each recipe below = the file to open + what to tell ChatGPT.

Change wording on a page

File: that page's .html

“In this HTML file, change the sentence ‘OLD TEXT’ to ‘NEW TEXT’. Keep everything else exactly the same and give me the full file back.”

Add or edit a webinar (Attend a learning session)

File: attend-a-learning-session.html

“This page lists webinar cards. Add a new card titled ‘Estate planning basics’ dated ‘Nov 6, 2026 · 12:00 p.m. ET’, matching the style of the existing cards. Give me the full file back.”

Change a page's main heading

File: that page's .html

“Change the main heading (the <h1>) from ‘OLD’ to ‘NEW’. Full file back please.”

Update the pension deposit dates

File: your-pension-payments.html

“Update the deposit-dates table to these dates: [your list]. Keep the same table format. Full file back.”

Change the hero banner text (Home or a section page)

File: index.html (home), or the section file (e.g. members.html)

“Change the hero banner eyebrow / title / summary text to ‘…’. Full file back.”

Change the DBprime / DBplus tool's questions or answers

File: assets/js/prototype.js  (this is a script, not a page)

“This is the script for the plan-design tool. Change question 1 to ‘…’ with options ‘A / B / C’. Give me the full file back.”

⚠ After saving, test the tool: go to the Estimate-your-pension page and click all the way through it.

6Changing the menu, footer, or hero on every page

These repeat on every page, so editing one file is not enough. Two situations:

A) Simple relabel

For example, renaming the menu item “Members” to “For Members”. Use a “Find in all files / Replace in all files” tool so the change hits every page at once.

B) Bigger changes

Adding a brand-new menu item, reordering the sections, or adding/removing whole pages touches the desktop menu, the mobile menu, and needs new page files. It's fiddly and easy to make inconsistent by hand.

Please wait for Russell for these — he has a generator script that rebuilds all ~97 pages automatically and keeps them consistent.

7Copy-paste prompt for ChatGPT

I'm updating an HTML prototype (a clickable website). I'm giving you one HTML file. Please make this change: [describe the change and quote the exact text]. Do not change anything else — keep all the classes, links, scripts, and structure identical. Return the complete updated file so I can paste it back.

8Re-zipping the prototype for the UX team

After you've tested your changes:

  1. Open the prototype folder.
  2. Select everything inside itindex.html, the other pages, and the assets folder — not the folder itself.
  3. Right-click → Send to → Compressed (zipped) folder.
  4. Rename it, e.g. CAAT-navigation-prototype.zip.
  5. Share it. Recipients unzip it and double-click index.html.

Zipping the contents (step 2) means index.html sits at the top of the zip, so it's easy to find.

9If something looks broken

What you seeLikely cause & fix
Page has no styling / looks like plain textThe assets folder was moved, renamed, or deleted, or the file was saved with the wrong extension. Restore from your backup copy.
A link goes to a “file not found” pageA file was renamed. Put its original name back.
The interactive tool stopped workingAn edit to assets/js/prototype.js broke it. Restore that file from your backup.
Not sure what went wrongStart over from the original zip and redo the change carefully.

10Good to know: there are two copies

1. The offline bundle (this zip) — what the UX team runs on their own computers. Edit these files as described above. This is the one that matters for the test.

2. The design-system version at public/templates/ux-prototype/ (the internal site at localhost:3000) — the exact same pages, kept inside the CAAT Design System. If you're only handing out the zip, you can ignore this copy. If the test is run from the internal site instead, edit those files the same way.

Both are normally regenerated together by Russell's build script, so for anything beyond quick text edits, loop him in.