Jam Build

A web application reference of a custom static site, but as a versionable, offline, service-worker MPA, with batching, multi-user OCC, RBAC authz, and data on top.

Minimal, hand-crafted vanillajs by a human.

Quick Links

• 🚀 Getting Started
• 💡 How This is Different
• ⚡ Static Site Generator
• 📊 Data Store and Flow Architecture
• 📡 Batch Update and Conflict Flow
• ⏳ Service Worker Timer Architecture
• 🧪 Testing Procedure and Detail
• 🎭 Performance Audits
• 🔧 Build Process Summary
• ✨ Command Reference
• 📈 Project Stats Snapshots

Project Summary

Overview

This project serves as a starting point for a PWA (Progressive Web Application). It builds a versionable, offline-first, multi-page JAM (JavaScript, APIs, Markup) web app with support for multi-user data.

Key Features

• Service Worker First:

  • The project design centers around a service worker, which is different from most web applications.

• Custom Sass/Handlebars Static Site Generator:

  • A multi-page application built using a custom static site generator that leverages Sass and Handlebars.
  • Image processors generate metadata used to render preload tags and other performance-oriented styles and markup.
    • Custom WASM image processor pipeline for performant optimization and webp format creation. Boosts build speed and reduces external toolchain dependencies. Eases application image maintenance, reduces image size.
  • See the static site generator document for more detail.
  • Static site only branch (sans data layer) available.

• Offline Capabilities:

  • Pages are rendered directly from the service worker cache using a stale-while-revalidate strategy.
  • Service worker manages offline data updates and reconciliation when the network is restored.

• Version Updates:

  • The service worker handles version updates and ensures that users receive the latest static pages and app versions.
  • Supports versioned deployment for both front-end and back-end components.

• Service Worker Data Update Batching:

  • Data mutations are staged in IndexedDB and committed to the API in offline supported batch processes, optimized for resource usage.

• Optimistic Concurrency Control:

  • The service worker and data service handle multi-user optimistic concurrency control with three-way merge resolution.

• Role-Based Access Control:

  • Supports role-based access control for different user roles (e.g., user, admin).

• Reusable, General Data Design:

  • Features a reusable, general data design with application and user regions.

• Established Toolchain:

  • Uses a well-established toolchain with no magic (no hidden or complex processes) and minimal dependencies.

Technology Stack

• Vanillajs, plain Javascript Object persistent nanostores

Runtime Dependencies

• Expressjs
• Workboxjs
• Authorizer
• Mariadb

Development Dependencies

• Handlebars
• Sass
• Playwright
• Gulp
• Rollup
• Docker
• Localnerve

Donate

If this project is helpful or useful to you, please consider donating to help me create and maintain more great things.

I'm also available for hire.

Author and License

Jam-build, a web application practical reference.
Copyright (c) 2025 Alex Grant info@localnerve.com (https://www.localnerve.com), LocalNerve LLC

Jam-build is free software: you can redistribute it and/or modify it under the terms of the GNU Affero General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version. Jam-build is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU Affero General Public License for more details.
Additional terms under GNU AGPL version 3 section 7:
a) The reasonable legal notice of original copyright and author attribution must be preserved
by including the string: "Copyright (c) 2025 Alex Grant info@localnerve.com (https://www.localnerve.com), LocalNerve LLC"
in this material, copies, or source code of derived works.