Community Playlist
Portland events, venues, artists, boards. The main site.
Updates
player: keep the hood/venue/artist scope as the channel when tracks change
a9346ed0
player: 'Play this neighborhood' plays the hood (deep link beats resume), hood name in the channel bar, round play button
17c3628b
fix: 500s from root-owned file-cache entries after deploy; chown .cache in deploy.yml, regions cache reads fail soft
b540fc91
dev: mount nights/ in docker-compose; NEXT.md note on new-app mounts
0b34ee7c
nights: new module, 'Getting there' on event pages (bike, bike share, walk, transit, drive, Amtrak Cascades); NEXT.md tagged loyd/claude
d7dea577
docs: AGENTS.md + docs/NEXT.md handoff queue for Loyd/opencode or the next Claude round
b1fdba9e
regions: switching city from an event page lands on the city front page
03d300e3
regions: let nginx cache the cookie-less legacy 301 so it replaces stale pre-launch pages
3633e24a
regions: unlaunched city paths go to the hub (coming soon) instead of 404
331c1e7d
regions: peer city paths (/portland/, /seattle/), PNW hub at root, canonical item redirects, always-on switcher
c74e7d74
regions: path-based scopes (/seattle/, /pnw/), link/redirect prefixing, API scope via referer, switcher, Seattle seeded inactive
3c8e1799
docs: deploy is GitHub Actions (not Plesk) + manual fallback; mark region sweep step 3 done
f64b750e
regions step 3 migrations: content region fields + backfill; pin seed migration dep (no cycle)
e7e10b10
regions tests: allow the seattle test host
ea7f0d6f
regions sweep step 3: region FK on Event/Venue/Topic/Offering/BikeReport, auto-assign, scoped lists
3d37b9b7
regions: mark sweep step 2 done; list deliberate deferrals
ad7c0785
region tag: fall back to default text on any lookup error (never break a page)
5c556b12
regions sweep step 2: template copy uses {% region %} (renders 'Portland' today)
a52c7612
regions: mark sweep step 1 done in MIGRATION_PLAN
51165e71
regions sweep step 1: geo gates are region-aware (Portland behavior unchanged)
4e46c9e1
regions: initial migration
451917f4
regions module (Portland-only groundwork) + MODULES.md index
48e13659
crews module: neighborhood crews (join -> lead invite -> set-password), 4 seeded crews
94909da2
crews: initial migration
c35767e2
bikes: venue bike parking + nearby-theft card, shop mode, printable QR posters, module README
0e67bd16
bikes: venue parking migration
3e14bb8f
email_digest: send in paced batches (20 per 30s) to stay under Gmail's burst throttle
d0d3dd9c
sharekit module + Timberwolves social posts
baea66f2
bikes: social fields migration
4a44292c
onboarding module: 3-step hood/interests/channels wizard + changelog-driven What's new
ed52e1b4
Feedback & ideas
Nothing sent yet.
+ Send Community Playlist feedback →
Support room
Research pass on CP (2026-09-06): 7423 approved events (2596 upcoming, 4827 past), 2563 artists, 186 genres, 133 users.
The headline gap: 34 Venue rows against 1134 distinct location strings. Thousands of real Portland places exist only as text on an event - so there is no page for a search engine or a person to find. Living Haus (756 events), Starday Tavern (294), Portland Art Museum (134) have no venue page at all.
SEO: robots.txt and sitemap.xml are fine, but no JSON-LD and no canonical anywhere - 7423 events that do not say what they are. The wiki also lives on a different domain (ichunez.com/wiki), splitting authority.
The asset worth building on is the archive: 4827 past events is a Portland music history nobody else has. Plan is venues first - derive entities from locations, then venue pages with past + future events and structured data.
Venue layer built: 34 -> 287 venues. The pages already existed (upcoming + past events, follow, calendar feeds, MusicVenue structured data) - there were just only 34 venues against 1134 distinct location strings, so almost nothing had a page. Derived them from the location strings already on events; no event data changed. Living Haus 762 events, Starday Tavern 392, Holocene 55.
Caught two of my own mistakes: a venue named "Portland" matched 4780 events because nearly every location contains the city, and duplicate rows came from different address strings for the same place. Both now blocked; 83 bad rows removed.