CAAT Design System · User Guide
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.
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.
Each page is one HTML file in the main folder. The file name is the page title in lowercase with dashes instead of spaces.
| Page | File to edit |
|---|---|
| Home page | index.html |
| Members landing | members.html |
| Contact us | contact-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 protection | understand-inflation-protection.html |
| Pension Solutions | pension-solutions.html |
| any other page | same 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.
Tip: Uploading the file and asking for “the full updated file back” avoids copy/paste mistakes.
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.
After you've tested your changes:
Zipping the contents (step 2) means index.html sits at the top of the zip, so it's easy to find.
| What you see | Likely cause & fix |
|---|---|
| Page has no styling / looks like plain text | The 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” page | A file was renamed. Put its original name back. |
| The interactive tool stopped working | An edit to assets/js/prototype.js broke it. Restore that file from your backup. |
| Not sure what went wrong | Start over from the original zip and redo the change carefully. |
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.