Technology we use
Here is a list of the tools we use to make this platform work. Of course each of them depends in turn by other tools (for instance Quasar Framework depends on Vue.js, and Vue.js is in turn composed by several components, like the router and vuex, a "state management pattern"), however, given a set even arbitrary of the most prominent tools we use, the reader might explore on his or her own both in extension and in depth the vast areas not covered by the following table.
|Mediawiki 1.34||The collaboration and documentation platform which inspired and powers Wikipedia.||We use it for the back-end side of this site, in order to ensure collaborative creation of quality contents.|
|Mediawiki extensions||Plugins extending the set of features of Mediawiki.||Some of the most prominent extensions include: Page forms, Semantic Mediawiki, Visual editor, Ms Upload, MultimediaViewer, and more: we are also using a custom extension created by us!|
|Quasar framework||open-source Vue.js based framework for building apps||We use it for all the Front-end part of the site, taking advantage of its server side rendering feature and beautifully crafted components|
|Cheerio||DOM manipulation from an html string||We use it to perform some adjustments to the mediawiki html output before recording the latest version of a page to be served through the APIs|
|nodemw||Node.js interface for the Mediawiki APIs||We use it to call the mediawiki APIs from a Node.js script to retrieve and structure wiki pages before serving them through the APIs|
|detectlanguage||Language identification JSON webservice||We use it to determine the language of a wiki page, in order to filter them by language in the front-end site, or to perform hyphenation|
|Detecting languages (Google Cloud Translation)||Language detect using Google Cloud Translation APIs||As above, we use both of them concurrently|
|Knex||Query builder for Node.js||We use it to assemble mysql queries in our Node.js scripts|
|Email templates||A wrapper for sending email using template engines (like PUG) and transports (like Nodemailer)||We use it to send email using PUG templates and Node mailer-Sendgrid transport|
|jsonwebtoken||Node.js implementation of An implementation of JSON Web Tokens.||We use it to authenticate a student accessing his/her Classes|
|Hyphenopoly||"Hyphenation for node and Polyfill for client-side hyphenation."||We use it to hyphenate the organization or documentation's pages based on the detected language of each wiki page. Especially important on mobile devices combined with justified columns.|
|Redis||"in-memory data structure store"||We use it to record/retrieve the list of files stored in private wikis which can be accessed from students using the classes tool. The list is built each time that the page is loaded, hence the need of a solution focused on performances.|
... and more ! The list is in progress !