<commit_before><!DOCTYPE html>

<html>
<head>
  <meta http-equiv="Content-Type" content="text/html; charset=utf-8"/>
  <title>Using Service Workers</title>
  <link href="css/main.css" rel="stylesheet" type="text/css">
</head>

<body>
<h1>Using Service Workers</h1>

<p><strong>Adding offline capabilities, background sync and push notifications to your web applications.</strong></p>

<p>
Technology level: <em>experimental</em>
</p>

<p>
For any issues, submit issues against the <a href="https://github.com/flaki/ck-service-workers">ck-service-workers</a> repository.
</p>

<h3>Versioning information</h3>

<p>Current as of July 2015, last significant update was 2015-07-13. <br>
  This content kit tracks the latest version of the <a href="https://github.com/slightlyoff/ServiceWorker/">service worker specification</a>
  and related specs, all code &amp; demos include the required browser version/implementation.</p>

<p>This content kit is published under the Mozilla Public License, version 2.0.</p>

<h2>What should the presenter have?</h2>

<ul>
    <li>What hardware and software will the presenter need?</li>
    <li>For example
      <ul>
        <li>Modern browsers, text editor?</li>
        <li>Python or Node installed?</li>
        <li>Instructions for projecting your device's screen (USB webcam, document camera, etc.)</li>
        <li>Correct USB cable for the device</li>
        <li>Remote debugging enabled for phone demos</li>
      </ul>
    </li>
    <li>What knowledge and background will the presenter most likely need?</li>
</ul>


<h2>What should the audience have?</h2>

<ul>
    <li>What hardware and software will the audience need?</li>
    <li>What knowledge and background is the audience recommended to have? For beginner level kits, please include even basics like understanding how to write a simple web page or understanding how to use an editor.</li>
</ul>


<h2>About "Modular Content Kit"-s</h2>

<p>Not all audiences are created equal - so not all presentations, workshops should be the same as well.</p>

<p>Modular content kits consist of several, smaller chunks of talks, slides, workshop parts.
  When speakers know the audience of there talk beforehand, they could easily mix-and-match the different parts to give the best fitting talk/service to their audience.<br>
  Being able to compose one's presentation from smaller chunks can also prove great when the event schedule &amp; circumstances require fitting the presentation into a tighter time limit.
</p>


<h2>Learning objectives</h2>

<p>After you present or teach this content kit, your audience will know how to:</p>

<ul>
  <li>A short 5 to 15 minute talk or intro composed of the content kit's intro modules is great for:
    <ul>
      <li>Introducing service workers for non-technical audiences, share the vision/possibilities they enable in the future</li>
      <li>Demonstrate basic usage and show possibilities for technical audiences</li>
      <li>Teach service worker basics &amp; intro to usage to audiences familiar with JavaScript-programming</li>
    </ul>
  </li>
  <li>Deep-dive modules could be then used to elaborate on a subject matter like (for audiences familiar with code)
    <ul>
      <li></li>
    </ul>
  </li>
</ul>

<h2>Link to materials</h2>

<p>Resources overview</p>

    <ul>
        <li>Source code: <a href="https://github.com/flaki/ck-service-workers/">GitHub</a></li>
        <li>Live demo: <a href="http://flaki.github.com/ck-service-workers/index.html">Service Worker Content Kit</a></li>
        <li>Issue tracker/feedback: <a href="https://github.com/flaki/ck-service-workers/issues">GitHub Issues</a></li>
        <li>Builds:</li>
    </ul>

<p>Supporting docs/references</p>

    <ul>
        <li>Docs: <a href="https://developer.mozilla.org/en-US/docs/Web/API/Service_Worker_API">MDN</a></li>
        <li>Specification: <a href="#https://slightlyoff.github.io/ServiceWorker/spec/service_worker/index.html">Service Workers</a></li>
        <li>Tutorial: <a href="http://www.html5rocks.com/en/tutorials/service-worker/introduction/">Introduction to Service Worker</a></li>
        <li>Implementation status: <a href="https://jakearchibald.github.io/isserviceworkerready/">isServiceWorkerReady?</a></li>
        <li>Service worker news: <a href="https://twitter.com/service_workers">@service_workers</a></li>
    </ul>


<h2>Presentation setup</h2>

<ul>
  <li>Link to slides</li>
  <li>Links to videos of the presentation materials being used (optional)</li>
</ul>

<p>Include notes here on presenting or using the materials</p>

<h2>Demo setup</h2>

<ul>
  <li>Link to demos</li>
  <li>Demo script:
    <ul>
      <li>A walkthrough of how to run the demo</li>
      <li>Main points to make</li>
    </ul>
  </li>
  <li>Troubleshooting:
    <ul>
      <li>Things that might be broken</li>
      <li>Things that might be broken</li>
    </ul>
  </li>
  <li>Links to videos of the demos being used</li>
  <li>Instructions for how to give the demo offline</li>
</ul>

<h2>Active learning</h2>

<p>If possible, include some kind of active learning mechanism in your content kit slides, to break up the presentation a bit. This may include links to demos that the audience can play with, live coding sections, demos that include participation from the audience, etc.</p>

<h2>Frequently asked questions (FAQs)</h2>

<p>
Refer to the <a href="faq.html">FAQ section</a>.
</p>

<p>
To add your own answers from your previous experiences, create a PR to the
<a href="https://github.com/flaki/ck-service-workers/blob/gh-pages/FAQ.md">FAQ.md</a> file,
or ask your own questions in the <a href="https://github.com/flaki/ck-service-workers">issues section</a>.
</p><commit_msg>Rearrange sections & clarify index copy<commit_after><!DOCTYPE html>

<html>
<head>
  <meta http-equiv="Content-Type" content="text/html; charset=utf-8"/>
  <title>Using Service Workers</title>
  <link href="css/main.css" rel="stylesheet" type="text/css">
