yes it can you just need a filter/sort/search function added in

This is a non-answer.

you build all the possible variants (or at least the ones you want to have statically build) using the return of generateStaticParams. So you'd end up building pages like domain.com/composers/year/2011 domain.com/composers/year/2012 , domain.com/composers/style/opera . You could also mix those e.g. domain.com/composers/2011/opera. Last example would be a catch all route while the other examples would be just catch one level deep

If you provide your goal url structure it would be easier to give an example

Seemed like a good one to me 🙂 in your specific case then if you didn't get what I mean is to create a catch all dynamic route and add a getStaticParame to generate all the various options you want built. Then done.

If the page is built on the server side during build-time, how can I have a clickable button for a user? What am I missing?

What are you trying to do with the button?

On a client page, I can fetch the data, and apply a filter to it immediatly, and whenever a user filters with some text for example, I can make the list filter immediately.
But with a server component, the data is prerendered, I cant put it through a dynamic filter

Lets say I have a list of 1000 composers.
During build time, a page gets all composers, and places them on one page.

In an ideal world, I have a search input field, where the user starts typing a composer's name, and it shows only the composers with letters that fit.
However, this requires dynamically filtering the composers as the user types.
And I dont see how that can happen with a component rendered during build time, thats where my issue is. I don't know what the correct approach is.

how come you are doing it that way anyway? why not make it dynamic for searching?

Is there any way I can do that while still benefitting from a prerendered page? (that is, fast serving and SEO seeing that I have a page with these composers)

well yeah, ISR really would do this

thats what i do in this situation

unless im missing something

Is that a pages-routes specific approach?

works on Pages or App dir routing

i would look into it and see if that works for you

I was not aware of this approach. Thank you very much. I only looked in app-dir docs previously, didn't know if some of these approaches are interchangeable between routes approaches.

No worries! It's crazy the stuff you can do now. Hope this helped!

also, just a bonus/side tip.. if you create a search api for your site, you can get google to use that for doing SEO/SERP/etc.. its literally the back door into google.. at least i think.

Interesting, is this what you mean? https://developers.google.com/custom-search/v1/overview "Custom JSON Search API"?