I noticed that several projects also use github/releases to tag new versions

https://github.com/WeakAuras/WeakAuras2
https://github.com/Aviana/LunaUnitFrames

It shouldn't be too hard to add another module to be able to pull all of these directly from github.
More research is needed, fetching contributors should be straightforward, and we can use the github api to detect new versions

Suppose a user wants to switch to WoA but they already have addons installed (Possibly due to previously using Curse/Twitch).
As of WoA 1.0.0, there is no mechanism to detect addons that are already installed.
Any previously installed "untracked" addons will not be in addons.json and WoA will not be able to update or manage them (WoA will be able to detect them thanks to chokidar, but it can't do anything to them).

This story shall be considered complete when:

• WoA detects what addons are installed but are not in addons.json.
• If an addon is hosted on multiple sites (curseforge, wowinterface, github) then WoA will offer a choice of where to install from.
• This system is secure from tampering so there is credit to addon creators (incorporate donation/patreon links), transparent so people can trust there is no malware, and decentralized so that no site/host can monopolize addon distribution,

Story shall be considered complete when,

• A new button is added that can cancel Installing/Updating/Uninstalling a new addon

Use docpress, or another documentation generator to create project website. Then add this to one of the build steps for the CICD pipeline.

example: http://docpress.github.io/#examples

My young naive mind didn't realize that any installer or executable we create will need to be signed or else Windows smartscreen will complain or an antivirus will immediately delete/sandbox WoA.

On a separate note, all releases are built remotely and automatically pushed to github with appveyor, so no human is actually deploying releases.

I'm also not too sure I understand what needs to be done with regard to signing our application

The following blue screen will pop up because we do not have the executable signed. It may cause anti-viruses to remove World of Addons or sandbox the entire program.
We need to either spend big $$$ every year to sign an OPEN SOURCE project or we hope people see that we are honest and transparent; we don't have any interest in developing malware.

This really sucks, I get why it has to be like this but it really sucks.

Project Repo: https://git.tukui.org/elvui/elvui/tree/master/ElvUI

Version: <a class="commit-row-message item-title" href="/elvui/elvui/commit/74e91ccb1450fd839c709ba0940158f47e4536d8">Release v10.83</a>

Target URL: https://git.tukui.org/elvui/elvui/-/archive/master/elvui-master.zip

This looks like a pretty straightforward integration. Not sure how to fetch author list.

Re-design our UI.
Currently we keep track of addon contributors/authors, addon subdirectories, addon version, and the addon's host, however we don't show everything.

This story shall be considered complete when:
A new design shall display addon contributors/authors, addon subdirectories, addon version, and addon's host, while maintaining simple controls to update, install, and uninstall addons.
A new design PR shall be submitted to /dev.

I don't write good. pls help write wiki

Need help for the following wiki pages:

• https://github.com/WorldofAddons/worldofaddons/wiki/How-to-use-World-of-Addons

Story shall be considered done when
The wiki shall explain in plain english how to install World of Addons client.
The wiki shall explain in plain english how to update World of Addons client.
The wiki shall explain in plain english how to install addons for all supported sites.