Brand Guidelines · v1

Story Trail

"Every place remembers."

Brand statement

Story Trail turns a walk into an encounter with the people who were there before you. Not a plaque, not a caption — a voice. A street corner becomes someone's first kiss. A tenement becomes three generations under one roof. A tavern becomes the night before everything changed. Every trail is a way of belonging somewhere, even for an afternoon. The land remembers; Story Trail helps you listen.

Why this, not a travel-guide voice: the product already does the hard part — GPS waypoints, AR/VR walking mode, real historical research via Suburb Historian. The brand's job is to make sure none of that reads like a museum placard. The emotional arc is wonder → belonging: the delight of learning something you didn't know, then the quieter feeling of now being someone who knows it.

Origin

A holiday house in St Leonards

It started with kids on devices at a holiday house on Victoria's Bellarine Peninsula, staring at screens instead of the coastline outside. The fix wasn't taking the tech away — it was pointing it at something real: augmented reality that made the ordinary beach worth looking up for. Then came a book on Fort Queenscliff's WWII history, alleging a string of wartime murders nearby may have involved a Japanese commando or spy — with a list of the actual places it happened. Walking those places made the idea obvious: this should be an app.

That same stretch of coast also passes Indented Head, where a 1931 monument commemorates John Batman's 1835 landing alongside Matthew Flinders' — filed under "exploration," with no mention of what it began for the Wadawurrung people whose Country it already was. Story Trail exists to tell both kinds of story: the one that makes a kid look up in delight, and the one a hundred-year-old plaque left out. See Difficult history, told honestly, below.

Who it's for

Family-first

Primary audience: parents and kids, out and about together — not a solo traveller with headphones in. That's a real decision, not just a nice-to-have secondary use case, and it follows straight from the origin story: this began as a way to get kids looking up from a screen, not a travel-history app that happens to be kid-tolerant.

The product decision that follows: discovery starts in the real world, not in the app. A parent and kid spot a marker on a fence post or trailhead sign before either of them has opened Story Trail at all — the QR code is the invitation. Every default (voice, chapter length, pacing, the "unlock the next chapter" mechanic) should be built for the kid holding the phone, not the adult reading over their shoulder. A solo traveller or history enthusiast should still get plenty out of it — but they're the secondary case now, not the design target.

Tone reference

Warm, not clinical

Most trail and travel apps are optimised for efficient utility — the right instinct for the map, the wrong one for the stories. The tone target is closer to Stories of Home: first-person, human-voiced, portrait-led — a project about people's stories, not a wayfinding tool that happens to contain history.

KEEP

Map-first utility for wayfinding

GPS, distance, proximity, "start walking" — this layer should stay efficient and clear. Nobody wants friction between them and the trailhead.

CHANGE

Everything once a story opens

The moment a waypoint story appears, the voice should shift — warmer type, first-person framing, human photography. That's the brand's actual home.

Brand pillars

What Story Trail always is

01

Wonder at street level

History isn't behind glass — it's under your feet. The surprise that the ordinary corner you're standing on has a story is the whole hook.

02

Told, not captioned

Every waypoint reads like someone telling you about a place they love, not a plaque describing a "historic structure."

03

Belonging through knowing

Understanding who was here makes you, briefly, part of the place too — this is true for a weekend visitor and a lifelong local alike.

04

Placeless craft, local heart

The same warmth and design quality everywhere Story Trail launches, but every trail is unmistakably of its own place — never generic.

05

Whose story, and whose isn't

Some of the fullest history here predates any plaque — and some plaques only tell the coloniser's half. Where a trail touches First Nations history, Story Trail names whose Country it is, and doesn't repeat a monument's silence as if it were the whole story.

Difficult history, told honestly

Case study: Indented Head

