Welcome to Your Website!

You're about to take control of your Just Track It website content. This guide will walk you through everything you need to know to confidently manage your site—no technical knowledge required.

Last updated: February 17, 2026

How to Use This Guide

This is your quick-start companion. We'll cover the essentials in four parts:

Understanding Your Website — How the site is designed and why it works
What is the CMS? — The simple control panel for your content
CMS to Website Map — Where your edits actually appear
Your Top 5 Tasks — The things you'll do most often

First time here? Read sections 1-3 to understand the big picture, then jump to section 4 to start making changes.

Need the full manual? There's a comprehensive 100+ page owner's manual available at /owners-manual.html with detailed documentation on every CMS feature. But start here first—this guide covers what you need to know right now.

1. Understanding Your Website

Before we dive into editing, let's talk about how your site works and why it's built the way it is. Think of this as understanding your business before you start changing the signs.

The Big Picture: Your website isn't just a brochure—it's a sales conversation that happens automatically, 24/7. It guides potential customers from "I'm curious about track days" to "I'm ready to register" without you needing to be there.

The 4-Stage Customer Journey

Introduce

Homepage: Quick value explanation

Clarify

Events, Tracks, FAQ: Answer questions

Build Trust

Partners, Testimonials, Stats: Prove credibility

Invite Action

Clear CTAs: Make next step obvious

How People Actually Use Websites (This Will Help You Edit Better)

Here's something important: people don't read websites like books. They scan, skim, and look for specific information. Understanding this will help you make better editing decisions.

What "Scanning" Means in Practice

When someone lands on your website, here's what actually happens in their brain:

First 3 seconds: They scan the headline and hero image to decide if they're in the right place
Next 10 seconds: Their eyes jump to section headings to see what's available
Next 30 seconds: They read bits and pieces of sections that sound relevant to their question
Decision point: They either click a button, leave, or dig deeper

Real Example: Imagine someone searching "track day events Ohio". They land on your homepage. In 3 seconds, they need to see "Track Day Events" in big text and a button that says "View Events". If the homepage said "Welcome to our community" with a "Learn More" button, they'd leave—even though the events page exists. The words and layout guide them.

Why This Matters for Editing

When you edit content in the CMS, always ask yourself:

"Is this headline clear in 3 seconds?" (Not clever, not vague—just clear)
"Can someone scan this paragraph?" (Short sentences, one idea per paragraph)
"Is the button text obvious?" ("Register Now" beats "Learn More" every time)

How Visitors Move Through Your Site (The Customer Journey)

Your website is designed as a guided conversation with four stages. Let's walk through what happens at each stage:

Stage 1
Introduce

→

Stage 2
Clarify

Stage 3
Build Trust

→

Stage 4
Invite Action

Stage 1: Introduce (Homepage Does This)

What happens: Someone lands on your site for the first time. They might know about HPDE, or they might be completely new.

What the page does:

Big headline explains what you do in 5 words: "Professional Track Day Events"
Subtitle adds detail: "Safe, instructed HPDE events at premier racetracks"
Buttons give clear next steps: "View Events" or "Get Started"
"Why" cards answer: "Why should I choose Just Track It?"

Why it's structured this way: New visitors need clarity fast. The homepage does one job: help them understand what you offer and where to go next. It doesn't try to explain everything—just enough to build confidence.

Stage 2: Clarify (Events, Tracks, FAQ, Requirements)

What happens: The visitor is interested but has questions: "When are events? Which track? What do I need? How much does it cost?"

What these pages do:

Events page: Shows upcoming dates, tracks, pricing—everything needed to pick an event
Track pages: Explains each racetrack (location, layout, difficulty, nearby hotels)
FAQ page: Answers common questions so they don't have to email you
Requirements page: Lists exactly what they need (license, helmet, vehicle requirements)

Why it's structured this way: Uncertainty kills sales. These pages remove every possible obstacle by answering questions before they're asked. Notice how event pages repeat the same layout—that's intentional. Once someone learns how to read one event, they can quickly compare others.

Real Example: Someone clicks "View Events" from the homepage. They land on a list of upcoming events. Each event card shows the same information in the same order: date, track, price, status. They can scan 6 events in 10 seconds because the pattern repeats. If each event used a different layout, they'd have to re-learn how to read each one.

