Revise add-ons documentation links and text#19742
Conversation
Updated links and descriptions for the add-ons resources.
There was a problem hiding this comment.
Pull request overview
Updates the NVDA add-ons developer documentation to reflect current official resources and reduce reliance on legacy links.
Changes:
- Replaces the legacy “Community add-ons website” link and note with the newer Add-on Store website link.
- Updates the add-on template link to point to the nvaccess/AddonTemplate repository.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
|
hi,
Additionally, Here're some add-on stores that I find valuable.
|
|
@kaveinthran wrote:
Thanks for your mention. The webpage mentioned owned by me (nvdaes) is not a store. It's just a webpage created for testing when the official add-on store was created. Now NV Access has addonstore.nvaccess.org, and imo adding other sources for things that aren't owned by NV Access, not maintained by them and which aren't specific to documentation, in a section about documentation, is not a good idea. |
|
Thanks for the clarification, and I totally agree with your consent and
recommendation. If adding a separate section for third-party documentation
with disclaimer/caveats could be considered, that would be great as well.
…On Thu, Mar 5, 2026 at 1:42 PM Noelia Ruiz Martínez < ***@***.***> wrote:
*nvdaes* left a comment (nvaccess/nvda#19742)
<#19742 (comment)>
@kaveinthran <https://github.com/kaveinthran> wrote:
Additionally, Here're some add-on stores that I find valuable.
Thanks for your mention. The webpage mentioned owned by me (nvdaes) is not
a store. It's just a webpage created for testing when the official add-on
store was created. Now NV Access has addonstore.nvaccess.org, and imo
adding other sources for things that aren't owned by NV Access, not
maintained by them and which aren't specific to documentation, in a section
about documentation, is not a good idea.
If other stores are added, I think that this should be done in a different
section, and with a justified purpose, explaining that these aren't
maintained by NV Access, and explaining that the official store allows NVDA
to check for add-ons integrity with sha-256, checks add-ons with virusTotal
and CodeQL, and that other stores may not have these features. But fur the
nvdaes website, which is independent to the add-ons directory, I think that
this website owned by me shouldn't be included since it should be very
similar to the addonstore.nvaccess.org, it's not maintained, and may be
confusing.
Anyway thanks so much.
—
Reply to this email directly, view it on GitHub
<#19742 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AFPTEY7IF75PLHX7AXHOJRT4PEHSRAVCNFSM6AAAAACWHMG3F6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DAMBSGM3TKMJVGU>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
Thank you so much @kaveinthran . Unless a separate section is created for external websites with a clear purpose, I plan to remove this website (or better,, unpublish it): https://nvdaes.github.io/nvdastore/ @seanbudd , unless you think that a backup is useful with clarifications about possible lack or maintenance, I'll unpublish this to avoid confusions. |
|
@nvdaes please don't unpublish, it greatly benefit to look for add-on info in one page like that. |
|
@kaveinthran wrote:
|
No description provided.