On 29 May 1835, John Batman anchored off Indented Head and negotiated a "treaty" with Wadawurrung people for the land that became Melbourne; a landing party went ashore on 9 June. The monument on the site, unveiled in 1931, commemorates it as exploration — the same word used for Matthew Flinders' 1802 landing nearby — with no mention that it opened the systematic dispossession of the Wadawurrung from land they had never ceded by their own account. That gap between plaque and truth is precisely the kind of story this app exists to close, and it won't always be a comfortable one.

This isn't a "serious mode" bolted onto an otherwise light brand — it's the same told, not captioned standard from the voice pillars, applied honestly even when the story is uncomfortable for the teller. A few standing rules:

Naming & tagline

"Story Trail" — locked

Primary tagline: Every place remembers. Short, works on a splash screen, translates across cities, ties directly to the emotional core (memory → belonging).

Working alternates (for varied contexts — app store copy, ads, signage):

Voice & tone

Write like you're telling a friend, not captioning a landmark

Specific, human detail beats grand historical sweep. Present-tense immediacy for scene-setting. Warm confidence — never a tourist-brochure exclamation point.

DoDon't
"This tenement held three generations under one roof — and a wedding in the stairwell in 1947." "This historic tenement building, constructed in the early 20th century, is a significant local landmark!"
"Ask anyone who grew up on this block about the bakery. They all mention the smell first." "Local bakery, established 1962, was popular with residents."
"Stand here a second. In 1919 this was the loudest corner in the city." "Welcome to Waypoint 3! Did you know this used to be a busy intersection?"
"Was he really a spy, or just a fisherman with terrible timing? Nobody's ever been completely sure." "This site is linked to alleged WWII espionage activities in the local area."
"Two blocks. Four stories. About twenty minutes." "Embark on an unforgettable journey through time on this must-see trail."
"This beach had a name and a people long before a ship anchored off it in 1835 — the Wadawurrung, who never signed away this land in any way they recognised." "In 1835, European settlers began exploring the fertile lands of the Bellarine Peninsula."

Colour system

Retiring the shipped green