Stage 3: Build Trust (Partners, Testimonials, Media, Stats)

What happens: The visitor is considering registering, but they're thinking: "Is this legit? Have other people done this? Are these events actually safe and professional?"

What these sections do:

Partner logos: "They work with reputable brands I recognize"
Testimonials: "Real people have done this and loved it"
Media coverage: "News outlets have covered this organization"
Stats: "They've run 155+ events since 2013 with thousands of participants"

Why it's structured this way: People don't trust claims—they trust proof. These elements don't sell; they remove doubt. That's why testimonials include real names (not anonymous), stats are specific (not "many events"), and partner logos are recognizable brands.

Stage 4: Invite Action (Clear CTAs Throughout)

What happens: The visitor is ready to take the next step, but they need to be told exactly what to do.

What the site does:

Every page has clear buttons: "Register Now", "View Event Details", "Contact Us"
Buttons use action words (not vague words like "Learn More")
Registration buttons go directly to the registration platform
CTAs are repeated in logical places (end of sections, end of pages)

Why it's structured this way: Even motivated visitors need to be told what to do next. The site removes friction by making the next step obvious, specific, and easy.

Key Takeaway: Every page, every section, and every word on your site exists to move someone through these four stages. When you're editing, ask yourself: "Does this introduce, clarify, build trust, or invite action?" If it doesn't do one of those four things, consider cutting it or rewriting it.

Why Patterns Repeat Across Pages

You might notice that many pages look similar—same hero layout, same section structure, same button styles. That's not laziness; it's intentional design.

The Pattern Recognition Principle

Human brains love patterns. When someone sees the same layout twice, their brain says "I know how this works" and they move faster. Here's what this means for your site:

All event pages use the same layout: Date at top, pricing in a box, track info in the same spot. Someone who reads one event page can instantly read all of them.
All track pages use the same structure: Hero image with track name, stats in a grid, features list, accommodations. Once learned, it's reusable.
All buttons look the same: Red buttons mean "primary action" (register, view details). White buttons mean "secondary action" (learn more, go back). Users learn this once and apply it everywhere.

Real Example: Imagine you're shopping on Amazon. Every product page has the same layout: image on left, title and price at top, "Add to Cart" button in the same spot. You don't think about it—you just know where to look. If every product page was different, shopping would be exhausting. Same principle applies to your site.

What This Means When You're Editing

Don't break the patterns. When you edit an event page, don't rearrange the sections or change how pricing is displayed. Users have learned the pattern. Breaking it makes your site harder to use.

Do keep the same tone and format. If one FAQ answer is 2 sentences, try to keep other answers around 2 sentences. If event titles are "Track Name + Month + Year", keep that format consistent.

What Pages You Have (About 35 Total) and What They Do

Your website has about 35 pages/routes organized into 7 categories. Each category serves a specific purpose in the customer journey. Understanding this will help you know which page to edit when content needs updating.

Category	Key Pages	Purpose & When People Use It
Core Marketing	Home, About, Contact, Partners	Purpose: First impression and general information When used: First-time visitors, people researching your organization
Events	Events list page + individual pages for each event	Purpose: Primary conversion point (where people decide to register) When used: High-intent visitors ready to pick a date and sign up
Tracks	Track overview + 5 individual track guide pages	Purpose: Help customers choose the right venue and learn the layout When used: Before registration (deciding which track) and after registration (preparing for event)
Education	Getting Started, Run Groups, FAQ	Purpose: Lower the barrier for new/nervous drivers When used: New drivers researching what HPDE is and whether they're ready
Programs	Ladies Intro, Gift Cards, Track Pass, Referral, Instructors	Purpose: Expand offerings beyond basic events When used: People looking for specific programs or added value
Requirements	Requirements, Media	Purpose: Set expectations (what you need) and build credibility (press coverage) When used: Before first event (checking requirements) or researching reputation
Legal	Privacy Policy, Terms of Service, cancellation policy content	Purpose: Protect the business and inform customers of policies When used: Rarely clicked unless someone has a specific question about privacy or refunds

Remember: Every page exists to either answer a question, build trust, or invite action. When you edit content, keep asking: "Does this move someone closer to registration, or does it create confusion?"

