maxlath

* great resource: https://developer.mozilla.org/en-US/Apps/Progressive * articles of interest: * [How you can develop Progressive Web Apps that feel like native mobile apps](https://medium.freecodecamp.org/how-you-can-develop-progressive-web-apps-that-feel-native-5110fbbcbf4b) * [Installable Web Apps: A Practical Introduction To...

current [Lighthouse](https://developers.google.com/web/tools/lighthouse) score: 

resources related to our updated stack * [Webpack: Progressive Web Application](https://webpack.js.org/guides/progressive-web-application/) * [Svelte PWA](https://github.com/tretapey/svelte-pwa)

shipping PWA to app stores: - https://web.dev/pwas-in-app-stores/ - https://www.pwabuilder.com/ - https://github.com/GoogleChromeLabs/bubblewrap

that could be fixed, when rewriting the top bar as a Svelte component, by using the `Dropdown` component, which can check on which side the dropdown content should be positioned

aha, then maybe start by fitting the largest dimension, rather than the shortest as it is the case at the moment, to make this possibility more explicit

We could index editions in Elasticsearch (this was already discussed but I can't recover where), include the publisher prefixed as derived data, and then query it with something like `/api/search?types=editions&claim=wdt:P3025=${isbnPrefix}`...

Note that, even if way less convenient that what you suggest, it's already possible to find those editions by ISBN publisher prefix, using SPARQL: * [Find editions that don't have...

I put the tag "feature request" because we don't have a "feature idea" tag ;) This is not the first time this is suggested, so it's good that we now...

I got it from the `shex` module on npm; using `@shexjs/cli` fixes the problem indeed. It comes with another (minor) issue though: ``` Error: Cannot find module '@shexjs/parser' Require stack:...