V7 keeps every V6 decision and swaps the stand-in data for the real 2027 inventory, joined to the live web catalog. Orange pins on the page link to the note that explains them. Header, footer and help card are mocked from the live site and don't navigate.
New in V8: featured courses
L Recommendation: an inline "Featured" band after the first 3 results
The band reuses the live featured-courses block from Courses for Youth: blue background, peach Honey heading, ink cards with rounded photos and the highlighter tag. Visitors already know it, and it reads clearly as "promoted" without looking like an ad. Three catalog-specific changes:
- Landscape 16:10 photos instead of squares, so the band is about 590px tall (two slim tiles) rather than the live 1,100px+ and doesn't stall scrolling.
- Each card is personalised to the search. It shows the next date that fits the filters, with dates, length, ages, price and status, plus how many more dates fit. The live cards only say "Sessions for ages 14–16 and 16–18".
- "See dates" jumps to that course's tile further down and highlights it, so the band leads into the list instead of competing with it.
Why after 3 rather than at the top: the first results should answer the search. Putting promotion first delays that and costs trust. Three slim tiles fill about one screen at 1440px, so the band appears on the first scroll, the highest-attention spot that isn't above the answer. The ribbon toggle (and ?featured=top|after3|off in both builds) lets you A/B test top vs after-3 vs off in user testing and in production.
M How the 3 are chosen: rules, not hand-curation
Picking 3 courses for every filter combination isn't manageable: 7 ages × 5 lengths × 12 regions × 6 landscapes × 9 types × 18 activities is millions of combinations, before dates. The filters can do the scoping instead. Editors keep one small pool of featured courses, and the page picks from it on every search:
- It must fit the search. Only courses with at least one date in the current results qualify. A featured course that doesn't match never appears.
- It must be bookable. At least one matching date is Open or Almost Full. Wait List dates only count if the course is flagged Feature for wait list (interest capture). Then the card's button becomes Notify me, the card ranks one step below its priority, and the band holds at most one such card, so bookable courses always lead. Full and Closed dates never qualify.
- No repeats. Courses already among the 3 tiles above the band are skipped, and only one course per place is shown (for example, not two High Sierra pages).
- Rank: editorial priority (1–3), then courses with savings or few spots left, then soonest matching date.
- Backfill from real signals. If editorial picks run short, courses with a reduced price ("Save $350") or Almost Full dates ("Few spots left") can fill the gap. These come straight from the inventory, with no editing needed.
- Show only with 3 qualifiers and 6+ results. With fewer than 3 qualifiers the band is hidden rather than showing 1–2 cards. With fewer than 6 matching courses it's hidden too, because the visitor can already see everything and featuring would just repeat it.
In this notes build, a dashed orange line appears wherever the band was hidden, with the reason. The testing build shows nothing.
N What it takes to build and run
CMS fields on the course record (5): featured (yes/no), featured_priority (1–3), featured_label (optional, e.g. "Staff pick"), featured_from / featured_until, feature_for_waitlist (yes/no). Everything else (dates, status, price, savings, ages) comes from the session index the filters already use.
Build: one server-side function on the same filtered query: filter → eligibility → rank → skip duplicates → top 3 → hide if fewer than 3. No new data source and no per-page setup. Track featured_impression and featured_click with slot, course, reason, placement and the filter state.
What the real inventory says: the biggest limit on the band is inventory, not the editors. About half of single-filter summer searches return fewer than 6 courses, so the band correctly stays hidden. Where it could show, the 19-course sample pool fills it about half the time, and making every course eligible would fill nearly all. Recommendation: a pool of 30–40 courses (roughly a third of the catalog) spread across ages and regions, reviewed monthly. As courses sell out, the band thins and disappears on its own instead of promoting full courses. Use the coverage table below as the health check.
Sample pool in this prototype: 19 courses marked "Staff pick" (priority 1–3) across middle school, high school, young adults, adults, families and Veterans. Joshua Tree – Veterans is flagged for wait-list capture. The picks are placeholders. Replace them with the team's real choices.
How often it appears (every single-filter search, after-3 placement):
Filter mechanics
1 Age bands match real age ranges
The inventory uses 14 different age strings (12–14, 13–14, 14–17, 17–21, 18–24, 18+, 21+, 30+…). V7 keeps V6's seven bands and parses each session's range into numbers. A session shows under a band when it serves most of that band, or when it sits entirely inside it.
- 25+ includes
18+, 21+ and 30+ courses. - 17–25 includes
18–24 and 18+, but not high-school 16–18 trips. - Families only matches parent-and-child courses, and they don't leak into the other bands.
Decided Age bands mean "old enough to go". So 25+ and 45+ both return every adult course, 46 dates today: each one has an open-ended minimum age (18+, 21+, 25+, 30+, 45+), so a 45-year-old is eligible for all of them. Every session row still shows its exact age range, so courses designed for older crews (30+, 45+) are easy to spot.
Resolves V6 §14.3 With this rule, nobody has to migrate data per course to support the 18+ → 25+ remap. The source records stay as they are.
2 Availability = containment, defaulting to summer 2027
Unchanged from V6: a session must start on or after the first date and end by the second date, and each bound works on its own. The default is Jun 1 – Aug 31, 2027, which holds most of the real summer inventory. Sessions that started before Nov 17, 2026 are dropped.
3 Live counts, no dead ends
Every option shows how many dates you'd get if you picked it, counted against all your other filters but not its own. Options that would return zero are greyed out and can't be clicked. Within a facet, choices combine with OR. Across facets, they combine with AND.
4 Facets now run on the web taxonomy
- Where is one two-column popover. The left column lists the 12 real L2 regions, grouped under L1 headings (West, Great Lakes, Southeast, Northeast & Mid-Atlantic, International). The right column is Landscape, built from L2 Setting: Mountains, Forest, Coastal, River, Lake, Desert. It's new, and it's the strongest "what kind of trip" signal the inventory carries.
- Activity lists all 18 real L2 activities in four plain-language groups: Hike & climb, On the water, On snow, Culture & service. Today it's a flat 19-item list hidden under More Filters.
- Program type adds Veterans (web-only courses) and Women's & girls' crews, a tag pulled from course names.
- How long buckets now start at 4 days, so the real 4–6-day courses aren't orphaned.
Search also covers meeting points, school names, the course summary and activity synonyms ("dogsled", "scuba", "spanish").
5 Sticky results bar using the live tape chips
The count, applied filters, Status, Savings and Sort stay pinned while you scroll, so you never lose track of what's narrowing the list. Applied filters use the live site's own highlighter-tape asset.
- Status uses the live labels and icons: Open, Almost Full, Wait List, Course is Full, Closed. The live data has both "Course is Full" and "Closed", so V7 shows both. V6 had merged them.
- Savings is real now. It flags sessions where the web price is below the inventory's Total Tuition. Six sessions qualify today, the same ones the live site shows with a strike-through.
6 Shareable, ad-safe URLs
Filter state is written to the URL with one key per facet (age, from, to, length, region, setting, type, activity, status, offer, q, sort) and read back on load. Old ad parameters like age-groupfilter=High+School are converted to the new bands, so paid traffic keeps landing on filtered results.
Course tile updates
A Real photos, live frame
The tile keeps the live blue-framed square and population tape (High School, Adults, Veterans…). It shows the real web photo set (2–5 per course). Hovering cycles through the photos, and clicking opens a lightbox at full resolution. The frame is 140px, smaller than the live 200px, so the photo never makes a tile taller than its title, summary, tags and three date rows. The tape matters more now: several course names are used by more than one page, for example two "High Sierra – Alpine Backpack & Rock Climb" pages (High School and Young Adults).
B A summary written for this course
New Each tile gets a two-line excerpt from the course description. The first paragraph is usually shared boilerplate ("On Outward Bound courses for high schoolers…"), so the build picks the first paragraph that appears on only this course. That gives each tile something to set it apart before anyone clicks through.
C Taxonomy you can see
Highlighter tags show program type (blue), activities (amber) and landscape (terracotta), the same values the filters use. A visitor can learn the filter vocabulary just by scanning the results.
D Slim tiles: one copy of each fact
Updated A tile now holds only what helps you choose between courses: photo, region, name, a two-line summary, taxonomy tags, and the dates table. The "X dates match · from $X" line is gone because the table already shows every date and price. Meets at, crew size and school are gone too. They now live in the compare view, where they help most.
Tiles average about 300px tall at 1440px wide, down from 407px (26% less scrolling for the same results).
E Ages per session, not per course
One course page can run several age bands. Boundary Waters Dog Sled has 18+ and 30+ crews on the same dates, and Joshua Tree has 14–16 and 16–18. V6 showed ages once per course. V7 restores the live site's Ages column so each row is exact.
F Bookable dates first; full courses sink
The collapsed tile shows up to three bookable dates (Open, Almost Full or Wait List) in date order. The expander says how many more there are and how many can still be booked. A course with nothing bookable drops below every course that has something, whatever the sort.
G Real savings, quietly
Struck-through Total Tuition, the web price, and a green "Save $X" tag. The amounts are real: $350, $1,020 and $2,000. The source data doesn't record an offer deadline, so V7 doesn't show one. Adding a deadline field would bring back V6's "by Mar 1" line.
K Star dates to compare (up to 4)
New Every date row starts with a star. Tap it and that date joins a tray along the bottom of the screen, which shows four slots so the limit is clear before you hit it. With two or more starred, Compare opens a side-by-side view.
- Each column shows dates, duration, ages, cost (with savings), status, meeting point, crew, activities, landscape, program, school and the summary. The lowest price and soonest start are marked.
- From the compare view you can open the course page, Apply or Notify me for those exact dates, or remove a column.
- Stars are by date, not course, so you can compare two dates of the same course (different ages or prices) as easily as two different courses.
- Starred dates stay starred while you change filters. Once four are starred, the other stars grey out with a tooltip saying why.
Worth tracking: compare_added, compare_opened, and which column people leave from. That shows which facts actually decide a booking.
H One clear action per row
Open and Almost Full rows get Apply, with V6's warning that it skips the course page. Wait List and Course is Full rows get Notify me, an alert with no fee. The course-level button keeps the live style and V5's "Explore this course" copy, and it links to the real course page.
Data & schema
S How the data was joined
The join key is course-page slug + start date, plus age range where one page has several bands on the same date. data/build_v7_data.py rebuilds catalog-v7-data.js from new exports.
Data issues worth fixing at source:
- L1 Region, L1 Setting and L1 Activities are blank on 201 of 237 inventory rows. V7 derives L1 Region from L2.
- En dashes in course names come through as "?" in the CSV export (for example "Ten Thousand Islands ? Sea Kayak"). The export needs to be UTF-8.
- Veterans courses and Dec 2027 winter dates are on the web but not in this inventory export (28 sessions).
- "Potomac River – Canoe & Environmental Service" is in the inventory but has no web page yet. It borrows photos from Potomac River – Canoe.
- 239 of 258 sessions are Open. The status mix will look very different in-season, so the status UI should be tested with spring data.
- The scraped web data says "Mountain" where the inventory says "Mountains". V7 normalises it.
J Course schema (filter model + JSON-LD)
The filters read one denormalised model: Course (id, name, url, school, regions[], type, population, activities[], settings[], meetingPoint, crewSize, instructors, summary, images[]) with Session children (code, start, end, days, ages → ageMin/ageMax, price, was, status). That's the session index from V6 §4.1, filled with real fields.
The page also outputs schema.org ItemList → Course → CourseInstance JSON-LD for the visible results, with dates, location, price and availability, so search engines can read the same structure. In production, render it on the server for indexable URLs only.
Show JSON-LD for the first result
Open questions
- Does the "serves most of the band" age rule match how Admissions would advise a family? The edge cases are a 14-year-old looking at 14–16 courses and an 18-year-old looking at 18+ courses.
- Is "Landscape" the right word, or should it be "Setting" as in Salesforce?
- Should Women's & girls' crews be a real taxonomy field instead of something inferred from the course name?
- Where does the savings deadline live in Salesforce, so the tile can say when an offer ends?
- Featured: should "Few spots left" backfill be allowed, or is it too much of a scarcity push for this audience?
- Featured: who owns the pool, and is a monthly review realistic during peak enrollment?