Conflict 1
Club shirt price
What did not line up
Jordan Reeves, Founder, wrote that club shirts are $20. The content pack says Club shirt, $25.
What we decided
The Gear page shows Club shirt, $25. The $20 figure is not on the public pages.
Why
Prices in the content pack are fixed. A conflicting email is logged instead of silently changing the price.
Where it shows: Gear page, and this log
Conflict 2
Who the site leads with
What did not line up
Jordan wrote: make it loud, lead with the Tempo group, we want fast people. The brief puts nervous first timers first, and the primary action is Join a Run. Maya Okafor wrote that nobody should think this is only for fast runners. Lena Ruiz asked for a calm, welcoming tone. The brief tone is energetic, welcoming, and a little cheeky.
What we decided
The nervous first timer is the main visitor. Pace groups are shown as Walk, then Social, then Steady, then Tempo. Type is large. Tempo is one group of four, not the headline.
Why
The brief lists goals in priority order. The walk group and the social pace group are also FAQ facts, not only a preference.
Where it shows: Home and Join
Conflict 3
Four pages or five
What did not line up
The brief and Jordan ask for Home, Weekly Runs, Join, Partners, and Gear. Lena Ruiz wrote that four pages is plenty.
What we decided
All five pages are built.
Why
The brief names the pages. Gear is where the shirt and hat prices live. Partners still shows all three package prices on one laptop screen, which is what Lena asked for.
Where it shows: Primary navigation
Conflict 4
White text on Sunrise Yellow
What did not line up
Brand rules say buttons are Sunrise Yellow with white text. Brand rules also require text of at least 4.5 to 1. White on #FFC93C measures 1.54 to 1. Asphalt #1E2A32 on #FFC93C measures 9.54 to 1.
What we decided
The button fill stays Sunrise Yellow. The label is Asphalt. Every button uses one shared component.
Why
Both rules are in the brand section. Contrast is also a scored requirement. The yellow was not replaced.
Where it shows: Shared button, every page
Conflict 5
Where Trail Green text can sit
What did not line up
Trail Green is for links and small accents. On Concrete it measures 4.39 to 1. On Mist, 3.69 to 1. On Asphalt, 2.93 to 1. On white it measures 5.00 to 1.
What we decided
The hex stays #2E7D5B. Green text is used only on white. Navigation labels are Asphalt on white. Footer links are Concrete on Asphalt. Cards use Mist with Asphalt text.
Why
Changing the hex would break a brand color. Moving the text keeps the color and clears 4.5 to 1.
Where it shows: Design system, navigation, footer, cards
Conflict 6
Saturday, October 17 is listed more than once
What did not line up
The weekly Saturday long run is 8:00 AM at Bean Counter Coffee. The same morning also lists Fall Kickoff Long Run and Charity 5K for the Food Bank, both at 8:00 AM at Bean Counter Coffee.
What we decided
The weekly row and both special rows are shown exactly. A note on Weekly runs says the packet lists them together. They were not merged or dropped.
Why
The kickoff may be the weekly long run. The packet does not say that. Guessing would hide a listed event.
Where it shows: Weekly runs
Conflict 7
Saturday, November 8 does not match the other Saturdays
What did not line up
October 17, October 31, and November 14 can be Saturdays in the same year. November 8 is 22 days after October 17, and 22 days after a Saturday is a Sunday. The packet still says Saturday, November 8. The year is not written in the packet. The clash does not depend on picking a year.
What we decided
The schedule prints Saturday, November 8 exactly. The weekday was not corrected on the page.
Why
Dates and weekdays in the packet stay as written when they disagree. The conflict is recorded here.
Where it shows: Weekly runs, and this log
Conflict 8
Sunday starts at the trailhead, and coffee is still the ending
What did not line up
Sunday Recovery Walk or Jog starts at Eastside Trailhead. The other weekly runs start at Bean Counter Coffee. A separate fact says every run ends with coffee at Bean Counter Coffee.
What we decided
Sunday keeps Eastside Trailhead as the start. Copy still says every run ends with coffee at Bean Counter Coffee.
Why
The start and the ending are different facts. Dropping coffee for Sunday would ignore the club-at-a-glance line.
Where it shows: Weekly runs and the coffee section
Conflict 9
A buddy on evening runs is not in the FAQ
What did not line up
The FAQ answer is: Water, shoes you can run in and a light for evening runs. Maya Okafor also asked runners to bring a light and run with a buddy. Chris Tran is Safety Lead. The packet does not quote him.
What we decided
The FAQ is quoted exactly. A separate note names Maya and her buddy request. No quote was written for Chris Tran.
Why
Putting buddy inside the FAQ would change a fixed answer. Hiding Maya's note would drop a safety request.
Where it shows: Join, and the evening note on Weekly runs
Conflict 10
No sign-up form, no shop, and one email
What did not line up
The packet gives partners@beltlinepace.example. It does not give a general contact, a registration link, or a place to buy the shirt or hat.
What we decided
Join tells people to show up at the published start. Gear lists $25 and $18 and says the packet does not say where to buy them. The partner email is used only for partners.
Why
A shop, a second email, or a fake checkout would be a new fact.
Where it shows: Join, Gear, and Partners
Conflict 11
Full name in headings, and sentence case
What did not line up
The brand says to always write BeltLine Pace Run Club in headings, and also to use sentence case headings.
What we decided
The full name is the wordmark and the first line of every page heading. Section headings stay specific, such as This week.
Why
Repeating the full name on every subheading would make the pages harder to scan. The wordmark is never shortened.
Where it shows: Wordmark and page headings
Conflict 12
Client update was not in the packet
What did not line up
The event adds a client update during the build. That note was not in the packet used for this site.
What we decided
No update was invented. A shared banner stays off until clientUpdate.active is set in lib/content.ts. Colors, the button, the navigation, and the facts in this file are the update path.
Why
Inventing an update would fake the response. One shared change is how the real note should land on every page.
Where it shows: lib/content.ts, shared button, design system live edit