Adds JSON files to manage the content of the Website in the two official languages of the team (Italian and English) in order to separate the website code from the textual content and images.
At the moment the entirety of the website uses JSON content except the footer, since in the future it will be able to dynamically load headers from the single pages
I decided to create a JSON file for every single page plus a generic one. At the moment the JSON files are empty and the content should not be considered in any way representative of the future contents of the website
Whenever considered appropriate, the website is able to load a dynamically decided number of elements (team areas, team members, events) even if in some cases the content is fixed (the reseq project).
It is worth mentioning that I was not able to obtain a working dynamic timeline. (The previous version defined spacing statically and without considering different devices, and since it is using css, I was not able to make up a solution to do it dynamically). I think however that to address this issue, I might wait the solutions to responsiveness of @GBergatto.
At the moment I have yet to define a way to load images
I will write a page on the WIKI to specify decision taken in the PR
[X] JSON files created
[X] JSON files linked to the code building the website
Adds JSON files to manage the content of the Website in the two official languages of the team (Italian and English) in order to separate the website code from the textual content and images.
At the moment the entirety of the website uses JSON content except the footer, since in the future it will be able to dynamically load headers from the single pages
I decided to create a JSON file for every single page plus a generic one. At the moment the JSON files are empty and the content should not be considered in any way representative of the future contents of the website
Whenever considered appropriate, the website is able to load a dynamically decided number of elements (team areas, team members, events) even if in some cases the content is fixed (the reseq project).
It is worth mentioning that I was not able to obtain a working dynamic timeline. (The previous version defined spacing statically and without considering different devices, and since it is using css, I was not able to make up a solution to do it dynamically). I think however that to address this issue, I might wait the solutions to responsiveness of @GBergatto.
At the moment I have yet to define a way to load images
I will write a page on the WIKI to specify decision taken in the PR