Feature/sta 227

[HughG]

Hi Dave, sorry this has been delayed so long! I'm taking a break from the daily grind of job-hunting, so maybe I can get this finished at last.

Implemented generation of in-app help screens from Markdown files.

• The existing Help screens are still used by default. To view the new ones, turn on the relevant Settings -> Debug option in the app, then restart it.
• One expected change which I think is okay, is that the FAQ sub-screens now have "Frequently Asked Questions" as the header, rather than "FAQ".
• One issue with the new screens is that the FAQ page in-text headings are at one level lower than before, hence the heading text is smaller. Could hack in a workaround to use a higher heading level for those sub-pages.
• The new screens are currently only there for English.
• Generation of the website should still work, even though the Markdown files moved, because I updated the jekyll build step to copy them into the expected plate. I tested it at one point, but can't remember how now, so it may or may not still work!

I think the next steps are as follows, either in this ticket, or in a follow-on if this is okay to merge.

• Write a little script to pull out translated Markdown files for all other locales.
• Create a separate Weblate Component for each Markdown file.
• Pre-populate the translations on Weblate for each Markdown component with the text pulled from the already-translated help string files. (I can probably knock up a script to create the files, but I'm not sure how easy it would be to bulk-upload them — I've never tried.)
• Once at least a few locales are tested, switch to the new code permanently, then remove the old code.

Then someone could think about actually editing the files! Weblate seems to be smart enough if you add/remove new sections: it adds a matching English section to each translated Markdown file.

[HughG]

Hi again, @davecraig. I've merged in the KMP changes and got the Markdown help pages basically working, tested for English (not sure how to test other locales), with a couple of TODOs. Come to think of it, I suspect other locales will not work until you translate the entry page, help-and-tutorials.md.

The website docs still appear to build correctly, but whatever script you have for regenerating the Markdown from the resource strings will need to updated to write them to '/app/src/main/assets/help`.

So, this branch should be ready to merge, but I can't guarantee it won't break main.