</head>

<body>
<h1>Using Service Workers</h1>

<p><strong>Adding offline capabilities, background sync and push notifications to your web applications.</strong></p>

<p>
Technology level: <em>experimental</em>
</p>

<p>
Submit any issues or pull requests against the <a href="https://github.com/flaki/ck-service-workers">ck-service-workers</a> repository.
</p>

<h3>Versioning information</h3>

<p>Current as of July 2015, last significant update was 2015-07-13. <br>
  This content kit tracks the latest version of the <a href="https://github.com/slightlyoff/ServiceWorker/">service worker specification</a>
  and related specs, all code &amp; demos include the required browser version/implementation.</p>

<p>This content kit is published under the Mozilla Public License, version 2.0.</p>


<h2>About this content kit</h2>

<p>Not all audiences are created equal - so not all presentations and workshops should be the same as well.</p>

<p>This content kit aims to be as modular as possible - consisting of several types of teaching resources to help presenters give talks, show slides and/or host workshops. When speakers know their audience beforehand, they could easily mix-and-match the different resources to create the most appropriate presentation for their audience, and also adapt to any time constraints or environmental limitations they might be subject to.</p>


<h2>What should the presenter have?</h2>

<ul>
    <li>What hardware and software will the presenter need?</li>
    <li>For example
      <ul>
        <li>Modern browsers, text editor?</li>
        <li>Python or Node installed?</li>
        <li>Instructions for projecting your device's screen (USB webcam, document camera, etc.)</li>
        <li>Correct USB cable for the device</li>
        <li>Remote debugging enabled for phone demos</li>
      </ul>
    </li>
    <li>What knowledge and background will the presenter most likely need?</li>
</ul>


<h2>What should the audience have?</h2>

<ul>
    <li>What hardware and software will the audience need?</li>
    <li>What knowledge and background is the audience recommended to have? For beginner level kits, please include even basics like understanding how to write a simple web page or understanding how to use an editor.</li>
</ul>

<h2>Learning objectives</h2>

<p>After you present or teach this content kit, your audience will know how to:</p>

<ul>
  <li>A short 5 to 15 minute talk or intro composed of the content kit's intro modules is great for:
    <ul>
      <li>Introducing service workers for non-technical audiences, share the vision/possibilities they enable in the future</li>
      <li>Demonstrate basic usage and show possibilities for technical audiences</li>
      <li>Teach service worker basics &amp; intro to usage to audiences familiar with JavaScript-programming</li>
    </ul>
  </li>
  <li>Deep-dive modules could be then used to elaborate on a subject matter like (for audiences familiar with code)
    <ul>
      <li></li>
    </ul>
  </li>
</ul>

<h2>Link to materials</h2>

<p>Resources overview</p>

    <ul>
        <li>Source code: <a href="https://github.com/flaki/ck-service-workers/">GitHub</a></li>
        <li>Live demo: <a href="http://flaki.github.com/ck-service-workers/index.html">Service Worker Content Kit</a></li>
        <li>Issue tracker/feedback: <a href="https://github.com/flaki/ck-service-workers/issues">GitHub Issues</a></li>
        <li>Builds:</li>
    </ul>

<p>Supporting docs/references</p>

    <ul>
        <li>Docs: <a href="https://developer.mozilla.org/en-US/docs/Web/API/Service_Worker_API">MDN</a></li>
        <li>Specification: <a href="#https://slightlyoff.github.io/ServiceWorker/spec/service_worker/index.html">Service Workers</a></li>
        <li>Tutorial: <a href="http://www.html5rocks.com/en/tutorials/service-worker/introduction/">Introduction to Service Worker</a></li>
        <li>Implementation status: <a href="https://jakearchibald.github.io/isserviceworkerready/">isServiceWorkerReady?</a></li>
        <li>Service worker news: <a href="https://twitter.com/service_workers">@service_workers</a></li>
    </ul>


<h2>Presentation setup</h2>

<ul>
  <li>Link to slides</li>
  <li>Links to videos of the presentation materials being used (optional)</li>
</ul>

<p>Include notes here on presenting or using the materials</p>

<h2>Demo setup</h2>

<ul>
  <li>Link to demos</li>
  <li>Demo script:
    <ul>
      <li>A walkthrough of how to run the demo</li>
      <li>Main points to make</li>
    </ul>
  </li>
  <li>Troubleshooting:
    <ul>
      <li>Things that might be broken</li>
      <li>Things that might be broken</li>
    </ul>
  </li>
  <li>Links to videos of the demos being used</li>
  <li>Instructions for how to give the demo offline</li>
</ul>

<h2>Active learning</h2>

<p>If possible, include some kind of active learning mechanism in your content kit slides, to break up the presentation a bit. This may include links to demos that the audience can play with, live coding sections, demos that include participation from the audience, etc.</p>

<h2>Frequently asked questions (FAQs)</h2>

<p>
Refer to the <a href="faq.html">FAQ section</a>.
</p>

<p>
To add your own answers from your previous experiences, submit a pull request to the 
<a href="https://github.com/flaki/ck-service-workers/blob/gh-pages/FAQ.md">FAQ.md</a> file,
or ask your own questions in the <a href="https://github.com/flaki/ck-service-workers">issues section</a>.
</p>
{'fraction_non_alphanumeric': 0.12861511577107906, 'fraction_numerical': 0.007164700742682394, 'mean_word_length': 3.923010752688172, 'pattern_counts': {'":': 0, '<': 376, '<?xml version=': 0, '>': 376, 'https://': 20, 'lorem ipsum': 0, 'www.': 2, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '555050', 'n_tokens_mistral': 3666, 'n_tokens_neox': 3496, 'n_words': 1227}