Hi everybody,
I originally wrote the 'Learn Plover' tutorials on Google Sites, as an easy web-hosting solution.
Gradually a few people in the plover community asked for 'write permission', which I happily granted. But it's become clear that 'Learn Plover' should really be a fully community-maintained and open-sourced site, and not something that is only for a few people to control.
I haven't been very involved in plover for the past several years, and so I've been comfortable to kick the can down the road, make fixes when someone reported a bug, but otherwise not deal with the issue. But now, Google is changing the whole Google Sites feature into something that doesn't support the formatting I use to identify keypresses. They're forcing Sites users to 'upgrade', and so it's not really realistic to stick with the status quo anymore. What other changes might be forced on Sites users in the future?
So I'd like to hear suggestions about what should be done with the site.
It seems like 'Learn Plover' is still a valuable resource. Maybe it should be incorporated into the github repository with the plover source code, and be viewed entirely on github? Maybe it should be converted to a 'real' HTML site with JavaScript and all the trimmings, and hosted on a community-run server?
Tim G has already volunteered to help with some of the HTML/CSS/JS stuff (and his interest partly inspired this RFC), and maybe other people would like to volunteer too? Is it possible we could put together a team that would each offer part of the software/hardware that would be needed to migrate away from Google Sites?
What are your thoughts? What does the Plover community want from 'Learn Plover'? Where should it go and how should it get there?
Be well,
Zack