Static vs on-the-fly pages

[colmjude]

All the pages on digital land are static pages, generated and the hosted on github.

We want to generate list pages for data collected for any schema. Those pages might look a little like this

Ideally the user would have the ability to do some searching/filtering of the list. We could do this as a progressive enhancement but it is a key feature of the page so maybe we should ensure it is available all the time.

Likewise, a page listing a few hundred records (for example, local plans) can work as a static page. But what about when we are many more records (brownfield-land with 27k or UPRN which would have millions)?

How should we approach moving some or all of the site on to a server?

[colmjude]

We discussed building Single Page Applications (SPAs) for these pages but they would still have the same progressive enhancement problem.

Sometimes that is acceptable as long as the user still has a way to perform the action they need to perform but in this case, without JS, there would be no way for them to filter or search across 1000s-millions of rows.