This Starter enables you to build a basic application with PWA capabilities on Enonic XP Platform. It’s using modern tools like Webpack for the build process and Workbox for automatic generation of Service Worker file and dynamic response caching. Simple routing is powered by Enonic Router library.

1.Make sure you have Enonic XP of version 6.12 or later installed locally. If not, read how to install it here:

2.Set up environment variable XP_INSTALL that points to the XP installation folder:

We assume that XP service is running on localhost:8000 and your app is called com.company.myapp as in example above.

1. Open http://localhost:8080/app/com.company.myapp in your browser. You should see this:

2.Click the "About" link in the header to open http://localhost:8080/app/com.company.myapp/about. You should see this:

3.Now’s the fun part. Go offline (either by turning off the Wi-Fi or unplugging cable or checking off "Offline" in the Dev Tools). Content of the About page should now change like this:

4.Go back to the main page. It should now look like this:

As you can see, the Starter can track its online/offline status and change content of its pages accordingly.

You are now ready to expand the application’s functionality, plug in any Front-end framework etc.

The Starter is using Webpack to build all LESS files into one CSS bundle (bundle.css) and all Javascript assets into one JS bundle (bundle.js). The Workbox plugin is used by Webpack to automatically generate a template for the Service Worker (sw-template.js) based on a predefined file (sw-template.js). Final Service Worker file will be rendered on-the-fly by Enonic Router lib by intercepting a call to /sw.js file in the site root.

js/main.js is used as entry point for the Webpack builder, so make sure you add first level of dependencies to this file (using require). For example, if js/main.js is using a LESS file called styles.less, add the following line to the main.js:

Same with JS-dependencies. For example, to include a file called about.js from the same js folder add this line to main.js:

You can then require other LESS or JS files directly from about.js effectively building a chain of dependencies that Webpack will resolve during the build.

As mentioned before, the build process will bundle all LESS and JS assets into bundle.css and bundle.js files in the precache folder which can then be referenced directly from the main.html page.

When the application is launched for the first time, Service Worker will attempt to precache the Application Shell - the minimum set of assets required for the application to continue working while offline. As described above, two files - bundle.css and bundle.js - generated by the build process will be precached by default. In addition, you may add any files to the assets/precache folder and they will automatically be added to the list of precached assets. Typically that would be images, icons, font files, 3rd-party stylesheets and Javascript libraries etc.

Empty square brackets in The last line is the placeholder which after the build will be filled with paths to actual assets from the precache folder, something like this:

Sometimes you may need to cache assets outside of the precache folder. In this case you have to explicitly specify the assets that you need to be cached (this can be a local asset or an external URL). Add a new line with a call to workboxSW.precache after the one with empty placeholder:

Application Manifest is a file in JSON format which turns the application into a PWA. Starter comes with its own manifest.json with hardcoded title, color scheme, display settings and favicon. Feel free to change the predefined settings: the file is located directly in the /assets/ folder.

Default favicon used by the Starter is called icon.png and located in precache/icons/ folder, so you can simply replace this icon with your own of the same name. If you want to use a different icon file, add it to the same location and change main.html to point to the new icon. Don’t forget to make same changes in manifest.json and browserconfig.xml.

This Starter is not a traditional site with plain HTML pages - everything is driven by a controller. Just like resources/assets/js/main.js is an entry point of the Starter’s client-side bundle, resources/main.js is an entry point and the main controller for the server-side execution. Setting it up is simple - just add handler of the GET request to main.js file and return response in form of rendered template or a simple string:

If your application name is com.enonic.starter.pwa and Enonic web server is launched on localhost:8000 then http://localhost:8080/app/com.enonic.starter.pwa/ will open the main page of your app.

If your application is not a single-page app, you are going to need some routing capabilities. The Starter is using Enonic Router library which makes it incredibly simple to dynamically route a request to correct page template. First, let’s change the default page to render a proper template instead of a simple string. Let’s say, we have a main.html template in the /resources/pages/.

Here we told the Router to respond to the "/" request (which is the app’s main page) with the rendered template from /pages/main.html.

Now let’s expand this to enable routing to other pages. Let’s say, we need two pages called "About" and "Contact" which should open via /about and /contact URLs correspondingly.

That’s it, we have just built a simple routing inside the main.js file. You can pass custom rendering parameters to each template inside the {} argument.

When you’re building a PWA you typically want a user to be able to open previously visited pages even when the application is offline. In this Starter we are using Workbox to dynamically cache URL requests for future use.

Here we cache requests to the /about and /contact URLs mentioned above, as well as request to the 3rd-party font file on an external URL.