I'd be interested in maintaining the website, but I can't make any promises on actual plover knowledge. On Saturday, November 6, 2021 at 6:28:52 AM UTC-4 [email protected] wrote:
> In the R community, we have developed a very successful solution through a > tool called bookdown <https://bookdown.org/>. > > bookdown is based on R Markdown, which is a document format that is > similar to Markdown. It's very easy to read and contribute to. It's > allowed the R community a wonderful freedom of collaboration on a slew of > books, with people suggesting everything from typo corrections to entire > section re-writes. You may need to know a bit of R to set it up from > scratch. But you don't need to know any R to contribute. I would be easy to > maintain. > > But R Markdown is also a collection of engines (primarily relying on > Pandoc) that allow you to export your content to PDF, LaTeX, HTML, EPUB, > and Word etc. bookdown would control how the components are rendered in the > various formats. > > For HTML output, the default engine is GitBook, but there's also built-in > support for Bootstrap and Tufte > <https://bookdown.org/yihui/bookdown/html.html>. Hosting is usually very > easy with either Github pages or Netlify. > > I'd be happy to put together a skeleton of what it would look like? And > people could try it out and see if it worked for them? But I wouldn't be > available to maintain it full time or migrate the content. > > On Friday, November 5, 2021 at 4:10:59 PM UTC [email protected] wrote: > >> While writing Art of Chording, VuePress <https://vuepress.vuejs.org/> >> has been a really nice tool. Others that I looked at were Gatsby >> <https://www.gatsbyjs.com/> and Docusaurus <https://docusaurus.io/>. >> Both seem like they'd fit the bill if you can get a developer who has a >> little bit of React or Vue experience. >> >> With GitHub Actions, building the code and deploying it to GitHub Pages >> is easy, fast, and free. If I were doing this project, I would move it to a >> GitHub repo and convert to one of the tools above then invite the >> maintainers to the GitHub repository. >> >> The only concern with moving to a GitHub repository that I see is >> maintaining an open source project is hard work and there are certain >> expectations with fielding issues and pull requests, so whoever takes over >> should be ready to deal with that or explain in the readme what >> contributions are acceptable and which aren't. >> >> Best of luck, >> >> On Friday, November 5, 2021 at 8:33:03 AM UTC-4 [email protected] >> wrote: >> >>> I definitely agree that putting it out there for others to contribute >>> would be beneficial. Regarding hosting, I'd recommend using a GitHub >>> Repository with Github Pages (https://pages.github.com) as it is free >>> and can be integrated directly with the "source" files. Storing images and >>> other media in the repository is definitely possible too. It makes it easy >>> for others to contribute but also for other people to extend it (I've >>> recently hacked together a tool which scrapes the Google Site and creates a >>> somewhat usable E-Book to read on my Kindle — perfect candidate for a >>> contribution). >>> >>> For formatting, something "common" like Markdown is most likely the best >>> as it allows easy contribution and conversion into a multitude of formats >>> (e.g. EPUB). Concerning special formatting: AFAIK you are using bold, >>> monospaced, and inverted text on a dark background. Bold and monospace are >>> supported by default in Markdown and "highlighted" text should definitely >>> be possible with one of the many "common" extensions (e.g. some ==marked== >>> text). When converting to HTML, adding a few custom CSS rules to style it >>> in your preferred way should be rather simple. >>> >>> Speaking of conversion and special CSS, static page builders like >>> https://www.11ty.dev or https://astro.build come to mind. >>> On Friday, November 5, 2021 at 9:05:01 AM UTC+1 [email protected] wrote: >>> >>>> Hi everybody, >>>> >>>> I originally wrote the 'Learn Plover' tutorials on Google Sites, as an >>>> easy web-hosting solution. >>>> >>>> https://sites.google.com/site/learnplover/ >>>> >>>> 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 >>>> >>>> -- You received this message because you are subscribed to the Google Groups "Plover" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/ploversteno/a37f3e53-5808-4844-b2e1-41d99784068fn%40googlegroups.com.
