Add venues list and song list for each artist

[switz]

So below "Recent Tapes" there would be a row for "Venues". There may be a way to solve this by adding a sixth column, going artists -> yearslist -> venueslist -> shows_at_venue_list -> songlist -> tapeslist - but what might be a better solution is taking you from venues to a new page that has a table of shows at a venue. To be clear, I think the former is better ux, but may be too complicated to implement.

The advantage of the external page is we can re-use the same table page for songs. Again, perhaps the six column strategy could be enough here, but also it might be too complicated or overly dense.

I'm a big fan of the phish.in song pages, so it may be worth taking some inspiration: https://phish.in/songs/piper

But also there's a few things I would change, which is that I'd make it more table-friendly, sorting the columns in the header, perhaps adding complex filtering.

A friend just asked me "is that the first 20 minute piper since 2.0" (from the show tonight) and I paginated through a number of pages manually checking the duration until I got to Spac 04 and saw that it was. So maybe we can solve for that use case in some easier manner.

Anyway feel free to ask questions or play with it. I'll be available on the discord to assist with both technical and UX questions if this intrigues you.

[switz]

From a technical standpoint, we should continue to use server components where appropriate and client components where appropriate - the api doesn't offer any pagination at the moment, which is a touch bulky, but also not the end of the world. If we're doing complex sorting/filtering in a table (perhaps using tanstack table), then let's use client components w/ nuqs for the search params. If we're not, then we can stick with server components to lighten the load. Data fetching can happen in server components regardless.

[switz]

A friend just asked me "is that the first 20 minute piper since 2.0" (from the show tonight) and I paginated through a number of pages manually checking the duration until I got to Spac 04 and saw that it was. So maybe we can solve for that use case in some easier manner.

For phish we should have "era" support so it could be cool to add complex filtering for things like "eras" or "years", then sort by duration. Would make answering that question (and others like it) lickety split fast.

[switz]

alecgorge — 11:45 PM
my vote would be not to have a sixth column
it is already pretty tight on my 13" macbook in arc with the vertical tabs
switz — 11:46 PM
I tend to agree – in theory we could do what I currently do on recent tapes/tih which is just redirect you back to the main layout once you finally click on a show
e.g. https://relisten.net/grateful-dead/today-in-history
alecgorge — 11:47 PM
each artist could be its own page and then you could have 5 columns
switz — 11:47 PM
hmm like collapsing the main artist list if you get into songs/venues
that's interesting
alecgorge — 11:48 PM
artists could be a column but then disappear up into a popover or something
idk
switz — 11:48 PM
so the main reason why tih/recent works like it does is because going nesting further columns involves an insane route structure
alecgorge — 11:48 PM
i've also been thinking about an ipad/macos layout
switz — 11:48 PM
you'd need: /phish/venues/madison-square-garden/2012-12-28/tweezer on top of all the other existing routes
its easier to just add one for venues and venues/:id and then navigate back to the main layout. you lose context but its simpler from a route design/code structure