You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 27, 2018. It is now read-only.
This is mostly alright, except that static resource is unnecessary (they're all static resources on GitHub Pages), and the timestamps aren't useful either. I might consider adding checkmarks, as we've done for sequences in #148, #160, and #161.
I might also consider adding some header and footer text, although offline is different from configure, bootstrap, and integrate in that it gets run frequently and automatically (as part of a build sequence), whereas those other commands get run infrequently and always manually. So I'm not sure it makes sense to include a header/footer. At most, I would add a one-line header like:
Offlining [TARGET DIRECTORY] to [path/to/offline-worker.js]…
The text was updated successfully, but these errors were encountered:
The offline command's output could be clearer. Here's the current output:
This is mostly alright, except that static resource is unnecessary (they're all static resources on GitHub Pages), and the timestamps aren't useful either. I might consider adding checkmarks, as we've done for sequences in #148, #160, and #161.
I might also consider adding some header and footer text, although offline is different from configure, bootstrap, and integrate in that it gets run frequently and automatically (as part of a build sequence), whereas those other commands get run infrequently and always manually. So I'm not sure it makes sense to include a header/footer. At most, I would add a one-line header like:
The text was updated successfully, but these errors were encountered: