డాక్యుమెంటేషన్ ప్రస్తుతానికి ఇంగ్లీష్-మాత్రమే. మిగిలిన సైట్ మీ భాషను అనుసరిస్తుంది.
Progressive Web App
Turn the public site into an installable, offline-friendly PWA from Settings → PWA — no build step, plugin, or file edit.
6 నిమి చదవబడింది
Settings → PWA turns a public site into an installable, offline-friendly Progressive Web App: app identity and generated icons, theme and background colors, display mode, a validated start URL, up to four app shortcuts, an install prompt, and a branded offline fallback. It's disabled by default, and enabling it needs no build step, plugin, or file edit.
What gets generated
| Route | Serves |
|---|---|
GET /manifest.webmanifest | The web app manifest, built from your saved settings on every request. |
GET /sw.js | The service worker: bounded static-asset caching, plus the offline fallback. |
GET /pwa-offline.html | The branded page shown when a visitor is offline and the page isn't cached. |
The manifest id and service-worker scope are always the site root and are not configurable.
Settings
| Field | Meaning |
|---|---|
| App name / short name / description | Manifest identity. |
| Icons | icon192Url / icon512Url / appleTouchIconUrl are generated; maskable variants are optional. |
| Theme / background color | Manifest theme_color / background_color. |
| Display mode | standalone (default), fullscreen, minimal-ui, or browser. |
| Start URL | Defaults to /; validated against a blocked-prefix list (/admin, /api, /login, /install). |
| Shortcuts | Up to 4 app shortcuts. |
| Install prompt | Enable, label, description, and whether to show the site logo. |
| Offline fallback | Title, message, and image for pwa-offline.html. |
| Asset cache | Enable, max entries, and max age for the service worker's static-asset cache (default 100 entries / 7 days). |
Disabling
Turning PWA off doesn't remove /sw.js — it keeps answering at the same URL, but as a stub whose only job is to delete every Justflows PWA cache and unregister itself, so an already-installed app recovers cleanly without manual cleanup.
Note
No environment variables are involved — everything is stored settings, applied live. A static / edge export seeds the manifest, service worker, and offline page into the crawl and regenerates them on the next export run.