MicrosoftEdge / MicrosoftEdge/Demos
Clarify equivalence of /pwa-pwastore/ & /pwa-installer/
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 330
- Forks
- 233
- Avg merge
- 21h 12m
- Merged PRs (30d)
- 4
Description
Need to state the relation between the /pwa-pwastore/ & /pwa-installer/ samples/dirs, in:
- Readme for /pwa-pwastore/
- Readme for /pwa-installer/
- The regular article's section about PWA installer
- The PWA table in this repo's main Readme
Details/research
This repo's main dir
https://github.com/MicrosoftEdge/Demos
lists the /pwa-pwastore/ dir:
https://github.com/MicrosoftEdge/Demos/tree/main/pwa-pwastore
yet that dir / sample isn't listed in Readme eg the PWA table:
https://github.com/MicrosoftEdge/Demos?tab=readme-ov-file#progressive-web-apps-pwas
The table instead, only, lists pwa-installer.
https://github.com/MicrosoftEdge/Demos/tree/main/pwa-installer
Other aspect of same issue: The article section "PWA installer"
https://learn.microsoft.com/microsoft-edge/progressive-web-apps/demo-pwas#pwa-installer
instead links to:
- https://microsoftedge.github.io/Demos/pwa-pwastore/
- https://github.com/MicrosoftEdge/Demos/tree/main/pwa-pwastore
Shouldn't that article section link instead to pwa-installer instead? Or, in addition? see draft:
https://review.learn.microsoft.com/microsoft-edge/progressive-web-apps/samples/?branch=pr-en-us-3476#pwa-installer
Contributor guide
No contributing guide indexed for this repository
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
Compare the pwa-pwastore and pwa-installer README files, the main README's Progressive Web Apps table, and the article's PWA installer section, including the linked draft. Determine how the two samples relate and update the listed documentation and links consistently; done means each location clearly identifies the intended sample and links are aligned.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100