About export-frontend. I’ve been wondering for a bit if the explorer shouldn’t be a pre-compiled module you can embed. Or host separately. Only pointing to data.
As currently every “instance” includes a lot of extra stuff too. Like https://sfosc.org/sourcecred/ The into page here, which is largely superseded by to the updated https://sourcecred.io/ homepage. I think most instances will link only to the project list or directly to an explorer instance.
Currently we’re also using server-side rendering to have URLs for these. However I think many more parameters are interesting to create URLs for. Like narrowing down to a timeframe, or linking to the github repositories view. Something like using GET parameters or hash parameters make sense to use instead. What that would also allow is to be completely driven by static files in the data folder. e.g. no need to use webpack to generate folders and minimal HTML files just so you can have your URLs the way you’d like. Which would eliminate the need for end-users to even compile the frontend.