2. What is the CMS?

CMS stands for "Content Management System." But let's skip the jargon and talk about what it actually does for you.

The Absolute Basics: What Problem Does a CMS Solve?

Imagine you need to update an event date on your website. Without a CMS, you'd need to:

Find the file that contains that page's code
Open it in a code editor
Search through hundreds of lines of code to find the right date
Change the date in multiple places (events list, event detail page, homepage highlights, calendar)
Make sure you didn't accidentally break any code syntax
Upload the changed files to the web server
Hope nothing broke

With a CMS, you:

Go to the Events section
Click on the event
Change the date in a simple form field
Click Save
The date updates everywhere automatically

Bottom line: The CMS is a control panel that lets you edit your website content in plain English forms, without touching code. Think of it like the difference between editing a Word document (easy) vs. editing raw HTML code (hard and risky).

The Difference: Code vs. CMS

❌ Without CMS (Raw Code)

<section class="event">

  <div class="event-header">

    <h2>Road Atlanta Feb 2026</h2>

    <span class="event-date">

      2026-02-14</span>

  </div>

  <div class="pricing">

    <p class="price">$495</p>

  </div>

</section>

Risk: One wrong bracket breaks the entire page. You need to find the right file, know HTML syntax, and update multiple locations manually.

✅ With CMS (Simple Forms)

Event Name

Event Date

Base Price

Easy: Fill in the form fields like you would in any web form. No code knowledge needed. Changes update everywhere automatically.

The House Analogy (This Makes It Click)

Think of your website like a house:

The structure: Foundation, walls, roof, plumbing, electrical = Built by developers
The contents: Furniture, decorations, what's on the walls = Managed by you through the CMS

The CMS is like having light switches, thermostats, and locks that let you control what's inside your house without needing to rewire the electrical system or knock down walls.

Real Example: When you update an event title in the CMS, you're rearranging furniture. When a developer adds a new feature like a "Ladies Program" page, they're building a new room. You control the contents; they control the structure.

