How it works/Logically related questions - Revision history

Admin at 18:59, 3 January 2021

2021-01-03T18:59:29Z

Admin at 17:42, 8 December 2020

2020-12-08T17:42:16Z

Admin at 07:20, 28 August 2020

2020-08-28T07:20:19Z

Admin at 07:20, 28 August 2020

2020-08-28T07:20:07Z

Admin at 07:14, 20 August 2020

2020-08-20T07:14:56Z

Admin at 00:20, 20 July 2020

2020-07-20T00:20:48Z

Admin at 00:18, 20 July 2020

2020-07-20T00:18:27Z

Admin at 18:35, 19 July 2020

2020-07-19T18:35:35Z

Admin at 11:51, 19 July 2020

2020-07-19T11:51:40Z

Admin at 11:04, 19 July 2020

2020-07-19T11:04:28Z

@@ Line 40: / Line 40: @@
 | 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].
+| 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.

@@ Line 27: / Line 27: @@
 Then of course because the audience for this platform is meant to be international, that is  able to speak only partially Italian language, in such a way that where they will experience that a distinguished (not trivial, nor anonymous) English language originates from a specific wit of the Italian culture itself, they will be inclined to study and to learn Italian not only because it stands at a specific position in the rank of world's most studied languages (for whatever reason) but for its inclusive and possibly universal character, therefore providing the feeling of being at the center of cultural changes of our times.
-Then because the aim of each language is poetry, in such a way that expressing oneself in a foreign language (rather than in the mother tongue) refrains precisely from doing, or is ultimately expected, poetry, and allows to write in a rather plain way focusing on contents (that is on a stiffened form of expression) limiting one's own activity within conventional limits, ultimately productive in the daily life.
+Then because the aim of each language is poetry, in such a way that expressing oneself in a foreign language (rather than in the mother tongue) refrains precisely from doing, or that is ultimately expected, poetry, and allows to write in a rather plain way focusing on contents (that is on a stiffened form of expression) limiting one's own activity within conventional limits, ultimately productive in the daily life.
 <!--

@@ Line 1: / Line 1: @@
 (another way of indicating "frequently asked questions" which
 have not yet been asked)
 {{CI accordion

@@ Line 2: / Line 2: @@
 have not yet been asked)
+{{CI accordion
-<!--
+|Why Mediawiki rather than Wordpress ?
-{{Collapse|1=Discussion text to be put into box.|2=Why Mediawiki rather than Wordpress ?|padding=20px}}
+|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.
@@ 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.
-</div>
+| Why a platform representing the Italian culture is conceived in English ?
-</div>
+| 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.
@@ 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'''
 -->
-</div>
-</div>
+| How the front-end counterpart of this site is created or updated?
-<div class="toccolours mw-collapsible mw-collapsed" style="border-top:none">
+| 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.
@@ 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
 -->
-</div>
-</div>
+| Why Mediawiki rather than Wordpress ? (again)
-<div class="toccolours mw-collapsible mw-collapsed" style="border-top:none">
+| 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.
-</div>
-</div>
+}}
 <!--
 Why a platform representing the Italian culture is conceived in English ? (again)
-<div class="mw-collapsible-content">
 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
 -->

@@ Line 83: / Line 83: @@
 </div>
 </div>
+</div>
 </div>

← Older revision		Revision as of 00:20, 20 July 2020
Line 59:		Line 59:
	During this process the Node.js script performs some convoluted operation structuring data in such a way that they can be retrieved or even "consumed" by a front-end interface in a way that would not be possible without some intermediate operation and a further elaboration of data (for instance such infrastructure allows offline navigation through consistent set of pages).		During this process the Node.js script performs some convoluted operation structuring data in such a way that they can be retrieved or even "consumed" by a front-end interface in a way that would not be possible without some intermediate operation and a further elaboration of data (for instance such infrastructure allows offline navigation through consistent set of pages).

−	In short the front-end application (which of course is built ''ad hoc'' for this purpose, and is subjected to a development process completely decoupled by that of Mediawiki, even if the inter-dependency of the two is taken into account) retrieves its data through a [[How it works/APIs\|dedicated API]] from a specific Node.js back-end, and these data are continuously updated and structured following changes performed on the Mediawiki back end.	+	In short the front-end application (which of course is built ''ad hoc'' for this purpose, and is subjected to a development process completely decoupled by that of Mediawiki, even if the inter-dependency of the two is taken into account) retrieves its data through a [[How it works/APIs\|dedicated API]] from a specific Node.js back-end, and these data are continuously updated and structured following the changes performed on the Mediawiki back end.

← Older revision		Revision as of 11:51, 19 July 2020
Line 39:		Line 39:
	Then because the aim of each language is poetry, in such a way that expressing oneself in a foreign language (rather than in the mother tongue) refrains precisely from doing, or is ultimately expected, poetry, and allows to write in a rather plain way focusing on contents (that is on a stiffened form of expression) limiting one's own activity within conventional limits, ultimately productive in the daily life.		Then because the aim of each language is poetry, in such a way that expressing oneself in a foreign language (rather than in the mother tongue) refrains precisely from doing, or is ultimately expected, poetry, and allows to write in a rather plain way focusing on contents (that is on a stiffened form of expression) limiting one's own activity within conventional limits, ultimately productive in the daily life.

		+	<!--
		+	Then because if you do a good work (with a good expression) in a foreign language, then users of that work might be inclined to check your work in your mother tongue as the source and natural expression of even that language,
		+	-->

	<!--		<!--

@@ Line 14: / Line 14: @@
 ([https://automattic.com/ Automattic]) for their [https://developer.wordpress.org developer documentation] as proof of uniqueness of its features.
-Then, because the business model of Mediawiki and Wordpress are completely different. Wordpress allows an easy use but as soon as you want to expand or complete your website you are pushed (or constrained) to adopt paying solutions.
+Then, because the business model of Mediawiki and Wordpress are completely different. Wordpress allows an easy use but as soon as you want to expand or complete your website you are pushed (or constrained) to adopt paid solutions.
 Mediawiki (as well as our platform) is completely free, including any desirable
-advanced feature, at cost to deal yourself with the code (starting from wikicode
+advanced feature, at cost to deal yourself with the code (starting from wiki text
 itself, and proceeding with the creation of dedicated extensions).