Thank you for replying, The reason we use Wordpress is that this is the
solution that was recommended by the experts with whom we consulted. While
the tutorial is largely static, we wanted to have the option of a CMS to
update content, add topics or exercises, and even to be able to add the
tutorial in additional languages. I wonder if you could elaborate more
about "a process that statified its content before publishing on
toolforge"? Bear in mind I don't have any technical/IT background.
בתאריך יום א׳, 2 באוג׳ 2020 ב-4:50 מאת Platonides <platonides(a)gmail.com
Keeping the code of a Wordpress site up-to-date is not generally hard.
However, in this case, and even more relevant given your query, I must ask:
why use wordpress? This seems a static set of pages, so it could be stored
as .html pages without the overhead of running wordpress... or the security
issues that might happen if that was abused. No code = no security issues.*
This could be developed as html pages (you are probably using raw html
markup already), or if you fancy preparing that in wordpress, you could
have a wordpress for editing the tutorial, and then have a process that
statified its content before publishing on toolforge.
* Or almost. I'm glossing over potential vulnerabilities on the web
removing the web application means the system hundreds of times safer.
Wikimedia Cloud Services mailing list
Cloud(a)lists.wikimedia.org (formerly labs-l(a)lists.wikimedia.org)