Back to Work

Local product case study

Island Happenings

A curated Vancouver Island event guide built for deciding what is worth doing nearby.

The product is intentionally smaller than a full events database: source-linked, practical, and maintained around useful weekly choices.

What it is

Island Happenings is a small local guide for answering what is worth doing nearby this week.

Product stance

The site promises curation and usefulness, not every event on the Island. That keeps the product maintainable and honest.

What I built

A listing and detail system with source links, planning notes, good-for tags, cost, timing, submission paths, and correction language.

Why it matters

Local event tools fail when they feel stale or overstuffed. A smaller guide can be more trustworthy when every listing earns its place.

Listing anatomy

The product proves its taste through what each listing keeps visible.

Source link: the original event page stays close to the listing for final confirmation

Time and place: dates, location detail, and map confidence are separated instead of guessed together

Cost and planning notes: practical context is treated as part of the listing, not decoration

Correction path: the product makes room for human submission and correction instead of pretending every listing is automated

Portfolio proof

Trust and curation choices a reviewer can understand quickly.

Editorial product judgment

The homepage is organized around choosing a plan, not browsing a raw database: timely picks, practical filters, and regional context.

Source-linked trust

Listings keep the original source close so people can confirm times, costs, venue details, and late changes before committing.

Location restraint

Map pins appear only when the source gives a useful location. Fuzzy or region-only events stay in the guide list instead of being guessed onto a map.

Correction path

The product includes submission and correction paths so community input can improve the guide without pretending everything is automated.

Technical notes

  • Next.js and TypeScript app structure for event listing, detail, submit, and map surfaces
  • Event data model shaped around source URL, checked language, planning notes, location confidence, and audience tags
  • Map/list behavior designed around trust boundaries rather than forcing every event into geospatial UI
  • Editorial workflow that can stay small while still producing useful weekly coverage

Boundary

Island Happenings is a curated guide, not an official venue calendar. The source link remains the final place to confirm changes before heading out.