Support PWA for offline documentation usage
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 11.8k
- Forks
- 7.9k
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 11
Description
Hi there,
Saw that #4526 addressed this, and that the OP actually went ahead and submitted merge request #4530. The merge request was rejected because it was unknown what the tradeoffs of including a manifest and service worker were.
I wanted to maybe restart the conversation on this, I think it'd be beneficial to have the docs be available in their original format for offline consumption. There are obviously work arounds (cloning and serving the site locally, offline docs providers), but both of those have fairly significant drawbacks and aren't as easy as right click installing the page.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing issue #4526 and merge request #4530, including why the earlier proposal was rejected. Evaluate the tradeoffs of adding a web manifest and service worker, then define what offline documentation availability and installation should provide before implementation begins.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- documentation, web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100