Technology we use link
Jump to navigation
Jump to search
| Line 18: | Line 18: | ||
!description | !description | ||
!use | !use | ||
| − | |||
|- | |- | ||
| − | |Mediawiki 1.34 | + | |[https://www.mediawiki.org/wiki/MediaWiki Mediawiki 1.34] |
|The collaboration and documentation platform which inspired and powers [https://www.wikipedia.org/ Wikipedia]. | |The collaboration and documentation platform which inspired and powers [https://www.wikipedia.org/ Wikipedia]. | ||
|We use it for the back-end side of this site, in order to ensure collaborative creation of quality contents. | |We use it for the back-end side of this site, in order to ensure collaborative creation of quality contents. | ||
| − | |||
|- | |- | ||
| − | |Mediawiki extensions | + | |[https://culturaitaliana.org/wiki/Special:Version Mediawiki extensions] |
|Plugins extending the set of features of Mediawiki. | |Plugins extending the set of features of Mediawiki. | ||
|Some of the most prominent extensions include: [https://www.mediawiki.org/wiki/Extension:Page_Forms Page forms], [https://www.semantic-mediawiki.org/wiki/Semantic_MediaWiki Semantic Mediawiki], [https://www.mediawiki.org/wiki/Extension:VisualEditor Visual editor], [https://www.mediawiki.org/wiki/Extension:MsUpload Ms Upload], [https://www.mediawiki.org/wiki/Extension:MultimediaViewer MultimediaViewer], and more: we are also using a custom extension created by us! | |Some of the most prominent extensions include: [https://www.mediawiki.org/wiki/Extension:Page_Forms Page forms], [https://www.semantic-mediawiki.org/wiki/Semantic_MediaWiki Semantic Mediawiki], [https://www.mediawiki.org/wiki/Extension:VisualEditor Visual editor], [https://www.mediawiki.org/wiki/Extension:MsUpload Ms Upload], [https://www.mediawiki.org/wiki/Extension:MultimediaViewer MultimediaViewer], and more: we are also using a custom extension created by us! | ||
| − | |||
|- | |- | ||
| − | |Quasar framework | + | |[https://quasar.dev/ Quasar framework] |
|open-source [https://vuejs.org/ Vue.js] based framework for building apps | |open-source [https://vuejs.org/ Vue.js] based framework for building apps | ||
|We use it for all the [https://culturaitaliana.org/ Frontend part] of the site, taking advantage of the server side rendering feature | |We use it for all the [https://culturaitaliana.org/ Frontend part] of the site, taking advantage of the server side rendering feature | ||
| − | |||
|- | |- | ||
| − | |Cheerio | + | |[https://github.com/cheeriojs/cheerio#readme Cheerio] |
|DOM manipulation from an html string | |DOM manipulation from an html string | ||
|We use it to perform some adjustments to the mediawiki html output before recording the last version of a page to be served through the [[How_it_works/APIs|APIs]] | |We use it to perform some adjustments to the mediawiki html output before recording the last version of a page to be served through the [[How_it_works/APIs|APIs]] | ||
| − | |||
|- | |- | ||
| − | |Esprima | + | |[https://github.com/jquery/esprima Esprima] |
|ECMAScript parser | |ECMAScript parser | ||
|We use it to securely parse the javascript object produced by the [https://culturaitaliana.org/Frontend_Index Frontend Index] storing the structure of the tree | |We use it to securely parse the javascript object produced by the [https://culturaitaliana.org/Frontend_Index Frontend Index] storing the structure of the tree | ||
| − | |||
|- | |- | ||
| − | |nodemw | + | |[https://github.com/macbre/nodemw nodemw] |
|[https://nodejs.org/en/ Node.js] interface for the Mediawiki APIs | |[https://nodejs.org/en/ Node.js] interface for the Mediawiki APIs | ||
|We use it to call the [https://culturaitaliana.org/w/api.php mediawiki APIs] from a nodejs script to retrieve and structure wiki pages before serving them through the [[How_it_works/APIs|APIs]] | |We use it to call the [https://culturaitaliana.org/w/api.php mediawiki APIs] from a nodejs script to retrieve and structure wiki pages before serving them through the [[How_it_works/APIs|APIs]] | ||
| − | |||
|- | |- | ||
| − | |detectlanguage | + | |[https://detectlanguage.com/ detectlanguage] |
|Language identification JSON webservice | |Language identification JSON webservice | ||
|We use it to determine the language of a wiki page, in order to filter them by language in the frontend site, or to perform hyphenation | |We use it to determine the language of a wiki page, in order to filter them by language in the frontend site, or to perform hyphenation | ||
| − | |||
|- | |- | ||
| − | |Detecting languages (Google Cloud Translation) | + | |[https://cloud.google.com/translate/docs/basic/detecting-language Detecting languages] (Google Cloud Translation) |
|Language detect using Google Cloud Translation APIs | |Language detect using Google Cloud Translation APIs | ||
|As above, we use both of them concurrently | |As above, we use both of them concurrently | ||
| − | |||
|- | |- | ||
| − | |Knex | + | |[http://knexjs.org/ Knex] |
|Query builder for Node.js | |Query builder for Node.js | ||
|We use it to assemble [https://www.mysql.com/ mysql] queries in our Node.js scripts | |We use it to assemble [https://www.mysql.com/ mysql] queries in our Node.js scripts | ||
| − | |||
|- | |- | ||
| − | |Email templates | + | |[https://github.com/forwardemail/email-templates Email templates] |
|A wrapper for sending email using template engines (like [https://pugjs.org/api/getting-started.html PUG]) and transports (like [https://nodemailer.com/about/ Nodemailer]) | |A wrapper for sending email using template engines (like [https://pugjs.org/api/getting-started.html PUG]) and transports (like [https://nodemailer.com/about/ Nodemailer]) | ||
|We use it to send email using PUG templates and Node mailer-[https://www.npmjs.com/package/nodemailer-sendgrid-transport Sendgrid transport] | |We use it to send email using PUG templates and Node mailer-[https://www.npmjs.com/package/nodemailer-sendgrid-transport Sendgrid transport] | ||
| − | |||
|- | |- | ||
| − | |Prism | + | |[https://prismjs.com/ Prism] |
|Javascript syntax highlighter | |Javascript syntax highlighter | ||
|We use it to display code snippets on the [https://culturaitaliana.org/How_it_works Frontend site] | |We use it to display code snippets on the [https://culturaitaliana.org/How_it_works Frontend site] | ||
| − | |||
|- | |- | ||
| − | |jsonwebtoken | + | |[https://www.npmjs.com/package/jsonwebtoken jsonwebtoken] |
|Nodejs implementation of An implementation of [https://jwt.io/ JSON Web Tokens]. | |Nodejs implementation of An implementation of [https://jwt.io/ JSON Web Tokens]. | ||
|We use it to signin a student accessing to [https://culturaitaliana.org/classes Classes] | |We use it to signin a student accessing to [https://culturaitaliana.org/classes Classes] | ||
| − | |||
|- | |- | ||
| − | |jsTree | + | |[https://www.jstree.com/ jsTree] |
|[https://jquery.com/ jQuery] plugin, that provides interactive trees | |[https://jquery.com/ jQuery] plugin, that provides interactive trees | ||
|We use it to display an interactive tree of [https://culturaitaliana.org/wiki/Frontend_Index the structured index] created by our script from a given set of wiki pages | |We use it to display an interactive tree of [https://culturaitaliana.org/wiki/Frontend_Index the structured index] created by our script from a given set of wiki pages | ||
| − | |||
|- | |- | ||
| − | |||
| | | | ||
| | | | ||
Revision as of 11:29, 28 June 2020
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), however, given a set even arbitrary of the most prominent tools we use, the reader might explore them further on his own and therefore retrieving what is missing.
| software | description | use |
|---|---|---|
| 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 Frontend part of the site, taking advantage of the server side rendering feature |
| Cheerio | DOM manipulation from an html string | We use it to perform some adjustments to the mediawiki html output before recording the last version of a page to be served through the APIs |
| Esprima | ECMAScript parser | We use it to securely parse the javascript object produced by the Frontend Index storing the structure of the tree |
| nodemw | Node.js interface for the Mediawiki APIs | We use it to call the mediawiki APIs from a nodejs 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 frontend 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 |
| Prism | Javascript syntax highlighter | We use it to display code snippets on the Frontend site |
| jsonwebtoken | Nodejs implementation of An implementation of JSON Web Tokens. | We use it to signin a student accessing to Classes |
| jsTree | jQuery plugin, that provides interactive trees | We use it to display an interactive tree of the structured index created by our script from a given set of wiki pages |
| ... and more ! The list is in progress ! |