Logically related questions link
Jump to navigation
Jump to search
| Line 2: | Line 2: | ||
have not yet been asked) | have not yet been asked) | ||
| − | + | {{CI accordion | |
| − | + | |Why Mediawiki rather than Wordpress ? | |
| − | {{ | + | |Well, first Mediawiki is actually being used by the team behind Wordpress |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | Well, first Mediawiki is actually being used by the team behind Wordpress | ||
([https://automattic.com/ Automattic]) for their [https://developer.wordpress.org developer documentation] as proof of the uniqueness of its features. | ([https://automattic.com/ Automattic]) for their [https://developer.wordpress.org developer documentation] as proof of the uniqueness of its features. | ||
| Line 24: | Line 17: | ||
Finally because through the general design of our platform (where Mediawiki is used as back-end site) the presentation of contents (i.e. the appearance of the website) can be completely decoupled by contents themselves: a part of your team can solely take care of contents, and their organization or pages structure, and another part of the team can design whatever data consumer application querying the APIs, and to use the data and the semantic data returned by it, in any conceivable way, apart from creating client-side applications, of course for [https://d3js.org/ data visualization] as well. | Finally because through the general design of our platform (where Mediawiki is used as back-end site) the presentation of contents (i.e. the appearance of the website) can be completely decoupled by contents themselves: a part of your team can solely take care of contents, and their organization or pages structure, and another part of the team can design whatever data consumer application querying the APIs, and to use the data and the semantic data returned by it, in any conceivable way, apart from creating client-side applications, of course for [https://d3js.org/ data visualization] as well. | ||
| − | + | | Why a platform representing the Italian culture is conceived in English ? | |
| − | + | | Well, surely because English is the ''lingua franca'' of our times. | |
| − | |||
| − | Why a platform representing the Italian culture is conceived in English ? | ||
| − | |||
| − | Well, surely because English is the ''lingua franca'' of our times. | ||
Then because the native language of world of technology, to which this platform refers to, is English. | Then because the native language of world of technology, to which this platform refers to, is English. | ||
| Line 48: | Line 37: | ||
Then of course because the audience for this platform is meant to be international, that is being able to speak only partially Italian language: {{highlight|but where "prospective students" would find that an international and common language (English and computer language) originates, in this specific case, from a web of ideas of which the natural language or mother tongue is Italian language itself, will devote himself to the study of it with the feeling to keep up with the times and possibly to participate to the development of them from a privileged side. }} '''this text has been added in a subsequent edit and might be not consistent to the the natural flow of the initial statement''' | Then of course because the audience for this platform is meant to be international, that is being able to speak only partially Italian language: {{highlight|but where "prospective students" would find that an international and common language (English and computer language) originates, in this specific case, from a web of ideas of which the natural language or mother tongue is Italian language itself, will devote himself to the study of it with the feeling to keep up with the times and possibly to participate to the development of them from a privileged side. }} '''this text has been added in a subsequent edit and might be not consistent to the the natural flow of the initial statement''' | ||
--> | --> | ||
| − | + | ||
| − | + | | How the front-end counterpart of this site is created or updated? | |
| − | + | | Well, while the back-end side of this platform is built upon a traditional technology (specifically [https://www.apache.org/ Apache]/[https://www.php.net/ PHP]/[https://www.mysql.com/ MySQL]) the front-end side is built on [https://nodejs.org/en/ Node.js], eventually [https://www.nginx.com/ Nginx], and a client side Javascript framework based on [https://vuejs.org/ Vue.js] like [https://quasar.dev/ Quasar framework]. | |
| − | How the front-end counterpart of this site is created or updated? | ||
| − | |||
| − | Well, while the back-end side of this platform is built upon a traditional technology (specifically [https://www.apache.org/ Apache]/[https://www.php.net/ PHP]/[https://www.mysql.com/ MySQL]) the front-end side is built on [https://nodejs.org/en/ Node.js], eventually [https://www.nginx.com/ Nginx], and a client side Javascript framework based on [https://vuejs.org/ Vue.js] like [https://quasar.dev/ Quasar framework]. | ||
The latter side is fueled with data retrieved from Mediawiki (a forked version with some extended features, mainly an enhanced support for a non-flat namespace that is with sub-pages and sub-folders) through a Node.js script triggered every time that a page or file is created, updated, moved and deleted, and autonomously checking the mediawiki database with a specific frequency for any other indirect change (for instance when pages are imported through the mediawiki import page, or after the execution of some maintenance script). By this way, we can ensure a real time synchronization between the two sides on direct page's editing, and an accurate synchronization "within minutes" when the wiki site is updated in some indirect way. | The latter side is fueled with data retrieved from Mediawiki (a forked version with some extended features, mainly an enhanced support for a non-flat namespace that is with sub-pages and sub-folders) through a Node.js script triggered every time that a page or file is created, updated, moved and deleted, and autonomously checking the mediawiki database with a specific frequency for any other indirect change (for instance when pages are imported through the mediawiki import page, or after the execution of some maintenance script). By this way, we can ensure a real time synchronization between the two sides on direct page's editing, and an accurate synchronization "within minutes" when the wiki site is updated in some indirect way. | ||
| Line 73: | Line 59: | ||
In short all the contents on the front-end site are updated in a automatic way, using the Mediawiki back-end as data source, and are displayed in an interactive way using a different technology | In short all the contents on the front-end site are updated in a automatic way, using the Mediawiki back-end as data source, and are displayed in an interactive way using a different technology | ||
--> | --> | ||
| − | + | ||
| − | + | | Why Mediawiki rather than Wordpress ? (again) | |
| − | + | | Because the ultimate aim of this platform is to organize and structure significant data ensuring interoperability and a frictionless dissemination in the public domain (under specific terms, or after a specific amount of time) in such a way that Mediawiki has been chosen for its complementarity with [https://www.wikidata.org/wiki/Wikidata:Main_Page Wikidata] which aims to represent a common platform for the world's repositories of semantic data, and possibly to participate with its development. | |
| − | Why Mediawiki rather than Wordpress ? (again) | ||
| − | |||
| − | Because the ultimate aim of this platform is to organize and structure significant data ensuring interoperability and a frictionless dissemination in the public domain (under specific terms, or after a specific amount of time) in such a way that Mediawiki has been chosen for its complementarity with [https://www.wikidata.org/wiki/Wikidata:Main_Page Wikidata] which aims to represent a common platform for the world's repositories of semantic data, and possibly to participate with its development. | ||
In this sense Mediawiki is an open platform and an open archive through which data recorded therein are not registered in an arbitrary or proprietary data structure, but in a universal vocabulary (or they are conceptually prone to be so) which can be understood potentially by every one: where of course we don't mean a limited set of specific enterprises holding the data ingenuously provided by users at the expense of their lives. | In this sense Mediawiki is an open platform and an open archive through which data recorded therein are not registered in an arbitrary or proprietary data structure, but in a universal vocabulary (or they are conceptually prone to be so) which can be understood potentially by every one: where of course we don't mean a limited set of specific enterprises holding the data ingenuously provided by users at the expense of their lives. | ||
| − | + | ||
| − | + | }} | |
| + | |||
| + | |||
<!-- | <!-- | ||
| − | |||
Why a platform representing the Italian culture is conceived in English ? (again) | Why a platform representing the Italian culture is conceived in English ? (again) | ||
| − | + | ||
Well, because the contents of a non-universally spoken language are better disseminated (or they are disseminated ''tout court'') through a universal medium. In this case we have to speak about the "contents" rather than the "culture" because a culture is only communicable in its own language. | Well, because the contents of a non-universally spoken language are better disseminated (or they are disseminated ''tout court'') through a universal medium. In this case we have to speak about the "contents" rather than the "culture" because a culture is only communicable in its own language. | ||
At the same time (ma senza adottare strutture linguistiche alla Azzeccagarbugli che esprimendosi "da una parte" e "dall'altra" non si risolvono per alcun partito) it's up to such "emergent" language to contaminate such medium as much as possible, first with sympathetic or seductive words, then with | At the same time (ma senza adottare strutture linguistiche alla Azzeccagarbugli che esprimendosi "da una parte" e "dall'altra" non si risolvono per alcun partito) it's up to such "emergent" language to contaminate such medium as much as possible, first with sympathetic or seductive words, then with | ||
| − | |||
| − | |||
--> | --> | ||
| − | |||
| − | |||
Revision as of 07:20, 28 August 2020
(another way of indicating "frequently asked questions" which have not yet been asked)
ExpandWhy Mediawiki rather than Wordpress ?
ExpandWhy a platform representing the Italian culture is conceived in English ?
ExpandHow the front-end counterpart of this site is created or updated?
ExpandWhy Mediawiki rather than Wordpress ? (again)