Open rjcorwin opened 4 years ago
In the Tangerine client app, we would need to support detection of not having an assets folder (a check for ./assets/app-config.json would do), if it doesn't exit then forward the user to a route showing a "content import" screen. The content import page would utilize the Native Filesystem API to select and gain read access to the local content folder. Then the trick would be using a Service Worker to proxy HTTP requests to ./assets/*
over to the contents of the local content folder.
Three parts...
./assets/
.
With the Native Filesystem API releasing from behind a flag in the next Chrome version, we could alleviate the need to use the command line to start tangerine-preview by offering it as a PWA.
We could publish the Tangerine Preview PWA to something like https://app.tangerinecentral.org, https://tangerine-preview.tangerinecentral.org... or the https://tangy.app URL I scooped up when the .app TLDN launched.