Refactoring the code into a browser extension and server side code

[asirota]

This is a big change, probably for a 3.0 of WATM.

Refactor the code into 2 pieces:

1. A browser extension that runs in all modern browsers (leave Safari out for now) that is installed by end user from the Chrome web store. This browser extension gets licensed and then asks for a WA admin password. It installs the necessary Global Javascript required to operate WATM

2. The code that is added to the site simply reads the config files that are edited by the extension and makes the necessary changes.

What do we get for this?

The browser extension running on a browser can modify not just the public website, but also the WA administrative interface. This gives WATM ability to

• change elements in the WA admin
• add an advertisement
• remove ads
• add a link to a feature that NewPath sells (eg WildApricot Hero)

[asirota]

Things to consider:

How to sell WATM (free, freemium, monthly subscription for certain features?)
What happens if WA changes their code to stop our add on from communicating with admin?