Skip to content

docs(pwa): clarify what Needle handles automatically + add gotchas#216

Open
kaktus-klaus wants to merge 1 commit intoneedle-tools:mainfrom
kaktus-klaus:docs/improve-pwa-docs
Open

docs(pwa): clarify what Needle handles automatically + add gotchas#216
kaktus-klaus wants to merge 1 commit intoneedle-tools:mainfrom
kaktus-klaus:docs/improve-pwa-docs

Conversation

@kaktus-klaus
Copy link
Collaborator

Summary

Improves the PWA documentation based on feedback that it sounded like users had to handle everything themselves — when in fact Needle's plugin takes care of most of the hard parts.

Changes:

  • Add "What Needle handles for you" section at the top — explicitly calls out:
    • All build assets pre-cached automatically (3D, textures, audio, WASM)
    • .gz files excluded from pre-cache (avoids bad-precaching-response 404s)
    • SPA routing fallback configured automatically
    • Web manifest auto-generated with sensible defaults
  • Add "What to watch out for" section with practical gotchas:
    • First visit must be online
    • External/dynamic assets are not pre-cached
    • Large projects may want to narrow globPatterns
  • Improve offline/kiosk section with a concrete actionable checklist

Why

The previous docs described PWA setup without making it clear what Needle's plugin handles vs. what the developer needs to do. The impression was that users needed to handle things like .gz exclusion and SPA routing themselves, when in fact these are handled automatically.

🤖 Generated with Claude Code

…tion

- Add "What Needle handles for you" section at the top — makes it clear
  that pre-caching, .gz exclusion, SPA routing, and manifest generation
  are all handled automatically (docs previously sounded like users had
  to figure all this out themselves)
- Add "What to watch out for" section with practical gotchas:
  * First visit must be online
  * External/dynamic assets are not pre-cached
  * Large projects may want to limit globPatterns
- Improve offline/kiosk section with a concrete checklist
- Remove ambiguous tip about all assets being cached; integrate that
  information more clearly with the new structure

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@bolt-new-by-stackblitz
Copy link

Review PR in StackBlitz Codeflow Run & review this pull request in StackBlitz Codeflow.

@kaktus-klaus
Copy link
Collaborator Author

@hybridherbst Would love your review on this PWA docs improvement when you have a moment! 🙏

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant