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 is designed for zero-config GitHub Pages deployment. All file paths are relative (css/styles.css, js/app.js, manifest.webmanifest, assets/jugadas/), so the trainer works from any GitHub Pages URL without environment-specific configuration or a build step.

​
Deploy in Three Steps

1

Push files to GitHub

Push the full repository — including the assets/jugadas/ folder — to the main branch. Every image file for all 148 plays must be present before you enable Pages.
git add .
git commit -m "Deploy Entrenador de Carambola Guiada"
git push origin main
2

Enable GitHub Pages

In your repository, go to Settings → Pages. Under Source, set the branch to main and the folder to / (root), then click Save. GitHub will begin building and publishing the site.
3

Open the published URL

GitHub will display the published URL — usually https://<user>.github.io/<repo>/. Open it in your browser. If you have previously loaded an older version of the trainer, clear your browser cache on the first visit to ensure the latest assets load correctly.
The assets/jugadas/ folder is large: 148 plays × 3 images each = 444 files. Make sure every file is committed and pushed to the main branch before you enable GitHub Pages. Missing images will result in broken play previews with no error message in the UI.

​
The .nojekyll File

A .nojekyll file must be present in the repository root. It tells GitHub Pages to skip Jekyll processing entirely, which is necessary because Jekyll silently ignores folders and files whose names start with an underscore (_) and can interfere with asset loading for any non-standard path. 
# Create .nojekyll in the repo root before pushing
touch .nojekyll
git add .nojekyll
git commit -m "Add .nojekyll to disable Jekyll processing"
git push origin main
Without this file, GitHub Pages may run Jekyll and interfere with asset loading.

​
Clearing Old Cache

The Service Worker (cache key entrenador-carambola-guiada-production-v235-corner-power) automatically caches all static assets on first load, which means users upgrading from an older deployed version may see stale content until the cache is invalidated. To force a refresh after deploying a new version:
  • Hard reload — press Ctrl+Shift+R on Windows/Linux, or Cmd+Shift+R on macOS.
  • Unregister the Service Worker manually — open DevTools (F12), go to Application → Service Workers, click Unregister next to the trainer’s worker, then reload the page.
Each new deployment increments the Service Worker cache key (e.g. production-v235-corner-power → production-v236-...), which automatically triggers a cache refresh for returning visitors on their next page load.

Build docs developers (and LLMs) love

Get started for freeTalk to us