Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/losyoguis/149tresbandas/llms.txt

Use this file to discover all available pages before exploring further.

The Entrenador de Carambola Guiada ships with a complete manifest.webmanifest and a registered Service Worker, giving it full Progressive Web App (PWA) support. Once installed, the trainer runs in its own window with no browser chrome, responds to your home screen icon, and works entirely offline after the first load.

​
App Manifest

The manifest defines the app identity, appearance, and launch behaviour:
PropertyValue
NameEntrenador de Carambola Guiada
Short nameEntrenador
Display modestandalone (no browser chrome when installed)
Orientationany
Theme color#07110e (dark green)
Background color#06110d
Icons48 px · 72 px · 96 px · 128 px · 144 px · 152 px · 192 px · 384 px · 512 px
Start URL./ (relative — works with any GitHub Pages base path)
manifest.webmanifest
{
  "name": "Entrenador de Carambola Guiada",
  "short_name": "Entrenador",
  "description": "Entrenador profesional de carambola guiada para billar a tres bandas...",
  "start_url": "./",
  "display": "standalone",
  "orientation": "any",
  "background_color": "#06110d",
  "theme_color": "#07110e"
}

​
Installation Steps by Platform

1

Open the GitHub Pages URL in Chrome

Navigate to your published URL (e.g. https://losyoguis.github.io/149tresbandas/) in Chrome for Android.
2

Tap the install prompt or menu option

Chrome may display an Add to Home Screen banner automatically. If not, tap the three-dot menu (⋮) in the top-right corner and select Add to Home screen or Install app.
3

Confirm the installation

Tap Add in the confirmation dialog. The Entrenador icon will appear on your home screen. For the best play experience, rotate your device to landscape orientation.

​
Service Worker and Offline Use

The Service Worker (cache key entrenador-carambola-guiada-production-v235-corner-power) runs at the repository root scope and manages a versioned cache of static assets. What is pre-cached on first install:
  • index.html, css/styles.css, js/app.js
  • manifest.webmanifest and all icon files (icon-48.png through icon-512.png)
What is cached on demand:
  • All images in assets/jugadas/ — each play’s three image files (posicion_inicial_NNN.webp, recorrido_guia_NNN.webp, guia_referencia_NNN.png) are stored in the cache the first time they are requested. After every play is visited at least once, all 148 plays (444 images total) are available offline.
After installation, core app functionality works fully offline from the first load. As you browse plays, the Service Worker caches each play’s images so that subsequent visits work without any network requests. What requires an internet connection:
  • The Videotutorial — video streams from YouTube or Google Drive are not cached by the Service Worker. An active connection is required to play the video tutorial.
Cache invalidation on updates: When a new version is deployed, the Service Worker cache key is incremented (e.g. production-v235-corner-power → production-v236-...). On the next visit, the new worker installs alongside the old one, downloads the updated assets, and takes control on the following page load.
Each version update increments the Service Worker cache key, ensuring every user automatically receives fresh assets after a deployment — without needing to manually clear their browser cache. If you need to force an immediate update during testing, open DevTools → Application → Service Workers → Unregister, then reload the page.

Build docs developers (and LLMs) love

Get started for freeTalk to us