What the CMS Lets You Control (and What It Doesn't)

Here's a clear breakdown so you know what's in your control:

✅ What You CAN Control Through the CMS

All text content (event descriptions, page titles, button labels)
All dates and prices (event dates, pricing tiers)
Images (event photos, track images, partner logos)
Page-specific content (homepage hero text, contact form labels)
Repeatable content (events, FAQ questions, track information)
Navigation link labels and destinations (header and footer links)
Which events are "featured" on the homepage
Event status (open, selling fast, sold out)

❌ What You CANNOT Control Through the CMS (Developer Territory)

Page layout and design (colors, fonts, spacing, where sections appear)
How the site works (forms submitting, navigation behavior, mobile menu)
Creating entirely new pages (that requires building the page structure first)
Adding new CMS fields (e.g., if you want events to have a new "parking info" field)
Changing how the site looks (making buttons blue instead of red, changing font sizes)

The Golden Rule: If it's about words, dates, prices, or images, you can change it in the CMS. If it's about layout, design, or how things work, that's developer territory.

How Your Specific CMS Works (Keystatic)

Your CMS is called Keystatic. Here's what makes it different from traditional CMS tools:

Traditional CMS (Like WordPress)

Content is stored in a database
You edit content through a web interface
When you click "Publish," changes go live immediately
Risk: One wrong click can break the live site instantly

Keystatic (Your CMS) - Safer Approach

Content is stored as files in a code repository (like a history-tracked filing system)
You edit content through a web interface (just like WordPress)
When you click "Save," changes go to a preview version first
You review the preview and decide when to publish
Benefit: You can't accidentally break the live site—there's always a preview step

The Safety Net: With Keystatic, there's no "Oops, I broke the site" moment. Every change gets previewed before it goes live. Think of it like having an "Undo" button before anything matters.

Your CMS Dashboard

Events

Road Atlanta
Feb 14-15, 2026 · From $341.99

Barber Motorsports Park
Aug 15-16, 2026 · From $323.99

Atlanta Motorsports Park
Apr 25, 2026 · From $296.99

How Your CMS Is Organized: Collections vs. Singletons

Keystatic organizes content into two types of areas. Understanding this distinction will make navigation much easier.

Type 1: Collections (Think: Filing Cabinets with Multiple Folders)

Collections are for content where you need multiple entries of the same type. Think of them like filing cabinets where each drawer holds the same kind of thing, but you can have as many as you want.

Real-World Analogy: Your Events collection is like a filing cabinet labeled "Track Day Events." Inside, you have one folder for each event: Road Atlanta Feb 2026, Barber Aug 2026, etc. Each folder contains the same type of information (date, track, price, run groups), but the details are different.

You have 6 collections:

Collection Name	What It Contains	How Many Entries?
Events	All your track day events	10-20 per year (you add/remove as needed)
Tracks	The 5 racetracks you visit	5 total (rarely changes)
Track Guides	Detailed driving guides for each track	5 total (one per track)
Partners	Sponsor and partner organizations	10-15 (add/remove as partnerships change)
FAQ	Questions and answers organized by category	5-10 categories, each with multiple Q&A pairs
Run Groups	Driver skill level classifications	7 total (Open, Novice Instructed, Novice Solo, Intermediate 1, Intermediate 2, Advanced, Instructor)

When to use Collections: If you're thinking "I need to add another ___" (event, partner, FAQ question), you're working with a collection. Collections let you create, edit, and delete individual entries.

Collections = Multiple Entries

📅 Events Collection

Event Name	Track	Date	Price	Status
Road Atlanta	Road Atlanta	Feb 14-15, 2026	From $341.99	Open
Barber Motorsports Park	Barber Motorsports Park	Aug 15-16, 2026	From $323.99	Open
Atlanta Motorsports Park	Atlanta Motorsports Park	Apr 25, 2026	From $296.99	Open

Click any row to edit that event's details

Type 2: Singletons (Think: One-Time Settings Panels)

Singletons are for content that appears in only one place or needs to be the same everywhere it appears. You don't create multiple entries—there's just one set of settings.

Real-World Analogy: The Home Page singleton is like the control panel for your homepage. There's only one homepage, so there's only one set of settings. You don't create multiple homepages—you just edit the one that exists.

You have 20 singletons (here are the most important ones):

Singleton Name	What It Controls	Impact Level
Home Page	Entire homepage: hero text, sections, buttons, stats, testimonials	High visibility
Contact Page	Contact form labels, dropdown options, success/error messages	Medium
Navigation	Header/footer link data across ALL pages	Site-wide impact
Company Info	Business email, mission statement, contact form endpoint	Critical (affects form submission)
About Page	Your story, values, track cards on About page	Medium
Getting Started Page	Beginner guide sections and content	Low (rarely changes)
Ladies Intro Page	Ladies program landing page content	Medium
Requirements	Driver and vehicle requirements	Low (rarely changes)
Testimonials	Customer quotes on homepage	Medium
...plus 11 more for programs, policies, and settings

When to use Singletons: If you're thinking "I need to change the wording on the ___" (homepage, contact form, about page), you're working with a singleton. Singletons control specific pages or site-wide settings.

Important: Changes to Navigation or Company Info affect multiple pages across the site. Always double-check these changes carefully in the preview before publishing.

Singletons = One Form with Many Sections

🏠 Home Page Settings

▼ Hero Section

Badge Text

Title Line One

Title Accent Line

▼ Why Choose Us Section

Section Heading

▼ Testimonials Section

Section Title

Scroll down to edit more sections. All sections control the same homepage.

Collections vs. Singletons: The Simple Decision Tree

Question:
Do I need multiple items of this type?

→

YES
It's a Collection
(Events, Partners, FAQ)

Question:
Is this a one-time setting or site-wide?

→

YES
It's a Singleton
(Home Page, Navigation)

How Changes Get Published (The "Preview Before Live" Workflow)

Here's the part that makes Keystatic safer than traditional CMS tools: nothing goes live until you've seen it and approved it. Let's walk through what actually happens when you make a change.

The 5-Step Publishing Workflow (In Plain English)

Step 1: Make Your Edit

You open the CMS, go to the content you want to change (e.g., an event), and edit the fields. Click "Save".

What's happening behind the scenes: Your changes are saved as a draft copy, not directly on the live site.

Step 2: Create a Publish Request (PR)

After saving, you create a publish request (also called a Pull Request, or PR). This is a formal way of saying "I want to publish these changes." The CMS will walk you through this.

What's happening behind the scenes: The system creates a proposal to merge your draft changes into the live site. This proposal includes a preview link so you can see what it will look like before publishing.

Step 3: Preview Your Changes

The Pull Request includes a link to a preview site. This is a temporary copy of your website with your changes applied. You can click around, test it on mobile, and make sure everything looks right.

What's happening behind the scenes: The system builds a temporary version of the site with your changes, hosts it at a special URL, and lets you interact with it. The live site is completely untouched.

Step 4: Automated Quality Checks Run

While you're previewing, the system automatically runs a series of checks to make sure your changes won't break anything. These check for things like valid dates, required fields, and proper formatting.

What's happening behind the scenes: Automated tests run to catch common mistakes (missing required fields, broken links, invalid date formats). If something's wrong, you'll see a red X and can fix it before publishing.

Step 5: Merge to Publish Live

Once you've verified the preview looks good and all checks pass, you click "Merge" to publish. Your changes go live within a few minutes.

What's happening behind the scenes: Your draft changes get merged into the main site, the site rebuilds with your changes, and the new version goes live automatically.

The 5-Step Publishing Workflow

Make Your Edit

Open the CMS, find the content, edit the fields, click "Save"

↓

Create Pull Request

Click "Create PR" to propose publishing your changes

↓

Preview Changes

Click the preview link to see your changes on a test site

↓

Automated Checks

System verifies required fields, date formats, and link validity

↓

Merge to Publish

Click "Merge" to make your changes live in minutes

Why This Workflow Exists: The Safety Net

The main benefit: You literally cannot break the live site. Even if you make a mistake in the CMS, it only affects the preview. If the preview looks wrong, you fix it before merging. If you forget to fill in a required field, the automated checks catch it. The live site stays protected.

Real Example: Let's say you're updating an event and accidentally delete the registration URL. When you create the Pull Request, the automated checks will see that the registration URL is missing (it's a required field) and show you an error. You fix it in the preview, re-check, and then merge. The live site never saw the mistake.

What Happens If You Need to Cancel?

Changed your mind? No problem. Before you click "Merge," you can:

Edit the draft again: Make more changes and create a new preview
Close the Pull Request: Discard your changes entirely and start over
Ask for a review: Tag someone else to review your changes before you merge

Bottom line: Think of this workflow like having a "Save Draft" button on steroids. You make changes, preview them in a safe sandbox, verify they're correct, and only then do they go live. This is why you can edit with confidence—mistakes don't propagate to the live site.

Pull Request Page (Ready to Publish)

Update Barber event pricing

content/update-pricing → main

🔍 Preview Your Changes

https://preview-update-pricing.justtrackit.pages.dev

Click to see how your changes will look before publishing

✅ All Checks Passed

✓ Build successful (2m 15s)

✓ Content validation passed

✓ Required fields verified

✓ No broken links detected

Preview looks good and all checks passed? Click "Merge Pull Request" to publish.

Recap: What Is the CMS?

Let's bring it all together:

✅ The CMS is a control panel for editing your website content without touching code
✅ It's organized into Collections (repeatable content like events) and Singletons (one-time settings like the homepage)
✅ Every change goes through a preview workflow before going live
✅ You can edit with confidence because you can't accidentally break the live site
✅ Automated checks catch common mistakes before they reach visitors

Ready to see it in action? The next section shows you exactly where your CMS edits appear on the live website, so you know what you're controlling.

Where Do Your Edits Actually Appear?

Now let's see what happens when you edit content - here's how CMS changes appear on your actual website:

Example: Editing an Event in the CMS

← CMS: "title"

Road Atlanta

← CMS: "location" → Braselton, GA

From $341.99 ← lowest available price

Pricing

2 Days Registration$649.99

2 Days w/ Track Pass$584.99

Saturday Only$399.99

Sunday Track Pass$341.99

+ Instructor Fee (Novice)$100

← All from CMS: eventProfile → pricing fields

← CMS: "registrationUrl"

Register Now

This is what visitors see on /events/road-atlanta-feb-2026.html after you edit the event in the CMS.

Example: Homepage Hero Editing

← CMS: Home Page → Hero → badgeText

Professional Track Days Since 2013

← CMS: titleLineOne

Your Car.

← CMS: titleAccent

Our Tracks.

← CMS: subtitle

HPDE track days at the Southeast's best tracks—5 run groups, in-car instruction, and an impeccable safety record since 2013.

← primaryButtonText

← secondaryButtonText

This is what visitors see on your homepage after you edit Home Page → Hero in the CMS.

Example: Events List Page

Upcoming Track Day Events

← CMS: status = "open"

← CMS: title

Barber Motorsports Park

Birmingham, Alabama

← CMS: dates.displayShort

Aug 15-16, 2026

← "From" = lowest pricing tier

From

$323.99

Road Atlanta

Braselton, Georgia

Feb 14-15, 2026

From

$341.99

Atlanta Motorsports Park

Dawsonville, Georgia

Apr 25, 2026

From

$296.99

This is what visitors see on /events.html. Each event you create in the Events collection appears as a card. The "From" price is automatically calculated as the lowest available pricing tier.

Key Takeaway: When you edit in the CMS, you're changing real content that real visitors see. The annotations above show exactly which CMS field controls which part of your website. The next section gives you a complete map.

3. CMS to Website Map

This is the most important section: where do your CMS edits actually appear on the website?

Quick Reference: Collections

CMS Collection	Where It Appears	What You Control
Events	`/events.html` (list) `/events/[slug].html` (detail) Homepage highlights	Event dates, pricing, track, run groups, registration link, status (open/sold out)
Tracks	`/tracks.html` Track references on event pages	Track name, location, stats (length, turns), features, nearby hotels
Track Guides	`/tracks/[trackId]/guide.html`	Long-form driving instructions, turn-by-turn guidance
Partners	`/partners.html` Homepage partner strip	Partner logos, descriptions, special offers, website links
FAQ	`/faq.html`	Questions, answers, category organization
Run Groups	`/run-groups.html` Event pages Getting Started page	Group names, colors, experience levels, passing rules, comparison table

Quick Reference: Important Singletons

CMS Singleton	Where It Appears	What You Control
Home Page	`/` (homepage)	Hero title/subtitle, "Why" cards, buttons, section text, stats, testimonials
Contact Page	`/contact.html`	Form field labels, subject dropdown options, success/error messages
Navigation	All pages (site-wide)	Header/footer/mobile link labels and destinations (menu grouping/order stays fixed for consistency)
Company Info	About page Contact page Footer	Email, mission statement, highlights, contact form settings
Testimonials	Homepage testimonials section	Customer quotes, author names, featured media link

Important: Changes to Navigation or Company Info affect multiple pages across the site. Always double-check these changes in the preview before publishing.

The Most Common Question: "Where Do I Edit This?"

When you see something on the website you want to change, ask yourself:

Is it about a specific event? → Go to Events collection
Is it about a specific track? → Go to Tracks collection
Is it a question/answer? → Go to FAQ collection
Is it on the homepage? → Go to Home Page singleton
Is it in the header or footer? → Go to Navigation singleton
Is it company contact info? → Go to Company Info singleton

4. Your Top 5 Tasks

These are the five things you'll do most often. Master these, and you'll handle 90% of your content needs.

1Create or Edit an Event

Why you'll do this: Adding new track days and updating existing events is your most frequent task.

Where to go: CMS → Events collection → Create (or select existing event)

What you need:

Event name (e.g., "Road Atlanta Feb 2026")
Track (select from dropdown)
Start and end dates (use date picker)
Pricing (base price, instructor fee, co-driver fee)
Run groups available (checkboxes—must include "Instructor")
Registration URL (link to external registration platform)
Status: Open | Selling Fast | Sold Out

Step-by-step:

Open Events and click Create
Fill in the event name and URL slug (automation can help generate this)
Select the track from the dropdown
Pick start/end dates with the date picker
Enter pricing details (base, instructor fee, co-driver fee)
Select run groups available (must include "Instructor", cannot include "Open")
Add registration URL (must start with https://)
Set status (open/selling fast/sold out) and featured checkbox
Click Save
Create a Pull Request and preview your changes
Check the events list page AND the individual event detail page
If everything looks good, merge to publish

After you save: Always verify BOTH pages—the events list (/events.html) and the event detail page (/events/[slug].html). Make sure dates, pricing, and registration links all look correct.

2Update Homepage Hero Text

Why you'll do this: Seasonal messaging, special promotions, or emphasizing different value propositions.

Where to go: CMS → Home Page singleton → Scroll to Hero section

What you control:

Badge text (small tag above title)
Title line one
Title accent line (highlighted in color)
Subtitle
Primary button text and link
Secondary button text and link

Step-by-step:

Open Home Page singleton
Scroll to the Hero section
Edit the title, accent line, and subtitle
Update button text/links if needed
Click Save
Create Pull Request and preview
Take a screenshot of before/after for comparison
Get stakeholder approval (this is high-visibility!)
Merge to publish

High-visibility change: The homepage hero is what EVERY visitor sees first. Always preview carefully and get a second opinion before publishing hero changes.

3Add or Update FAQ Questions

Why you'll do this: Customers ask new questions, policies change, or you want to clarify existing answers.

Where to go: CMS → FAQ collection → Select category or create new

What you control:

Category name (e.g., "Getting Started", "Registration", "On-Track", "Safety")
Question/answer pairs within each category

Step-by-step:

Open FAQ collection
Select an existing category or create a new one
Click into the Questions array
Add a new Q&A pair or edit an existing one
Write the question in the customer's voice (how they'd actually ask it)
Write a clear, direct answer (1-3 sentences for simple questions)
Click Save
Preview the FAQ page (/faq.html)
Check that the accordion behavior works (click to expand/collapse)
Test on mobile—make sure it's readable
Merge to publish

Pro tip: Keep answers short and scannable. If an answer needs more than 2 short paragraphs, consider breaking it into multiple questions or linking to a dedicated page.

4Update Contact Form Settings

Why you'll do this: Change form field labels, add new subject options, or update success/error messages.

Where to go: CMS → Contact Page singleton → formFields section

What you control:

Field labels (First Name, Last Name, Email, Subject, Message)
Placeholder text
Subject dropdown options (add/remove/edit)
Submit button text
Success and error messages

Step-by-step:

Open Contact Page singleton
Scroll to formFields section
Edit field labels or placeholders as needed
To add/remove subject options, edit the subjectOptions array
Click Save
Preview the contact page (/contact.html)
Test the form: try leaving fields empty to see validation messages
Optionally submit a test to verify success message
Merge to publish

Testing the form: After publishing, send yourself a test message to make sure everything works end-to-end.

5Update Track Information

Why you'll do this: Track stats change, new hotels open nearby, or you want to add/update track features.

Where to go: CMS → Tracks collection → Select track

What you control:

Track name and location
Description and overview
Track stats (length, number of turns)
Features list
Nearby accommodations (hotels with rates and distance)
Track image (also used for track guide hero backgrounds)

Step-by-step:

Open Tracks collection
Select the track you want to edit
Update name, location, description, stats as needed
To edit accommodations, click into the accommodations array
Add/edit/remove hotels (name, rate, distance from track, notes)
Upload a new track image if needed
Click Save
Preview BOTH pages: /tracks.html AND /tracks/[trackId]/guide.html
Also check any events that reference this track
Merge to publish

Track image tip: The track image you upload is used in two places—the tracks overview page AND as the background for the track guide hero section. Choose a high-quality, scenic image.

Before You Click Save

Every time you're about to save a change, run through this quick checklist:

✓ All required fields are filled in
✓ Dates are in the correct format (YYYY-MM-DD, use the date picker)
✓ URLs start with https://
✓ No typos or placeholder text left in
✓ Content is clear, concise, and matches your brand voice

After You Save

Create a Pull Request (PR)
Preview your changes on the test site
Check the changed page(s) carefully—look on desktop AND mobile
Take a screenshot for the PR (especially for visual changes)
If everything looks good, merge to publish live

You're ready to go! Start with Task #1 (Create/Edit an Event) to get comfortable with the workflow. Remember: you can't break anything—every change is previewed before it goes live.

Need more details?

View Full Owner's Manual