The live app currently uses a saturated forest green (#16A34A) as its only brand colour — functional, but it reads "hiking app," not "human stories." The new primary, Trail Clay, is an earthy terracotta: warm, found in brick and rooftops in cities worldwide (so it stays placeless across launches), and it doesn't compete with the muted, diverse hues trails themselves already use on the map.

Trail Clay
#C2552A · HSL 17 65% 46%
Primary — buttons, links, focus ring, nav
Ink
#2A2420 · HSL 24 14% 14%
Body text / foreground
Parchment
#FAF4E9 · HSL 39 63% 95%
Background — warm, not stark white
Discovery Gold
#C99A2E · HSL 42 63% 48%
Accent — new-story badges, highlights
Parchment Dim
#F1E9DC
Cards / secondary surfaces
Trail Red
#C33A2A
Destructive / error only

Trail-line palette (functional, kept diverse)

Individual trail routes on the map need to stay visually distinct from each other and from brand chrome — that's a data-viz job, not a brand-colour job. Replacing the shipped bright chart set with a muted "old cartography" palette keeps that function while fitting the warmer world:

Clay · default
Moss #5B7548
Dusty Teal #3E7C8A
Plum #7A4B6E
Ochre #C99A2E

Typography

Keep the pairing already loaded — just actually use it

Good news: Merriweather and Inter are already loaded in client/index.html and wired up as --font-serif/--font-sans in the Tailwind config. Merriweather just isn't applied anywhere yet. That's a lucky accident — a warm editorial serif for story content, paired with a clean sans for map/UI chrome, is exactly the split this brand needs. No new fonts to license or load — just apply font-serif to story titles and body text.

Every place remembers.

Merriweather 900 · Display

Chapter 2: The Watcher on the Beach

Merriweather 700 · Story title

Somebody was signalling ships from this exact stretch of coast in 1942. The navy was sure of it. A Japanese commando, they said — though nobody's ever been completely sure.

Merriweather 400 · Story body

Start walking

Inter 600 · UI label

0.6 mi · 5 waypoints · Easy

Inter 400 · Meta / captions

-38.2667, 144.6667

JetBrains Mono · Coordinates, IDs

Iconography & photography

Away from generic map pins and stock tourism photography

The current mark is a Lucide MapPin icon in a green circle — placeholder-grade, not custom. Photography direction should follow the Stories-of-Home instinct: real people, hands, doorways, everyday texture, natural light. Avoid: glossy drone shots, generic "landmark against blue sky" tourism stock, sharp GPS-pin iconography for anything story-related (fine for pure wayfinding UI, wrong for story moments).

USE

Portraits, hands, doorways

Documentary-style, natural light, imperfect — signals "someone lived here," not "postcard."

AVOID

Drone shots, glossy skylines

Reads as travel-brochure spectacle — the opposite of the intimate, human register the voice aims for.

App icon concept

Path + story, in one mark

A dotted trail (three fading waypoint dots) leads into a single pin shape — which is drawn to double as a speech-bubble tail, so the mark reads as both "location" and "a story is here" without needing text. Legible from a 16px favicon up to a 1024px App Store icon.

Standalone icon.svg included alongside this document — export to PNG/ICO/appiconset when ready.

Physical touchpoint: QR waypoints

The first brand impression happens outdoors, not on a screen

Now that discovery starts with a marker on a post, plaque, or sign before anyone opens the app, that physical object is arguably the single most important piece of brand real estate Story Trail has — a kid needs to recognise it as "a Story Trail thing" from a distance, before they can even read it.

Chapter 2 of 5 · The Queenscliff Watch

Scan to unlock Chapter 2

Illustrative only — not a scannable code.

Product family

Story Trail + Suburb Historian

Same DNA, different job — and a genuinely different person on the other end. Suburb Historian's users are local history experts: solo enthusiasts, people inside local history associations (still enthusiasts, just alongside like-minded people), and — the stretch goal, not yet the reality — museum or government heritage staff. They're passionate and usually sitting on more research than they know what to do with, but they're often "wonk-ish": deep on facts, dates, and sources, not necessarily practised at turning that into the voice-led narrative Story Trail publishes. Likely skewing older, and likely needing real hand-holding through the software itself, not just the writing.

Suburb Historian

Internal/authoring. Same Clay/Ink/Parchment palette and type pairing, but calmer, more utilitarian layout — a research tool, not a storefront. This is where trails and waypoints actually get researched and written.

→ exports to

Story Trail

Public-facing. Warm, story-voiced, Clay + Parchment. This is where the brand lives loudest — org logos authored in Suburb Historian surface here on trail cards.

The brand's job here is coaching, not gatekeeping. Someone who's spent thirty years researching their town's history should never feel judged by the software. Suburb Historian's voice should be patient, plain-language, and specific about why a step matters — never clever, never jargon-heavy — and generous with encouragement at every review checkpoint (the product already has three: research review, draft review, photo review). Each of those should read as a collaborator checking in, not a gate to pass.

Suburb Historian voice — coach, not critic

DoDon't
"Great start — you've got the facts. Want help shaping this into a story someone would want to read aloud?" "Content quality insufficient. Please revise narrative structure."
"No rush — everything's saved. Come back whenever you're ready." "Session will time out in 5 minutes."
"You know this place better than anyone. We'll help with the telling." "AI-assisted content generation pipeline."

Practically: assume the person at the keyboard may not be highly tech-fluent — plain language throughout, larger touch targets, nothing that requires knowing what "LangGraph" or "HITL" means (those are our backend terms, never the user's problem). If a research pass or photo search comes back thin, say so kindly and suggest a next step — never a bare error state.

In application

A waypoint story card, in the new system

Chapter 2 of 5 · The Queenscliff Watch

The Watcher on the Beach

Somebody was signalling ships from this exact stretch of coast in 1942. A Japanese commando, the navy said — though nobody's ever been completely sure. Look up. You're standing in chapter two.

📍 60m away🕰️ 1942