Proposed Add-on Store user guide section revisions #14961
Conversation
…-ons are, and explain that it being a "store" does not mean users must pay.
… noted view changing via arrow keys.
…e first one to "Filtering for enabled or disabled add-ons".
…uctory section, explaining enabled/disabled states.
…. Moved explanations before usage instructions.
…uctions on how to reach the search field.
…isplay name, publisher and description.", because there are no instructions.
…", because that has been used to describe NV Access accepting add-ons into the store, by some members in the community, and I wanted to make clear that they are not "vetted" in any way.
…ince the cases are specific.
…able all add-ons.
|
@seanbudd and/or @Qchristensen While I did not try to change it here, why are we still using the old " In any case, it seems strange since the store is an entirely new concept. |
In the wild, there may be links on the user guide targeting this paragraph. Keeping the old add-on manager anchor allows to avoid these links to be broken and to point to the paragraph which describes what has become the add-on manager. |
So would creating an HTML anchor immediately before the Add-on Store section, that manually redirects links there, while still enabling us to name the chapter appropriately. E.g.: That is valid T2T code, according to the spec. |
Yes, this fully makes sense to me. |
|
Strangely, GitHub will not let me re-open and re-target this PR |
|
Opened as a new PR with a clean branch. Had to cherry-pick it back into master, as it wouldn't let me rebase in. |
Replaced by PR #14966