Your bug, and it was worse than reported. Signed in, the only way back to the site was buried in the profile menu — an avatar tap, behind a lazy-loaded chunk, fourth item down. Signed out, there was no way back at all: no nav, no logo link, nothing but sign-in or the browser back button. And in the other direction the site menu never mentioned the Yard, so the two halves were invisible to each other.


Signed in, there is now a permanent Website item in the member nav — in the mobile dock and the desktop rail, set apart by a divider because it leaves the app rather than moving inside it. The dock goes from four items to five: 334px wide, clears a 360px phone.
Found while auditing the split, not reported: the member app showed “Sat 13 Dec” while the website showed “Sun 13 Dec” — same event, different day. 13 Dec 2026 is a Sunday; the site computes it from the admin, the app was reading a stale committed file. The app’s own comment claimed this was impossible. It was true when written and false by the end of the same day. Both now read one feed.
Tiga: “the top one for all of the pages, it’s kind of a bit bland.” These were generated on 12 Sep and regraded into the brand palette. Four were wired up; Events was generated and then never referenced — the file sat unused while that page rendered a bare gradient. Fixed and deployed just now. All five below are the live pages.





Tiga: “when you click on that particular link, it just gives you only the ticket for that particular event” / “when you click on the beach party, you see probably one ticket.”
The page was reading only the first upcoming event — every event the client created after that was silently dropped, so this could never work. Now every event reaches the page and the ticket grid follows whichever one you click. Invisible today because there is one live event, which is why it was worth fixing before the client adds a second. Shown against a two-event feed.


The count is real — distinct viewers in the last 30 minutes, stored in Postgres. Your rule applied literally: below 10 it says nothing at all. That is why you won’t see it on the live site right now — there is genuinely one person on that page. Shown here forced to 42.


Renders only when a real playlist URL exists, so nothing ships as a placeholder. Once Tiga sends one, the weekly update happens in Spotify — the embed always shows the playlist’s current contents, so nobody touches the site each week. Shown with a stand-in public playlist.

This was live to every visitor. The 13 Sep fix covered the home-page marquee; this row was missed — it rendered a hardcoded placeholder per entry regardless of what the content said.


The awards page: awards you’ve won, or an awards night you’d run?
The whole basis is one clause at 43:14 — “We’ll probably want an awards page inside the app” — said mid-sentence while moving on to press, never picked up again. One occurrence of “award” across both transcripts.
Those are completely different pages, and the credibility version overlaps the Partnerships page you already have (it holds Mix Mag and Resident Advisor). Inventing awards to fill a page would put fake credentials on a client’s live site, so I stopped. One sentence unblocks it.